aer0xander.bsky.social
@aer0xander.bsky.social
I don’t eat a lot of nuts anyway so no nut november is easy for me, not sure why ppl are complaining it’s so difficult
November 11, 2025 at 4:41 AM
Hell yeah brother
September 26, 2025 at 7:37 AM
Do not rotate dog
April 6, 2025 at 5:52 AM
She CRINK on my BRICS till I lose global hegemony
March 30, 2025 at 2:23 AM
Least corrupt politician in LatAm
March 3, 2025 at 3:18 AM
I prefer my suffering raw
January 26, 2025 at 7:39 AM
Proud of you, keep it up!
December 17, 2024 at 8:04 PM
Hell some for-profit businesses don’t even make money 🤣
December 17, 2024 at 2:11 PM
Talking directly to users she in founder mode
December 8, 2024 at 11:27 PM
Some bodybuilders set an alarm to wake up in the middle of the night and have a meal
December 5, 2024 at 2:54 PM
With DID:ETHR one potential solution would be is to create a local temporary L2 as DID directory and eventually post a proof on L1.
But I think first working on having more users custody their own keys and having more PDS’s is a better starting point for making the network more censorship resistant.
November 29, 2024 at 3:15 PM
You can def add extra local keys, but you those are tied w/ DID in the PLC directory so that can be easily censored, you could have a local (and verifiable) forked version of it + local PDS which gets federated upon trusted web connection. But then you can’t add new actors to it in a trusted manner?
November 29, 2024 at 3:15 PM
I suppose it could work if someone runs a mirror of the PLC directory locally but that doesn’t seem like a solid solution either
November 29, 2024 at 1:21 PM
But this solution wouldn’t work with DID:PLC I think, so it would be a hardfork of AT Proto with a different identity method like DID:ETHR.
I already integrated SIWE in my PDS, initially I wanted to use DID:ETHR as a DID method but then my PDS wouldn’t be compatible with the rest of the network
November 29, 2024 at 1:20 PM
No way my Airbnb had a pre-installed PDS
November 22, 2024 at 12:59 PM
That’s a big polycule wow
November 19, 2024 at 4:08 PM
Servers in Switzerland/Iceland and incorporation on a Caribbean island would be the most optimal set up.

Even with Bluesky being a non-monopolistic company, the EU will still find a way to fine them lol
November 19, 2024 at 10:46 AM
The Bluesky Social PBC is based in Delaware, I don’t think DE will go rogue?

Most neutral place without it being some authoritarian country would be Switzerland. EU itself has too much regulations etc.
November 18, 2024 at 5:05 PM
Bruvsky
November 17, 2024 at 6:24 PM
AT kinda need support for DID:ETHR for this, my idea was to have P256 keys stored locally with WebCrypto as the signing keys. Frequently you would switch the signing keys in the DID by using a smart wallet which could be controlled 1/2 with an email and passkey, so that you won’t easily lose access.
November 14, 2024 at 8:59 AM
Yeah I’ve got a fork of the client at creaton.io

Will have crypto tipping, subscriptions and privacy features.
Only problem is that encrypting a post for subscribers is still difficult with smart wallets, but SCWs are the best onboarding mechanism, kinda even want to have users w/ an EOA use them
Creaton
Social media as it should be. Find your community among millions of users, unleash your creativity, and have some fun again.
creaton.io
November 14, 2024 at 8:47 AM
The users of the Creaton PDS like mine @alexander.creaton.social have a smart wallet linked to their DID.
I’m aiming to onboard crypto natives. If existing Bluesky users want to they can migrate to the Creaton PDS for crypto features, would be nice to still cryptopill some of them, lots HATE crypto
November 14, 2024 at 8:15 AM
I’m the only dev building a crypto app on top of atproto (i think), I tried a lot of social protocols out there, some shut down, some are too expensive for users (farcaster), some are too onchain which just doesnt make much sense. Only critique I got is that PLC is a bit too centralized for my taste
November 11, 2024 at 11:33 PM