pull down to refresh
411 sats \ 5 replies \ @cointastical 28 Feb 2023 \ on: RIP Bitcoinhackers Mastodon bitcoin
NVK even yanked it earlier than when he said he would. He said March 1st, not Feb 27th. I had procrastinated on making one last backup of who I was following and members of a list so that I could update my list of "who to follow" so that I could then provide a current list (after stripping out any @bitcoinhackers.org entries):
Mastodon Who To Follow
https://github.com/cointastical/Mastodon-Who-To-Follow/blob/main/README.md
Oh well, Mastodon sucks, and this is a PERFECT EXAMPLE as to why, but only one of many, as I shared in my comment reply here:
Mastodon saw record number of downloads after Musk’s Twitter takeover
#87933
Bye bye Fedi, and thanks for all the (dead) fish.
Now on to Nostr!!!
if i had to guess, the server bill comes on the 1st, and dedicated are expensive so.
yanking it yesterday would make more sense than not.
reply
“The host turned off their service two days earlier than promised, therefore the protocol used by the service sucks!”
LOL
reply
Yes. That is valid criticism.
You're at the mercy of the instance maintainer and they can make their arbitrary rules and not keep their promises.
This protocol sucks.
Nostr is showing way because you own your identity there, courtesy of public key cryptography.
You're not bound to one single Mastodon instance that can close down at any second, resulting in you losing all your data, identity and followers.
reply
Thanks to the bridge there's no need to choose between the two
reply
Well, if you stay on Mastodon, you're still vulnerable to all the things I talked about.
Better to create a nostr identity.
Unless you get an
nsec with this bridge. Then yeah that's pretty nice.reply