IMO, if you choose a common username (except for alt accounts) for all your platforms (in my case, dch82) it’s fairly easy to find all the accounts. If you want to, you can also link your other platforms in the bio.
Suburban London guy
Mastodon: @[email protected]
IMO, if you choose a common username (except for alt accounts) for all your platforms (in my case, dch82) it’s fairly easy to find all the accounts. If you want to, you can also link your other platforms in the bio.
I don’t actually mean it’s EEE but that whatever they are doing feels similar; besides, with one big server controlled by a corporation in the centre of their ecosystem, they could “defederate” any rising AT-compatible competitor servers out of existence.
They might not now, but don’t ever trust a company to not do this.
what are you talking about? bluesky isn’t open source, the protocol is, and it reeks of embrace, extend, extinguish by branding itself as an open network
Fair enough, I will make another version shortly
EDIT: Solarized low-contrast versions are available; I think it would look much better!
No, AT is open source, not Bluesky
“Smile and wave boys, just smile and wave.”
Nice, reply from Mastodon.
Yep! I’ve noticed that using multiple hashtags does produce results.
I want to be able to engage with the community, even if it is just a couple of replies.
Go to settings > blocks and there should be a instance block there
That’s good, although I do want to crosspost to other instances like .zip
EDIT: nonono, i mean this post to block bad instances
The danger (as they can see) are not selfhosters, but larger competitive instances. They don’t allow AT servers of over 10 users and 1500 events a hour. This is clearly targeted to prevent large-scale instances (fediverse style) from being created.
How many bluesky users actually selfhost?