masterspace

This is not a matter of good vs bad, or right vs wrong. It is about expected vs unexpected.

Yeah, if you copy Twitter's UI users will expect it to behave like twitter.

It's not complicated, mastodon just kind of sucks from a user perspective compared to twitter while completely copying it, leading users to dislike it.

Decentralization is not a feature, it's an implementation detail.

And I've worked at FAANG companies developing their apps and am well aware of precisely what they do to get people to use them, and it's not make a carbon copy of twitter that's harder to use.

I think the spirit of the OPs comment is that it is the style of conversations, atmosphere and culture that each of them foster what makes them somewhat different.

If you want to organize discussion around topics, model it after reddit, where you subscribe to topics.

If you want to organize discussion around people, model it after twitter, where you subscribe to people.

Kbin and lemmy do a good job of modelling things after reddit, where you subscribe to topics. The decentralized nature just adds another layer of community duplication, but that was already a problem with reddit (r/gaming and r/games) and isn't that big a deal since all are subscribable from your preferred instance as long as it's federated with everyone.

The problem with Mastodon though is that it wants to model itself after Twitter where you subscribe to people, but unlike with topics, having duplicate copies of people is a real problem since it makes it hard to trust that you're actually subscribing to the right person and not a spam account. That is an extremely real problem that Mastodon tried to side step by pivoting to following topics, but at it's core the mastodon/twitter UX is not formatted for that, it's formatted for following people in real time and Mastodon seems like it has ignored that and is trying to insist that it's it's own thing that no one actually wants. Organizing discussion based around servers is not a user helpful format, it's exposing unwanted technical implementation details to the user in a way that only a tech nerd could ever love.

If you have to write a long ass post telling users that they're using your software wrong, then you wrote bad software.

Don't want people to think it's supposed to be Twitter? Don't model the entire UX after Twitter.

If you have to write a long ass post telling users that they're using your software wrong, then you wrote bad software.

Don't want people to think it's supposed to be Twitter? Don't model the entire UX after Twitter.

Signing an NDA to talk about an unreleased product is not predatory, it's standard practice for virtually any business (especially the kind inviting random people off the internet to see them). Many jobs require you to sign NDAs just to go through the interview process.

There is nothing gained by not going to the meeting with Meta, if they want to launch their Twitter clone they are more than capable of doing that regardless of whether or not this guy takes a meeting to hear them out. All he's done is learned less about what they plan on doing leaving him less capable of taking the best course of action, and if you trust him to make the right decision then that's objectively a bad thing.

Such bravery coming from someone who sounds oh so employed.

That's standard practice if you're going to be talking about an unreleased product.

Play Prey, and then if you like it and are itching for more, play the Prey DLC which was their first take on the time-loop-ish concept, but it's smaller and more stealth focused than Deathloop. Then if you like that and want something bigger with more style and less stealth, play Deathloop.

This is not a proper talk by meta that you could just "hear them out". They explicitly said off the record and confidential, there's no reason for that if it's something innocuous.

They plan on showing demos of their product to them or talking about potential features it might have. Boom, they require an NDA.

I don't think you understand how the professional world works or how common NDAs are. I've signed NDAs while going through interview processes at FAANG and other large companies just so that we can talk freely about projects I might work on. Especially for a company like Facebook where everything they do will get about a dozen news articles written, they're going to make you sign an NDA for any conversation about an unreleased product.

Imho, Arkane Studios games rank:

• Prey
• Dishonoured 1
• Dishonoured 2
• Deathlooop

and all were a fantastic time.

Though I haven't played Redfall yet due to the poor reception, I figure I'll wait til I'm bored in a year or so after they've had time to iron out some of the rougher edges.

Having a larger market = having a larger network = greater network effects for content

Having Meta join with Mastodon might actually sway people off twitter and into the fediverse where it will be easier to migrate over to a different instance.

It's foolish not to hear them out, you accomplish nothing. This isn't some silicon valley episode where he has some arkane secrets that meta engineers couldn't figure out that he might leak. Meeting with them is zero risk and he would gain more information on what they're planning.

In this case the American and Canadian coast guard spent resources trying to save people after they got into danger, and it sounds like the Greek coast guard might have spent resources keeping desperate people in danger until hundreds drowned.

The tragedy in Greece is an endictment of the Greek coast guard and western countries attitudes towards the developing world and refugees in general, but just because more people's houses are on fire elsewhere doesn't mean you shouldn't put out your own.