Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mastodon.technology Shutdown

ashfurrow.com

Post reply on HN
Print view View original

321–330 of 604 posts

Re: Mastodon.technology Shutdown

#321

Post by verdverm »

lapcat wrote: post #316
verdverm wrote: post #305

Earlier quoted context omitted.

You called it an investment, it is not an investment, it is an acquisition. It was not 100% obvious what you were implying, obviously

> You called it an investment, it is not an investment, it is an acquisition. Okthanksbye. > It was not 100% obvious what you were implying, obviously "Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize." https://news.ycombinator.com/newsguidelines.html

In Comments

Be kind. Don't be snarky.

---

I see you've edited it now to be more clear

Re: Mastodon.technology Shutdown

#322

Post by riffic »

m3kw9 wrote: post #246
proactivesvcs wrote: post #28

This is one of the strengths of a federated system run by people who aren't looking to profit. Firstly, they care about their users and are more likely to take difficult decisions, like the one Ash has made, for the good of themselves and their users. In doing so everyone involved has time to make an orderly move. Secondly, the service survives. Mastodon didn't shut down. The Fediverse didn't close. One beloved insta…

Twitter shutting down would need a couple black Swan events, you shouldn’t avoid doing something just because there could be a small chance of death(not walking out side to avoid a meteor strike). Twitter by all means is superior in every sense, speed, network size, reach and content.

> black Swan events

I think we might be experiencing this just in this year with its new ownership about to occur.

Re: Mastodon.technology Shutdown

#323

Post by shadowfacts »

somehnacct3757 wrote: post #172
yellow_lead wrote: post #17

Earlier quoted context omitted.

Well, where do you expect your data to be stored? In the ether?

On a server that I personally own or rent. Why does my data need to be anywhere else?

So then run an instance yourself on your own server?

Re: Mastodon.technology Shutdown

#324

Post by k__ »

mattl wrote: post #33
Macha wrote: post #10

Earlier quoted context omitted.

Network effects of twitter. Your friends are already on twitter if they still use this style of broadcast text based social media. Also recent privacy concerns and less recent issues with internet hostility means we're already past peak twitter, so mastodon is having to break into a declining market.

It's also less about my friends being on Twitter and more about the people who aren't my friends being on Twitter too...

Yes, so probably a marketing thing.

Re: Mastodon.technology Shutdown

#325

Post by barkingcat »

cmeacham98 wrote: post #44
proactivesvcs wrote: post #28

This is one of the strengths of a federated system run by people who aren't looking to profit. Firstly, they care about their users and are more likely to take difficult decisions, like the one Ash has made, for the good of themselves and their users. In doing so everyone involved has time to make an orderly move. Secondly, the service survives. Mastodon didn't shut down. The Fediverse didn't close. One beloved insta…

Look, I like open source federated ecosystems like Mastodon, but claiming Twitter or Facebook will be shut down any time soon is laughable. I'm not sure I could reliably predict whether Twitter or Mastodon will live longer.

Once the twitter sale is completed, the new owner of twitter can chose whatever they want to do with it, including shutting it down - which in this milleu would be something that the buyer of twitter will consider doing just for LOL's.

imagine the trolling potential of a rolling outage of twitter or ooops "new owner" deleted the database as a joke. Or replace all twitter profiles with sayings from Doge.

before you say "this person can't possibly do this" ... think again.

Re: Mastodon.technology Shutdown

#326

Post by Chris2048 »

lovich wrote: post #224
Chris2048 wrote: post #217

Earlier quoted context omitted.

"soon enough" could be a decade relative to the assumption that they'll be around forever.

If you’re going to stretch definitions like that “anytime soon” can go as far. It was a reasonable paraphrase

If by "stretch" you mean "consider the context", then no, it's an unreasoned paraphrase.

Re: Mastodon.technology Shutdown

#327

Post by teawrecks »

IMO there's nothing wrong with passing the torch to a new maintainer, this is just part of the design of mastodon. People shouldn't arbitrarily trust an instance maintainer on mastodon any more than they should trust google, twitter, fb, or a tor node with their data. The info they chose to share in plain text with a mastodon instance should be considered compromised. All that matters is the future; where will you send your data going forward?

It's part of the design of mastodon that the maintainer can pass the admin role to a new maintainer, and if a user doesn't approve, they can migrate to a new instance. If other instances don't approve, they can blacklist it.

Re: Mastodon.technology Shutdown

#328

Post by Jon_Lowtek »

EarlKing wrote: post #253
wizzwizz4 wrote: post #151

Earlier quoted context omitted.

Unlike email, the Fediverse hasn't been captured by a few large organisations. So long as we take measures to ensure that this doesn't happen, "go somewhere else" will always be a viable solution to complaints about an instance's moderation. I disagree with moderation decisions made by many instances, but if they made no moderation decisions, I would not be able to use the Fediverse. So I'm glad of it, even if it's a…

"Go somewhere else" isn't a solution when a plurality of servers agree to tolerate racist, sexist, or just plain obscene conduct. I'm also amazed that giving users control over what they see isn't an option. That solves the problem completely by making it the user's problem. That, however, somehow never seems to be an option.

> I'm also amazed that giving users control over what they see isn't an option.

so... you never actually used Mastodon? Its users do have the ability to filter content based on keywords, accounts or domains.

Re: Mastodon.technology Shutdown

#329

Post by riffic »

noirscape wrote: post #25
berkes wrote: post #15

Earlier quoted context omitted.

The tech also doesn't help. It's a "typical" Rails application: large, convoluted, lot's of moving parts, and services, and generally slow as molasses (solved by throwing more hardware at it). As experienced Rails dev(ops), I managed to run and help run an instance, but it's not something done on a friday afternoon, let alone scale up. What we really need in this landscape is dead simple services. I'm thinking about…

There are plenty of other choices. Pleroma[1] is probably the biggest competitor and is lightweight enough that you can deploy it on a raspberry pi. It's written in Elixir which takes a bit to set up, but the devs offer OTP releases that don't require you to have Elixir installed to use it and are the closest to "single file" deployment you get. Resourcewise it takes up only a fraction of what Mastodon demands in ter…

> There are plenty of other choices.

There's even WordPress, with a plugin.

A lot of ~~people~~ entities such as companies, organizations, etc have a WordPress site.

edit: Pretend this site supports basic formatting in comments?

Re: Mastodon.technology Shutdown

#330

Post by ByThyGrace »

qznc wrote: post #63
cmeacham98 wrote: post #44

Earlier quoted context omitted.

Look, I like open source federated ecosystems like Mastodon, but claiming Twitter or Facebook will be shut down any time soon is laughable. I'm not sure I could reliably predict whether Twitter or Mastodon will live longer.

Let’s use Google+ as an example. It did shut down and still not all wounds have healed yet. For example, the indie RPG scene laments its demise. Edit: A Reddit thread as citation https://www.reddit.com/r/rpg/comments/udegsl/does_anyone_hav...

TIL about .compact on reddit threads. Thanks!
Post reply on HN