zlacker

bluesky dev here. whoops.

as others mentioned, not a hard fix.

>>pfraze+(OP)
Hilarious though! I'm guessing this is the kind of stuff the Beta was supposed to find. Any other cool/funny bugs y'all have found?

>>pfraze+(OP)
Do you have a public test suite so we can see how solid your protocol is?

>>pfraze+(OP)
What is the easy fix? Use the .well-known/ standard instead of the current mechanisms, and roll back verification for anyone who’s already been verified with the flawed approach?

>>kodah+c2
I created a rich text system for posts to handle things like links and mentions with the eventual goal of it being the basis for all kinds of rich text (bolding, italics, spoiler tags, etc)

the flexibility bit us on the butt. people started faking mentions via the APIs and one user figured out he could pack 1000 mentions into one "@everyone" and cause us all to get notified. pretty predictable in hindsight but I dropped the ball there

>>pfraze+dc
Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.

http://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule

>>pfraze+(OP)
Can I ask what's your tech stack?