IRC channel logs

<jar286>Has anyone heard about the proposed 'at:

<jar286>' URI scheme?

<jar286> https://mailarchive.ietf.org/arch/msg/uri-review/x3LbUP7_DOlEFCH84QvZdRU74Js/

<jar286>Has to do with the AT protocol which has something to do with @foo social media handles?

<jar286>(Yes this might be the wrong place to ask about this, but this is also the only chat I follow)

<isd>Looks like it's a bluesky thing. Hadn't previously heard of it.

<isd>(and this channel is low-traffic enough that I'm fine with it veering off-topic from time to time)

<juliana[m]>Wow, they sure did rush from embrace to extend

<isd>(I do wonder why not just use acct:)

<ocdtrekkie>The comments in the list recommend atproto: to ensure there's no collisions with other uses.

<ocdtrekkie>It is intriguing how different standards attack from different angles. AP being a W3C spec and AT going after custom URI schemes.

<ocdtrekkie>I think I'd really like to see some evidence the protocol will extend beyond literally just BlueSky's own app before too much effort is made by standards groups. ActivityPub has proven itself with dozens of implementations.

<drakonis>must be real nice to be able to just walk up to standard bodies and EEE them into submission

<drakonis>worse yet, being so shameless in order to achieve that feat

<Zarutian_iPad>is BlueSky still invite only and not publickly web accessible?

<Zarutian_iPad> https://lobste.rs/s/lfbey9/binary_formats_protocols_ltv_is_better

<Zarutian_iPad>more on topic but not that much

<Zarutian_iPad>wondering if we use the Agoric/smallcaps formated json then it might be possible to negogate at connection establishment for say an msgpck transliteration/format that that pretty much spits out the same stuff the smallcaps does or expects depending on where the line should be drawn

<Zarutian_iPad>(in Agoric implementation if we just change JSON.parse() and JSON.stringify() to whatever equiv then nobody including smallcaps would be wiser)

IRC channel logs

2023-05-10.log