5 ms·
That is not an unreasonable assumption, no, for a service. I would posit that your error is in thinking of Mastodon as a service, rather than a community of pe
by jtode 3y ago
That is not an unreasonable assumption, no, for a service.
I would posit that your error is in thinking of Mastodon as a service, rather than a community of people trying to get away from using "services" to live our lives through.
In that context, I would expect exactly these sorts of errors, and as an admin, I would expect the community to understand and be forgiving, because we are all figuring this out together as we go - again, with only the money in our bank accounts.
I think that if you're genuinely interested in participating in the Mastodon project and helping it to succeed, I would suggest that writing a polemic which reflects your service-based expectations and shits on the efforts of the earnest sysops who do this for the passion of it and the desire to see this better alternative happen is about the worst way to express your frustration at losing data that you had the option to do a weekly backup of yourself.
You need to let go of your "service" expectations and start thinking of Mastodon as what it is: a network of personal computers which people are using to talk to each other. You need to think of your personal Mastodon profile the same way you think about your personal hard drive.
- lapcat 3y ago> you had the option to do a weekly backup of yourself. I would gladly do this, as I gladly back up the data on my own personal hard drive, but I had no idea I needed to do a weekly backup of my Mastodon data! Nobody warned Mastodon users that this kind of data loss was to be expected. By the time I found out, it was too late. How many of the 1.8 million monthly active Mastodon users are doing weekly backups of their Mastodon data? When has Eugen Rochko or other Mastodon instance administrators ever advised Mastodon users to this? You seem to be blaming the victims here. And again, it's not just me: every user of my old instance experienced the same data loss, whether they know it or not (likely not). There's no "community" if the Mastodon instance administrators are not making crucial announcements to Mastodon users, not helping those users preserve their data. If anything, I have just performed a service to the Mastodon community by informing Mastodon users that their data is not safe on the instances. Instead of properly warning users, they spread reassuringly false bromides like "It doesn't matter which Mastodon instance you join." As it turns out, this matters a lot.
- jtode 3y agoAgain though, you need to examine your expectations here. These are not Admins who have qualified for a job - some might happen to be that, but most are not. Most are just people who want this to happen, again, and are doing their best. That being said, new tools come out all the time to improve the situation; "we" (I am not an admin, just a fan) are figuring out what a functioning federated social network needs by doing a federated social network. Mistakes will be made. The answer to the mistakes is not retreating to "monolithic single-entry service only without billions of dollars of startup capital," which is what your advice to only go to the biggest instance smacks of. There is a new thing, I encountered the hashtag yesterday but I can't recall it now and I didn't look closely, but it's some sort of database I think in which instance admins can leave notes and ratings of other instances, or something like that. I wish I could remember the hashtag, but it looks to me like an attempt to at least start setting up a clearing house type thing for the deeper details of instance administration. I believe the problem it was created to solve has more to do with moderation and lazy admins who don't bother doing it, but it could easily be extended to examine the settings of instances and give users optics. I'm certainly not saying that you should not point out that this is happening, by the way, and if your admin was lazy/complacent/obnoxious about it, you are quite correct to leave. I, likewise, chose to leave the main instance some time back, and I'm not gonna get into why, it was different and personal reasons, and the miracle of this network is that I found a new place that suits me as well. I do think your piece reads as entitled and ignorant, and you should give it a rewrite with a better understanding that you are addressing a community, not a company. edit: OP has decided he doesn't want me to comment further apparently, I am no longer able to reply, but I can still edit. In response to the reply below, I lost all my posts on Lemmy a few weeks ago because of a CSAM post attack which basically made them need to wipe the database, from what I read. Shit happens when you're doing something out of pocket with nothing but what's at hand. The entire Fediverse is experimental and held together with duct tape and spit. Don't make the mistake of thinking it isn't again. That said, I stand corrected in my original, flip response. lapcat did not advocate going back to Twitter.
- walterbell 3y agoHow many humans (1-10? 10-100? 100-1000?) from the Mastodon community signed off on the Mastodon feature/policy which enabled admins to (inadvertently?) delete user content without advance notice to affected users?