Bsky.Team

once upon a time in the land of gnomes…

hahaha okay cool. Yeah that's right, allows me to focus on protocol and platform work

are you a... "friend of the compost outhouse"

haha rude

I just watched it from the sidelines since I moved out of product. Those poor folks tried it twice before getting blocked due to ecosystem readiness issues. Finally doing it... yeah it's great

Too many options can confuse consumers

Sam, I know you worked hard on the Lettuce. You did really great work. You should be proud. We all knew it carried some risks and I'm proud we're the kind of company that takes those risks. But

Striking "lettuce" off of the product roadmap and sighing

It should feel immensely smoother. The new RN architecture performs a lot lot better

I do prefer Fable but Opus seems not far off for basic things. I'd like to just keep replacing primary/secondary models with upgrades. Sounds like they're going to swap out Fable 5 for Opus 5 and hope we don't cry too much.

standard aws bill

Fable seems by far the best to me. The open weight models are impressive and closing the distance but definitely not the best.

Seems like Anthropic fixed this? Probably a bad deploy that got fixed, hopefully they're trying to merge the quotas!

Hopefully Anthropic made a mistake here while trying to make Fable permanent. Maybe they're merging Fable usage into the main quota instead of keeping it separate? Because we have 2 more days! dowehavefable.com

If you owe AWS $700, that's your problem. If you owe AWS $7 trillion, that's their problem.

This is best example so far of "information wants to be free"

Congrats!

it was a real ericssy

Just went to see the Odyssey. Had a great time, longer than I expected, I'm getting texts from my gf like "Are you ever coming home." Then I'm walking home and you wouldn't believe the cast of characters that got in my way. Like the gods were against me. And you wouldnt believe what I came home to

Just self-replying to cover everyone's responses -- decent points are being made about the challenge here. I dont have a great answer; it may just fall on each pds operator to decide how to handle it

robot comments in session file are super overbearing lol. maybe worth making it verify claims and try to fix things at code level instead of these paragraphs

do it. The Puyallup. just do It.

yeah probably not as a lexicon feature itself. but you could for instance specify a lexicon with just one field "content" that is the cipher text (either as a string or as bytes)

probably a few ways you can cut it. but the protocol is not opinionated about record contents (except that they fit the atproto data model). so you can just store E2EE data in record and layer on some type of key-agreement scheme (like decentralized MLS)