@mahmoudajawad@mastodon.online
2023-07-04 07:36 UTC
Replies (6)
-
@simon_lucy@mastodon.social 2023-07-04 07:47
@mahmoudajawad@mastodon.online @clifff@shakedown.social @Gargron@mastodon.social There are no DMs on Mastodon instances.
-
@codefolio@ruby.social 2023-07-04 12:33
@mahmoudajawad@mastodon.online @clifff@shakedown.social @Gargron@mastodon.social An awful lot of Mastodon data is simply not locked behind anything. Blocking the Threads app won't do much in that case. The screenshots above are Threads asking the user's phone for data stored on that phone, and won't affect other users. Not saying it's not a problem. But it shouldn't affect any user other than the one installing Threads. It's around as intrusive as TikTok or Facebook.
-
@TheActualBrian@mastodon.social 2023-07-04 13:14
@mahmoudajawad@mastodon.online @clifff@shakedown.social @Gargron@mastodon.social So, the app that's likely to bring in tons of people, just block that because you don't like the app that you don't have to use unless you block them...?
-
@corn@eldritch.cafe 2023-07-04 13:25
@mahmoudajawad@mastodon.online The best way to prevent that is to move off mastodon.online into an instance that has signed the https://fedipact.online. @Gargron@mastodon.social seems to *want* Meta to join in considering his behavior. And he operates both .social and .online @clifff@shakedown.social
-
@mike@sauropods.win 2023-07-04 15:33
@mahmoudajawad@mastodon.online @clifff@shakedown.social @Gargron@mastodon.social If you want to have conversations that should not be public, then Mastodon is 100% the wrong place to have them. That's true already, nothing to do with Facebook.
-
@dragonfrog@mastodon.sdf.org 2023-07-04 18:18
@mahmoudajawad@mastodon.online @clifff@shakedown.social @Gargron@mastodon.social Isn't developing a whole new service and recruiting their users to join it the hard way? Vs quietly setting up an instance of an existing fediverse product as the easy way?