this is basically what happened with APNG, people love that format despite it being objectively worse than animated webp because it has the PNG name (even though the PNG group rejected it for around 15 years until they were taken over by the W3C)
nah webp is good actually
"webp is fascism" and other deranged takes i have witnessed on this network
i wonder what i should set as the favicon for this pds since witchsky shows those in the client now
i might change it so that the requesting user's current pds is checked/updated from the original source on initial request, and then read locally for a period of time after that
right now migrations are detected by listening for identity events, checking the account's did document, and comparing it to what's on file
are identity events just not fired in specific cases?
call me when they enable animation though
oh nice the pfp on this account is transparent now by default
hmmm, some migrations still aren't working on the pds feeds...
most ml stuff doesn't interest me but i've found particular interest in roost's projects (e.g. osprey) since they've been shown to work well at scale, can run locally, and reduce the rate in which people have to deal with this stuff
the less we can expose people to harmful material, the better
"just hire more people" results in what happened to facebook moderation contractors, a pure regex/match system results in a ton of false positives, lack of moderation entirely is worse
saying this as someone against the large majority of applications for ai/ml: i do want to know how people upset at ml-based auto moderation propose it be handled at the scale of tens of millions of users without creating a higher level of false positives or putting more people at risk
if i ever allow a single line of code written by claude into any of my repositories you are legally allowed to shoot me on the spot
the reasoning for this is because the feed now alternates between different jetstream instances (due to intermittent issues with the official ones), and some of those jetstream instances pull from the above relays
note to other PDS admins who want to ensure that posts appear in the "Your PDS" feed: i'd recommend adding relay.fire.hose.cam and northamerica.firehose.network to your PDS_CRAWLERS env variable (you can add multiple by separating each entry with a comma)
just tried adding a couple more relays to request crawls from
test
Hi
finally got it back up
will be making an attempt to move the pds to another server in a bit
is there a jetstream instance running off of blacksky's relay by chance
added a few more jetstream instances for the pds feeds to fall back on, namely a couple of microcosm's instances and firehose.stream's nyc instance
...if i'm reading that california os age verification bill (AB-1043) right, couldn't this technically be implemented by a vendor by just asking for a number during setup and treating their app marketplace as an "addon/extension store"?
(the accounts have that at the end of their handle for the same reason why most accounts on here have "bsky.social" at the end of their handles)
cryptoanarchy.network is one of the open account servers run by blacksky (alongside blacksky.app and myatproto.social), these accounts seem to be pivoting to registering on account servers not run by bluesky under an assumption that no action will be taken (which is untrue)
sorry for being so negative over the past few days literally nothing positive is happening and there's almost nothing positive to look forward to
i feel like i've had it burned deep within me that asking directly for help/input on things is bad in a lot of cases and i really wish i could unlearn that
this is agonizing i hate this so much
AAAAAAAAAAAAAAAAAAAHHHHHHHHHHHHHH GOD I HATE FEELING LIKE I CAN'T DO A DAMN THING
