favs.blue
  1. 3

    "When it's all said and done, the Atmosphere is just a medium for communication and information transfer. You mustn't confuse it with reality."

    You're wrong. The border between the two isn't all that clear. I'll be able to enter it soon. In full range. Full motion. I'll translate myself into it.

    71 17
    Jul 22, 2026
  2. 5

    DRM should be widely viewed as the anti-competitive, anti-consumer practice that it is, and any implementor of it should be met with a boycott and/or lawsuit, send tweet

    57 13
    Jul 1, 2026
  3. 7

    Odeo released a new service today called Twttr, which is a sort of “group send” SMS application. Each person controls their own network of friends. When any of them send a text message to “40404,” all of his or her friends see the message via sms.

    #20yearsago

  4. 8

    Reply to @null.namespaces.me

    less infra overhead = more sex with computers. exactly.

  5. 9

    samhain is typing...

  6. 11

    "average person uses 5 concurrent umans sessions at a time" factoid actually just statistical error. average person uses 1 session at a time. Jeff Sessions, who lives in a cave & uses 10,000 each day, is an outlier and should not have been counted

  7. 12

    Hey #Followers: Check this out. Pretty #Cool.

  8. 13

    Reply

    less infra overhead = more product velocity. exactly.

  9. 15

    i don't think anyone should use w social, and i think the atproto dev community should disown it entirely

  10. 16

    Reply

    following ted's recommendation, i will be writing and publishing an overview of the cases for/against updating the URI specification to permit DID-as-authority

  11. 21

    Reply to @mfzx.net

    seems to be converging on "at:did:…"?

  12. 22

    Reply to @mfzx.net

    @bnewbold.net: "IMHO adding a post-quantum option is the top priority. I'm open to removing secp256k1 in theory, but would not prioritize the effort needed over adding MLDSA (or whatever)"

  13. 23

    Reply to @mfzx.net

    @dholms.at up, presenting "Possible changes
    for IETF version"

  14. 24

    Reply to @mfzx.net

    scope of the atp working group

  15. 25

    Reply to @mfzx.net

    @bnewbold.net starting his presentation on the status of the repo and sync documents