5 ms·
It is somewhat ironic that it (for now) has somewhat of an old school free software crunchy hippie feeling feel (which I'm personally always all for), because t
by jrm4 4y ago
It is somewhat ironic that it (for now) has somewhat of an old school free software crunchy hippie feeling feel (which I'm personally always all for), because the value to big companies feels like an absolute no brainer.
"Hey, see the stupid thing that happened to Eli Lilly? You know how you can actually just have your own email instead of gmail in your company if you pay for it? Also your own website? This is that, for what Twitter does."
Seems positively stupid for companies to NOT go in this direction.
- riffic 4y agothe problem is being able to pitch the wider ecosystem without sounding like a loon spouting technobabble. I'd love to pull off being able to sell this to normies.
- jrm4 4y agoAin't that the truth. I find that I'm the only one leading with essentially what I just said.
- unshavedyak 4y agoI think they (devs) just need to round out the rough corners with blacklisting, whitelisting, etc - because i think: > it's just like email, foo@gmail.com becomes @foo@gmail.com, that's it! Is pretty easy to sell. The issue there is that in any "real" email host (ie not in your closet) you have no problem[1] emailing another host. Yet with Mastodon it's rather dependent on the specific of platforms blocking rules. Which isn't to say that this is an indigestible concept for the average person; just that it's a rough edge, it needs some work, some transparency. Likewise how federation works is also a bit obtuse. The speed of nodes federating to each other feels inconsistent on a UX, and imo you should basically _never_ miss pieces of a conversation. Or at least if you do, it should be very clear that there is a blocked comment, or a yet-to-be-synced comment, etc. Right not it can just look like someone is replying to themselves or etc. Really though it's all quite solvable with some UX it seems. There's some tech issues too of course, but all together this feels quite a feasible "twitter but like email" tool. I'm quite happy with it, and i'm even happier to ignore Twitter. [1]: generally speaking of course. It's expected to just work.
- WorldMaker 4y ago> The issue there is that in any "real" email host (ie not in your closet) you have no problem[1] emailing another host. Spam filtering and intense host allowlists and denylists are just as bad in email. In many cases it is actually worse because the number of "real" email hosts has shrunken to a staggeringly small number (most of which are major corporations) in some situations and self-hosting can be quite fraught with hidden traps and accidental denylist penalties and an increasingly baroque maze of security standards like SPF and DKIM and… From that perspective Mastodon is currently far more open in federation than today's email. As much as anything "email is open" and "Fediverse is subject to blocks" is a marketing problem more than anything. Email as an internet foundation tech has decades of accidental propaganda versus reality. Mastodon has a lot of loud critiques from people that either don't want it to survive or have some other political game they are playing. > Likewise how federation works is also a bit obtuse. The speed of nodes federating to each other feels inconsistent on a UX, and imo you should basically _never_ miss pieces of a conversation. Or at least if you do, it should be very clear that there is a blocked comment, or a yet-to-be-synced comment, etc. Right not it can just look like someone is replying to themselves or etc. This is rarely a "speed" thing and in email analogy terms much more a "BCC" problem. Your instance was not BCCed on the other content. I remember ages of email when mailing lists were far more plentiful when these sorts of "BCC issues" were quite common. If your mailing list wasn't BCCed on a reply but then the reply of the reply BCCs it, there's an obvious missing piece in the conversation. Mastodon UX could absolutely improve, but in this case the instance generally has no idea there is a "yet-to-be-synced comment" because there isn't a "yet-to-be-synced comment", the instance never saw that comment because it wasn't BCCed on it in the first place. (Though yes, this analogy breaks down a small bit because some of the "mailing list" posts come from RSS-like feed syndication, but there also there's no easy way to "guess" what might be in a feed the instance hasn't synced.) Also, some of these BCC issues are intentional, for the same sorts of privacy reasons BCC itself exists in email. Mastodon offers some privacy settings for how far messages travel and some users don't want to "BCC the world" with some of their posts. There's never going to be a "complete view" of many conversations because people want some privacy in their conversations and Mastodon allows that.
- 4y ago
- danuker 4y agoThe Fediverse has a much smaller reach than mainstream social networks. Your target audience might not be on it.
- jrm4 4y agoFor now. That's kind of the point here.
- cody_coconuts 4y agoWon't a centralized platform always have a wider audience than a decentralized one? I think that's one of the hurdles that you have to get over by offering other advantages
- rsynnott 4y agoYes, that’s why everyone uses AOL for email rather than that faddish SMTP. More seriously, there’s nothing in particular that requires complete centralisation for success, though a future billion person ActivityPub network probably relies mostly on a few giant hosts (a la gmail) rather than millions of small ones.
- VyseofArcadia 4y agoI see shades of Google+ haunting the rhetoric surrounding Mastodon. The lesson we should have learned about alternative platforms is that they will attract power users and enthusiasts. These people will be very vocal about why everyone will switch to the next big whatever. A lot of enthusiasts and power users will switch, and a big flood of people comes over to the alternative platform like the tide coming in. But normal users don't really give a crap about Twitter politics. The people who don't think about Twitter as a community or wider thing and just want to retweet funny cat pictures or whatever. They'll never move. It is a lot of effort for something they just don't care about. And the enthusiasts? Well, now they're dealing with a fragmented community, where some of their contacts are on one service and some are on the other but a majority are on both because let's be honest, all the new Mastodon folks aren't burning their Twitter bridges behind them. They start out posting everything on Mastodon. Then they realize they're leaving lots of people out, and they start posting everything on both platforms. Then slowly, one post at a time, the laziness sets in and before you know it they're posting exclusively on Twitter and wondering whatever happened to that promising Mastodon thing. The tide goes back out.
- bsaul 4y agofunny enough, the trend for mail has actually been to use google for enterprise ( or equivalent) and stop hosting your email servers. i believe that could be a middleground : a mastodon server hosting service.
- SQueeeeeL 4y agoA centralized repository is inherently at odds with the federated nature of mastodon
- bsaul 4y agoJust because Google enterprise offers email hosting doesn’t make email itself centralized. Just the fact that the protocol is federated is enough to prevent abuses (since anyone who doesn’t like the abuse can self-host without any loss of feature or friction).
- rsynnott 4y agoThese already exist, though they tend to be community focused. There probably is a place for a corporate focused one.