Also SmokeSignal events https://smokesignal.events/

I saw a talk by the peole working on FrontPage last week, they use the Bluesky Relay, filter it down to only see the posts they're interested it, and have their own AppView. It doesn't yet have the same kind of intereoperability with Bluesky that Lemmy does with (say) Mastodon; FrontPage posts are only visible to FrontPage. But, there are discussions on how to get beyond that.

Good point, thanks. It's great that mods are blocking sources of racism, although also means that people who don't see can wind up thinking that there isn’t any racism.

[-] thenexusofprivacy@lemmy.blahaj.zone 3 points 3 weeks ago* (last edited 3 weeks ago)

Thanks, it's a great example, and good to hear they got banned quickly! It's a great point that when moderators are proactive most people don't see the posts so think there's less racism than there actually is.

That's a great point, can I quote you on having seen it on Lemmy quite a few times?

[-] thenexusofprivacy@lemmy.blahaj.zone 4 points 1 month ago* (last edited 1 month ago)

From the article

Dr. Johnathan Flowers' The Whiteness of Mastodon, Ra’il I'Nasah Kiam and Marcia X's Blackness in the Fediverse, and the links in Dogpiling, weaponized content warning discourse, and a fig leaf for mundane white supremacy have some of the history.

Preemption is bonkers from a privacy perspective, and also flies in the face of the basic principle that the states are "the laboratories of democracy." But from a corporate perspective preemption is wonderful ... it keeps pesky pro-privacy states like California and Washington from ever raising the bar above whatever can get through Congress! So historically privacy advocates and organizations have always opposed preemptive federal legislation. But that wall cracked in 2022, where EPIC Privacy joined pro-industry privacy orgs like Future of Privacy Forum to support a preemptive bill (although EFF and ACLU continued to oppose the preemptive aspects).

The argument for supporting a preemptive bill (not that I agree with it, I'm just relaying it) is that the federal bill is stronger than state privacy bills (California unsurprisingly disagreed), and many states won't pass any privacy bill. Industry hates preemption, industry hates the idea of a private right of action where people can sue companies, most Republicans and corporate Democrats will do what industry wants, so the only way to pass a bill is to include at most one of those. So the only way to get that level of privacy protection for everybody is for people in California, Maine, Illinois, etc, to give up some of their existing protection, and for people in Washington etc to give up the chance of passing stronger consumer privacy laws in the future. California of course didn't like that (neither did other states but California has a lot of votes in Congress), and Cantwell's staffers also told us in Washington that she was opposed to any preemptive bill, so things deadlocked in 2022.

With this bill, I'm not sure why Cantwell's position has changed -- we're trying to set up a meeting with her, if we find out I'll let you know. I'm also not sure whether the changes in this bill are enough to get California on board. So, we shall see.

A very good idea! https://startrek.website/ took this approach, it'd be intersting to check in with them to see what they learned.

41

KOSA's supporters are claiming that the latest version addresses concerns from the LGBTQ community, and a few LGBTQ organizations (including GLAAD and HRC) have endorsed this version, but don't be fooled: the dozens of LGBTQ and human rights organizations who have been opposing KOSA were not consulted about these changes and so while there are improvements, it's still far from sufficient. This article's EFF's take on the amended version. TL;DR summary:

  • LGBTQ+ Youth will be at risk of having content, educational material, and their own online identities erased.
  • Young people searching for sexual health and reproductive rights information will find their search results stymied.

We are asking everyone reading this to oppose this latest version, and to demand that their representatives oppose it—even if you have already done so.

150

EFF's take on the amended version of KOSA. TL;DR summary:

We are asking everyone reading this to oppose this latest version, and to demand that their representatives oppose it—even if you have already done so.

19

This is the just-released unclassified version of the Privacy and Civil Liberties Oversight Board's December 2020 classified report on the National Security Agency’s (NSA’s) use of XKEYSCORE, an intelligence analysis tool.

Fediblockhole does something along those lines for on Mastodon ... not sure if there's an equivlaent in the Lemmy world.

39

cross-posted from: https://lemmy.blahaj.zone/post/7992691

There are some straightforward opportunities for short-term safety improvements, but this is only the start of what's needed to change the dynamic more completely.

This is a draft, so feedback welcome!

48

A deep dive into the Data Protection Review Court by Alfred Ng and John Sakellariadis, including some great perspectives from Max Schrems of noyb.eu

They don't, at least not from your instance.

I can't speak for others but yes, I want a fediverse that doesn't have white supremacists and fascists.

36

cross-posted from: https://lemmy.blahaj.zone/post/7477620

Transitive defederation -- defederating from instances that federate with Threads as well as defederating from Threads -- isn't likely to be an all-or-nothing thing in the free fediverses. Tradeoffs are different for different people and instances. This is one of the strengths of the fediverse, so however much transitive defederation there winds up being, I see it as overall as a positive thing -- although also messy and complicated.

The recommendation here is for instances to consider #TransitiveDefederation: discuss, and decide what to do. I've also got some thoughts on how to have the discussion -- and the strategic aspects.

(Part 7 of Strategies for the free fediverses )

77

cross-posted from: https://lemmy.blahaj.zone/post/7371919

There's likely to be a lot of moving between instances as people and instances sort themselves out into the free fediverses and Meta's fediverses -- and today, moving accounts on the fediverse today. There are lots of straightforward ways to improve it, many of which don't even require improvements to the software. And there are also opportunities to make creating, customizing, and connecting instances easier.

(Part 5 of Strategies for the Free Fediverses )

46

cross-posted from: https://lemmy.blahaj.zone/post/7235896

Here's how Kat Marchá describes caracoles:

"you essentially ask to join concentric federations of instances ... with smaller caracoles able to vote to federate with entire other caracoles.

And @ophiocephalic's "fedifams" are a similar idea:

Communities could align into fedifams based on whatever conditions of identity, philosophy or interest are relevant to them. Instances allied into fedifams could share resources and mutually support each other in many way"

The idea's a natural match for community-focused, anti-surveillance capitalism free fediverses, fits in well with the Networked Communities model and helps address scalability of consent-based federation.

Yes, I'd say Lemmy communities are cross-instance communities - people can join communities on a different instance than their account.

101

cross-posted from: https://lemmy.blahaj.zone/post/7193618

The "free fediverses" are regions of the fediverse that reject Meta and surveillance capitalism. This post is part of a series looking at strategies to position the free fediverses as an alternative to Threads and "Meta's fediverses".

On Lemmy? Certainly not. But on other fediverse software, there are followers-only posts, direct messages, local-only posts ... none of it's encrypted, but still it's not public.

61
view more: ‹ prev next ›

thenexusofprivacy

joined 8 months ago