Folks, the reason #Facebook/ #Instagram/ #Meta/ Zuckerberg hasn’t launched #Threads in the #EU isn’t because the EU is determined to protect your privacy, it’s because the EU is determined to protect The Single Market (peace be upon it) from anticompetitive behaviour. It’s because they’re using Instagram to launch Threads and sharing data between them (and not with EU startups that might want to use that data too). It’s #antitrust, not #privacy. It’s markets, not people.

#DigitalServicesAct

By the way, it’s possible that #Facebook/ #Instagram/ #Meta/ Zuckerberg’s fediverse play for Threads is related to sidestepping the anti-competitiveness/antitrust issues around the EU’s Digital Services Act.

“Hey, look, we’re not a monopoly. We’re not being anticompetitive… we’re federating using an open protocol. Here, let our friend Eugen, CEO of Mastodon, explain to you how it works in very dispassionate words…”

#eu #ec #fediverse #mastodon #antitrust #DigitalServicesAct #PR #usefulIdiots

@aral (off topic, but # after / does not work for tags, you need to insert some kind of space, even an invisible one, here it is for you: > /‌# < copy-pasting this should give slash-hashes that tag properly)
@oblomov Thanks for the heads up but that sounds like a bug in Mastodon.

@aral

my understanding is that it's an intentional choice

https://github.com/mastodon/mastodon/issues/1910#issuecomment-294348051

Hashtags directly after / don't become links · Issue #1910 · mastodon/mastodon

See this post here for a demo: If you type a hashtag (eg: #hashtag) directly after a forward slash (/) it doesn't become a clickable link. I feel like it should! [Yes] I searched or browsed the rep...

GitHub
@oblomov @aral isn’t that a basic in-page reference link? NOT making that a hashtag is a feature IMO not a bug
@sivy @aral it could be designed in such a way that hashtag is recognized when the stuff up to the slash is not recognized as a link, although that would reduce consistency