Huh, now that's a first one here... Mastodon tells me there are two replies to my last "about today" post, but I can't see them. Neither logged in nor logged out, neither in online interface nor using elk.
Someone posting using "followers only" with me not following them? Something else? 🤔
[eda:] solved, likely comments from an instance my instance restricts/blocks (and I very much think that it's good that way!). Thanks to everyone who helped!
I did the requisite responsible reading about Threads federating, and I decided to domain block them after thinking about it.
Anybody who wants to view my public posts can still view them.
This is mostly an infosec account, and there's AFAIK zero infosec community presence on Threads.
I'm not really interested in helping Threads grow an infosec community presence.
I don't think there's any Mastodon admin ready for the network effects of several million users suddenly joining the network. There is shockingly little discussion about problems like coordinated inauthentic activity, which are going to come at that scale. I'm REALLY not interested in seeing or interacting in any way with chinese state disinformation campaigns lol
Mastodon servers and clients are held together by duct tape and prayers by people in their spare time. Threads is held together by people paid full time salaries at a large multinational corporation. Threads can make a better fediverse app and a better fediverse server than anything that currently exists. I think any future where people start downloading the Threads app as their default client to interact with the fediverse, and where people start using threads.net as their default server, is one that is very dangerous for the existence of the fediverse as a set of interoperable clients and servers built on open standards. I'm doing my part to make this as unappealing and as high friction as possible 🫡
fuck libs of tiktok, and fuck threads which is currently platforming them. The impact of accounts like Libs of TikTok on rolling back LGBTQ rights in the real world is a very good example of why network effects, discoverability, and social media amplification are dangerous.
Thanks to @jerry for letting people on this instance make this choice themselves. Having this kind of choice is a welcome change from other social networks.
@jerry@catbuttes@cxiao So if someone on future federated threads found my account and wanted to reply to a post of mine, would I see the reply if I don’t follow them? Will they be able to follow me? Will I see stuff from Threads boosted by a follow of mine?Still not clear to me after reading the doc. https://docs.joinmastodon.org/admin/moderation/#limit-user
Go for example on @mosseri and click on the three dot button to see the "block domain threads.net" button.
At this time I don't consider necessary or even wanted to do a server wide block on ecoevo.social. More so that as a science server, some people here might want to interact with Threads in the future (if following a Masto account from Threads is ever implemented).
"A limited account is hidden from all other users on that instance, except for its followers. All of the content is still there, and it can still be found via search, mentions, and following, but the content is invisible publicly."
Based on the post I linked to, I thought this would apply in situations where an admin blocks off a whole instance.
Debatte über Migration: Ramelow sieht Thüringen "am Limit"
Thüringens Ministerpräsident Ramelow schlägt Alarm: Sein Land sei angesichts steigender Flüchtlingszahlen am Limit. Sein Innenminister vermutet hinter dem vermehrten Zuzug von Migranten eine Kampagne Russlands.
Bluntly: If your instance doesn't have rules filtering links from the BBC (and a half a dozen other news sources), you cannot convince me that defederating from them does anything to make people actually safer.
Also if you are CW'ing all links to the #BBC regardless of content: that's yet another thing that weakens what CWs are actually for. As one disability advocate on here put it a while ago, you are taking a curb cut and using it as a skateboard ramp.
A #limit is a perfectly reasonable tool if you feel like you need it. It will prevent them from showing up (on mastodon) on the timelines of anyone who doesn't subscribe. It will keep them out of the public timelines.
But defederation is, as was pointed out, trying to punish them when we lack the institutional power to make that happen.
But what bugs me is that it feels a lot like attempting to punish them in the name of safety.
With nazi services that is clear. You can draw the line directly. Same with CSAM-heavy services.
If a service is spamming yours and causing an interruption the same thing applies.
But you are operating in the service of your users who are presumably mostly if not entirely adults. So how does this "protect your users" in a way that, say, limiting would not?
None of these instances, to the best of my knowledge, have blocked bbc links from being shared.
If somehow that weren't an issue but posts from the BBC were, then people can opt not to follow those who share such. Or if it is boosting transphobic content it can be handled through action on the person sharing the transphobic content.
Laut Medien fast 500 E-Autos auf brennendem Frachter
Laut niederländischen Medien sind auf der "Fremantle Highway" fast 500 E-Autos - weit mehr als bislang angenommen. Was das für die Entwicklung des Brandes und die Löscharbeiten auf dem Frachter bedeutet, ist unklar.
Hm so I've read a bit about threads on here and while I expected a mostly negative response to them federating with services like mastodon to me the topic is rather exciting.
I know some of my old Twitter pals outside the EU are already trying it and it'd be fascinating to interact with them without ever having to sign up for a service I do not want.
Furthermore as far as I understood @Gargron threads can not just creep into private data on your instance anyway.
Visto che a detta di @informapirata avrei interpretato male un annuncio innescando "polemiche miserabili", qualcuno di @devol sarebbe così gentile da spiegarmi cosa è stato annunciato su https://noblogo.org/devol/a-proposito-di-threads-threat-di-meta-su-mastodon e spiegarmi come si concilia il "blocco totale pubblico" di una community con la possibilità di "seguire migliaia di account", e come viene realizzato questo "blocco sbloccato"? Magari è una cosa così geniale che decido di farla anche io, ma per ora mi è incomprensibile.
Hello remote followers! If you're on a Mastodon (or other fediverse) instance that Fanglitch.space limits (what does that mean?), you can totally follow me and get my posts in your home feed, but unless I'm following you, I'm sorry but I'll never see your posts unless by chance. Yes, even if you mention me directly.
Reasons for instance limits can include too-large instances, lack of moderation, or content against the Fanglitch.space rules. If you want to know more, I suggest you speak to your admin.
I have an alt account at @bloodwrites and I may be able to see your mentions there, so you can always drop an additional @ in your replies, or just hit me up there so I can follow you back on Fanglitch.space.
Yes, it's a bit of a hassle, but that's federation.
Gerade gelernt, daß #Pixelfed standardmäßig pro #Instanz ein #Limit an registrierten Nutzern bei 1.000 setzt. In Worten: Eintausend. Läßt sich natürlich konfigurieren, aber gut zu wissen.
Rozeszła się plotka, że twórca Masto i kilka innych osób związanych z projektem rozmawiało z Meta, a nawet podpisała jakiegoś NDA z nimi. I że to na pewno oznacza że albo Masto zostanie sprzedane Zuckerbergowi, albo też stanie się coś tam innego (w sumie to nie wiadomo co), ale na pewno będzie to coś złego dla fedi 😅 I już podnosi się raban, i już jest nawoływanie do podpisywania petycji anti-Meta, już jest zachęcanie by ludzie zgłaszali adminom swoich instancji, by jak tylko Meta zacznie korzystać z ActivityPub to od razu ich blokować, itp. itd.
A ponoć chodzi o to, że Meta się szykuje do tego, by wpiąć się właśnie do protokołu AP. Czy to dobrze czy źle to nie wiem. Ale z tego co mi wiadomo, to ten protokół jest otwarty i KAŻDY może się do niego wpiąć, nawet spółka Zucka. Pytanie tylko jak go wykorzystają i co dalej z tego wyniknie. Ale straszenie powtórką z historii mariażu Google z XMPP jest.
Raz jeszcze. To szansa która może się szybko nie powtórzyć. Więc zgoda trzeba rozwijać techniki przycinania ruchu, ale nie odcinać się na ostro bez podjęcia próby wyssania użytkowników (żywych ludzi).
(Speaking personally) I think it has to do with recent rapid growth certainly. We do hope to catch bad actors before they can do enough damage - which is why an application process is a great curation system. As for sustainably growing moderation, I think we have growing moderation considerably fast (from around 6? to 36?).
We'd really like an option to gate out instances which we feel can issues like what limting does on Mastodon because our goal is not to close the gates for the people using Beehaw. (This is limiting on Mastodon : https://docs.joinmastodon.org/admin/moderation/#limit-server)
The potential role of a 3rd servers to mediate between Beehaw and Lemmy.world
As this #RedditBlackout accelerates the Fediverse experiment, I feel the urge... the need... to chime in with my 2-cents....
Beehaw defederating from lemmy.world and sh.itjust.works (beehaw.org)
Interesting bit of news for the threadiverse. All three of these are fairly large lemmy instances
ANNOUNCEMENT: defederating effective immediately from lemmy.world and sh.itjust.works
hey folks, we'll be quick and to the point with this one:...