Greg will post once it's ready

huh, geez. i watch this discord like a hawk yet still managed to miss the bit that asked us to dm someone for beta access

who should i be dming?

you should be dming greg, doing it now isn't very useful i believe

You'll have to wait till the next round @andrew

Too late now, but once it's announced again it's Greg.

Not Brimble.

😦

McKeon.

so sad

or erwin, they seem to be able to hook people with access

No 😄

or maybe they mean access to the channel

He meant access to the channel.

I missed it as well Andrew :(

makes sense

Yeah, only Greg has access to add people to R2 AFAIK.

And he's doing it on a schedule I believe.

yup, next one soon™️

Greg posted a bit prematurely

I think tomorrow is a better bet

Is the invite posted in this channel or another?

This is the channel

Sooner is "always" better

Highlighting this poll again for visibility for anyone that missed it

I'd vote #2, but as long it's using a semantic

details

+

summary

element, it should absolutely be searchable via ctrl + f in the browser 👀

Is that true? https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details doesn't let me search into the summary element. At least not on FF

ah interesting. Works for me in Chrome, weird

Yeah, Chrome seems to handle it

New release just went out     * Sigv4 supports (unchunked) signed payloads.     * Fix put for open beta bindings (internal beta bindings are unaffected).     * Fixed a regression in the S3 frontend around decoding the key name correctly (object characters like :, ?, and ' ', weren't handled correctly). This regression also applied to x-amz-copy-source.     * Fixed a bug where deleting one object and then deleting another object which is a prefix of the first could result in problems during deletion.     * Fix corner condition where DeleteObjects may return an error even though the object was in fact deleted.     * startAfter + continuationToken is fixed for listing buckets and objects. Listing objects remains broken in that some key sequences aren't returned in lexicographical ordering. This also impacts startAfter behaving correctly in some cases.     * S3 ListObjects now correctly renders Prefix, Delimiter, StartAfter, and MaxKeys in the response object.     * ListObjectsV2 now correctly honors encoding-type parameter.     * PutObject works with POST requests for S3CMD compatibility