Wow, the general public is smarted than I thought they were.
Internet-connected smart appliances are almost universally a bad idea. In some cases it is just extra features (like remote phone notifications when a laundry cycle ends) but it almost always involves tracking and vulnerabilities that you don’t way.
If there was a good local protocol I would be much more eager, but until Thread catches on it doesn’t really seem like there are great options.
So you own your own blog and content. You can host your blog in a Wordpress site, GitHub pages, Ghost, or wherever you want.
Sounds like it just pulls feeds from anywhere. Nothing specific about GitHub at all.
This is like saying that Google is a search engine for GitHub blogs 🤷 I mean it is, but it is also a much more general tool.
According to https://github.com/LemmyNet/lemmy/issues/1395 Lemmy sends WebMentions.
Regarding the edit:
what I should have said was providing a product in the same market. So the fact that’s its free might not be relevant and a free, instance of a decentralized social network could be considered in the same market as a commercial, centralized social network.
Again, I don’t think the exact product matters too much. Being in different markets can help, for example a Twitter Whistle would have a better argument than a Twitter Social Network. But for huge brands that are well known everywhere (like Twitter) the market difference tends to matter less.
I still don’t see twitter going after this single instance
Yes, it is unlikely. But definitely not impossible with things that Twitter has already done to try and push out Mastodon (like banning links). And if it does happen it will be devastating to the instance as changing domains is painful. So I’m just suggesting that it may be best to play it safe here to avoid possible problems down the road.
I am not a lawyer. But…
I don’t think selling matters at all. The problem is if someone could confuse it. “Is Twitter Down” is arguably very hard to confuse as it is clearly something about Twitter (telling if it is down), and it doesn’t seem to present itself as being made/run by Twitter. This is further supported by the “by ryan king” in the corner.
However if people often talk about #BlackTwitter as some subset of content on Twitter it seems entirely possible that people could think that blacktwitter.io could think that it is run by Twitter. If it was called something like thenewblacktwitter or blacktwitteralternative it would be less likely to cause this confusion.
Another angle that they may argue is that they have an official product called “Twitter Blue” and they could argue that people would believe that “Black Twitter” is also an official Twitter product.
The most important think to remember about Trademark law is that it is very much about consumer protection. It doesn’t give you exclusive rights to use your trademark, it just prevents people from using your trademark to make something seem to be from you.
On top of all of that being legally right isn’t the only thing that matters. If Twitter accuses you of Trademark infringement unless you want to hire a bunch of lawyers you are probably just going to do what they say.
WordPress is always a good option. They have a freeium hosted option at wordpress.com or you can run your own. You can also always move to another provider or host it yourself.
Tumblr is also big and popular and there are tons of smaller hosts like https://bearblog.dev/.
my feeling is that it is reasonable to have the sender of the message set the terms here
This is fundamentally impossible thanks to the analog loophole. The receiver can always copy down the message to a notepad, or just remember it. Exposing this mutual agreement is staying honest and make sure that it is understood by everyone involved.
It is important to remember that disappearing messages (in any application) are only helpful for people who you trust currently. (And until the messages are deleted.)
While I probably wouldn’t use a propitiatory client I have no real issues with it. You can always switch off if you feel that it isn’t respecting you, even if it is harder to verify what it is doing under the hood.
Basically having a federated and open protocol greatly mitigates the downsides of a proprietary client.