bryan newbold

M̴̥̋r̶͈̄.̶̧̚ ̶͙̀W̵͇͝à̶̯ţ̶̾š̸̯ȍ̸̩n̸̪͘ ̴̨͊-̴͇́ ̷̞̈́c̸̹̈́ō̴ͅm̴̗̆e̷̮̽ ̶̯̚h̷̡̎ḛ̷͒r̴̞̈́e̶̦̐ ̵̲̑-̷̬͠ ̷̧̑I̸͚͋ ̴̹̊w̴͕̎ȃ̷̭ǹ̴̟ť̶͈ ̷̱̂t̷̲̓ó̸̱ ̶̹́ș̸͋e̸̹͗e̷̾ͅ ̸̻͌ỵ̵́ö̶̯́u̷̳͝

AI scraping volume is centralizing the web by making "hosting a website" as difficult as "hosting your own email". even if you are fine having your site crawled, the scrapers are so aggressive that you basically need to use a CDN or tool like Anubis or be able to serve millions of req/day

this is a cool project! in addition to automating offsite repo+blob backups, it has a web UI for registering PLC recovery keys (which you keep in a p/w manager, not remote service), and doing the adversarial PLC recovery process (eg, if your "old" PDS is unavailable) solid step for own-your-data

it's so over (dril posts on threads now)

who is developing a reputation for taste in atmospheric design? eg, in the 2010s era, I would refer back to Github URL path structure, APIs, and product design (even though I didn't use github directly very much). who is doing that for atproto lexicons, apps, etc?

I don't have any confidence that US/Israel will stick to anything. US/Israel could still attack in the next 24hr, or in a month, etc

probably a good time at least, like, upgrade to modern/current/supported versions of base OS, runtimes, network daemons. that debian oldoldstable box running python3.5 which has somehow made it this far probably ain't going to make it

devs working with bsky image embeds: we are planning to bump the image embed blob max size from 1 MByte to 2 MByte. first in the lexicon schema, and then in the Bluesky Social app. more about impacts, and what this means in terms of lexicon evolution, in this github discussion

@grain.social is good now

the space data center thing doesn't make economic sense. is it about evading govt regulation or taxation? or just hype/noise (I mostly assume the later)

taking this pretty seriously for both atproto and PLC. don't foresee having firm proposals until towards the end of the year at the earliest, but already starting to think about transition logistics

more pizza for your consideration

also, I guess I should add: the strong version of all this is permissioned data, where you get more control over who can access data at all (with tradeoffs of visibility, reach, and benevolent reuse). which is going to be a lot of work, but is getting underway

to give an update on where that proposal stands: I got as far as publishing demo lexicons and deploying an example that passes through headers aligned with the IETF AIPREF work last summer: demo.user-intents.org