One of the most important tools for trust and safety efforts is the “block” feature, allowing a user to entirely block someone else from following them. Yes, on Twitter you can get around this by g…
Depends on what going backwards means, from a technical perspective this is fine and more forward than the centralized providers would have you believe. The only step back im seeing is mainly UI and tooling. The bones here are fine and the UX im seeing on Lemmy and Kbin are inline with reddit just a few years ago.
If having to deal with UX issues is a huge problem the just wait and come back when its more developed, most of what you use in your day-to-day computing is OSS code, if its good enough for your daily work, its good enough for socials.
You know, maybe I didn’t understand the full meaning of your comment - I assumed you were referring to not having the ability to block a user as a “return to how social was meant to be on the internet”
why would I not be able to block a user on the internet? I was able to block them on every system from the beginning. Centralized services will have you think you need thier magic code to do that but we used to do it with clients all the time.
I still run IMAP email clients with a boat load of personal rules, though I did move the blocks to my server for efficiency. Still its MY server, like im posting to you now from my fediverse instance. If i wanted to block someone here they can be annoying sure but at the end of the day I have many of the same tools i had before, though there might be more cat and mouse. That said nothing stops you from having entirely private instances and since we technically can completely control our servers and clients its entirely possible to have things like one-way servers and nodes that are more picky about what they forward. If the network grows you will see an increased sophistication in management tools.
Depends on what going backwards means, from a technical perspective this is fine and more forward than the centralized providers would have you believe. The only step back im seeing is mainly UI and tooling. The bones here are fine and the UX im seeing on Lemmy and Kbin are inline with reddit just a few years ago.
If having to deal with UX issues is a huge problem the just wait and come back when its more developed, most of what you use in your day-to-day computing is OSS code, if its good enough for your daily work, its good enough for socials.
You know, maybe I didn’t understand the full meaning of your comment - I assumed you were referring to not having the ability to block a user as a “return to how social was meant to be on the internet”
why would I not be able to block a user on the internet? I was able to block them on every system from the beginning. Centralized services will have you think you need thier magic code to do that but we used to do it with clients all the time.
I still run IMAP email clients with a boat load of personal rules, though I did move the blocks to my server for efficiency. Still its MY server, like im posting to you now from my fediverse instance. If i wanted to block someone here they can be annoying sure but at the end of the day I have many of the same tools i had before, though there might be more cat and mouse. That said nothing stops you from having entirely private instances and since we technically can completely control our servers and clients its entirely possible to have things like one-way servers and nodes that are more picky about what they forward. If the network grows you will see an increased sophistication in management tools.
But we were talking about Twitter specifically, not any sort of self-hosted platform or personal site.
I don’t disagree with you, I’m just confused when the discussion moved from Twitter to an anecdote about one’s IMAP email client
my bad, im in “fuck these guys lets all setup nodes” mode atm and still getting used to the UI