you can make an app that *interoperates with* atproto by writing to a user's PDS in parallel with writing to your database.
but you make an *atproto app* by making the client write to the PDS and listening to the relay for the records.
you can make an app that *interoperates with* atproto by writing to a user's PDS in parallel with writing to your database.
but you make an *atproto app* by making the client write to the PDS and listening to the relay for the records.
who cares about authenticating your transfer when you can read after your write
who cares about authenticating your transfer when you can read after your write
why not extend the protocol to support that in a generic way?
why not extend the protocol to support that in a generic way?
paletteswap.site/dif...
paletteswap.site/dif...
but it does something entirely different (frees the object early, causing a crash during GC)
be careful when running node libraries under gjs
but it does something entirely different (frees the object early, causing a crash during GC)
be careful when running node libraries under gjs
theres a new scam going around where they place a box with a stick on the floor, the idea is that they put something you like underneath the box to lure you in and then they pull the stick with a string, trapping you inside!
be careful yall......
theres a new scam going around where they place a box with a stick on the floor, the idea is that they put something you like underneath the box to lure you in and then they pull the stick with a string, trapping you inside!
be careful yall......
DO NOT CLICK THE LINK.
Bluesky would NEVER send a DM like this and make you scared. This would come through email and would have a more professional email than this.
Stay safe!