[-] thenexusofprivacy 4 points 6 months ago

Interesting, my first reaction is that I also wouldn't have expected it but as you say there's a lot of room in the Fediverse. In Seven Theses On The Fediverse And The Becoming Of Floss, Aymeric Mansoux and Roel Roscam Abbing talk about the Fediverse as "a site for online agonistic pluralism", and this is a good example - radically different views coexisting.

[-] thenexusofprivacy 4 points 6 months ago

Thanks, I'll include something about Hubzilla's progress ... the proof of concept Faircamp integration is interesting, do you know if anybody's following up on it?

[-] thenexusofprivacy 4 points 6 months ago

Yeah, right now the way I think of it is that Bluesky is (conceptualy) a single big instance, connected to the rest of the ActivityPub fediverse via Bridgy Fed (which speaks both AT and ActivityPub). Bluesky's decentralized in a different way, and the broader ATmosphere (apps that use AT protocol) is growing as well, but it deosn't really have the same concept of instance.

[-] thenexusofprivacy 4 points 6 months ago

Agreed that there's a difference between funding and other kinds of engagement -- and a difference between initial funding to get them off the ground. Right now it's not exactly clear what funding Meta's contributed and what the longer-term plans are. One of the other polls in the thread was about transparency, and (at least so far) 90% of the respondents are saying that SWF should be transparent about the funding it's getting from Meta. And, another poll zeroes in on funding and has different options for initial and up-front, and whether or not there are any strings attached.

[-] thenexusofprivacy 4 points 7 months ago

The Bridgy Fed dev didn't get browbeaten into anything, he thinks the opt-in approach is better (and I agree). And he's also said the backlash was probably deserved.

[-] thenexusofprivacy 4 points 8 months ago

Thanks for pointing that out! But, I got enough pushback on the wording of point 2 that I changed it to just "Think before you post"

[-] thenexusofprivacy 4 points 8 months ago

The previous post that I linked to is now down to -70! Discussions about racism often make people very uncomfortable. Thanks for all your responses in the thread that came from this, one of the commenters blocked me so I can't respond directly to them, but I greatly appreciate it!

[-] thenexusofprivacy 4 points 8 months ago

Thanks for the pointer.

[-] thenexusofprivacy 4 points 8 months ago

Good point, thanks. I seem to recall another one as well -- although both were widely defederated so I suspect most people on those instances didn't wind up seeing them.

[-] thenexusofprivacy 4 points 9 months ago

Thanks for making the effort to research it ... there are some great examples in this thread and some of the cross-posts (although some were so egregious that the mods took them down). Also, did you follow the links at the beginning of the article? They're talking about Mastodon (I'll include some examples from Lemmy in the revised version) but give an idea o the overall dyamics. In any case, I'll put in a big more about the problem in the revised draft.

[-] thenexusofprivacy 4 points 1 year ago

Mutuals-only posts would be useful, and have been requested since 2018 if not earlier. As @ShittyKopper points out there are challenges; Claire's 2020 comment https://github.com/mastodon/mastodon/issues/7135#issuecomment-636767048 discusses the issues in more detail. Then again some other fediverse software has them already ... and Claire's comparison to follower-only posts highlights that it could be done, it's just not a priority. So this is another good example of something that's not likely to get addressed with today's structure, and potentially could be a fork with different priorities -- if resources are avaialble, which is of course a big if.

109
How to block Threads on Mastodon (privacy.thenexus.today)
submitted 1 year ago* (last edited 1 year ago) by thenexusofprivacy to c/mastodon@lemmy.world

Should the Fediverse welcome its new surveillance-capitalism overlords? Opinions differ! If you're one of the fediverse influencers who sees Threads arrival it as "historic" and "a glimpse of the future" ... well, you might want to skip this post.

But if you're one of the many many people on the fediverse who doesn't want to deal with Threads, read on!

5
How to block Threads on Mastodon (privacy.thenexus.today)
submitted 1 year ago* (last edited 1 year ago) by thenexusofprivacy to c/thenexusofprivacy

Should the Fediverse welcome its new surveillance-capitalism overlords? Opinions differ! If you're one of the fediverse influencers who sees Threads arrival it as "historic" and "a glimpse of the future" ... well, you might want to skip this post.

But if you're one of the many many people on the fediverse who doesn't want to deal with Threads, read on!

32
submitted 1 year ago by thenexusofprivacy to c/fediverse@lemmy.world

There's another wave of discourse about The Bad Space on the microblogging side of the fediverse, so here's my article from a couple of months ago.

If you're familiar with Fediseer, there's some discussion of similarities and differences in Compare and contrast: Fediseer, FIRES, and The Bad Space

109
submitted 1 year ago by thenexusofprivacy to c/privacy@lemmy.ml
107
submitted 1 year ago by thenexusofprivacy to c/fediverse@lemmy.world

A really interesting look at the recent spam wave.

69
Steps towards a safer fediverse (privacy.thenexus.today)
submitted 1 year ago by thenexusofprivacy to c/fediverse@lemmy.world

The good news is that there are some straightforward opportunities for significant short-term safety improvements. If fediverse funders, developers, businesses, and "influencers" start prioritizing investing in safety, the fediverse can turn what's currently a big weakness into a huge strategic advantage.

Contents:

  • It's about people, not just the software and the protocol

  • It's also about the software

  • And it's about the protocol, too

  • Threat modeling and privacy by design can play a big role here

  • Design from the margins – and fund it!

2
Steps towards a safer fediverse (privacy.thenexus.today)
submitted 1 year ago by thenexusofprivacy to c/thenexusofprivacy

The good news is that there are some straightforward opportunities for significant short-term safety improvements. If fediverse funders, developers, businesses, and "influencers" start prioritizing investing in safety, the fediverse can turn what's currently a big weakness into a huge strategic advantage.

Contents:

  • It's about people, not just the software and the protocol

  • It's also about the software

  • And it's about the protocol, too

  • Threat modeling and privacy by design can play a big role here

  • Design from the margins – and fund it!

10

Detailed reporting on the sleazy tactics suveillance hawks in Congress used to sabotage this week's vote on FISA Section 702 reform. It really is a bipartisan issue: the the House Intelligence Committee's Chair Mike Turner (a Republican) and Ranking Member Jim Himes (a Democrat) worked together on this, although Himes is now trying to distance himself.

46
submitted 1 year ago by thenexusofprivacy to c/lgbtq_plus@beehaw.org

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.

154
submitted 1 year ago by thenexusofprivacy to c/technology@lemmy.ml

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.

17

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.

20

They've unveiled a new version, with some improvements. Fight for the Future's statement (not quoted in the Washington Post, of course, which is a mouthpiece for tech) says "we are glad to see the attorney general enforcement narrowed" but also notes that "As we have said for months, the fundamental problem with KOSA is that its duty of care covers content specific aspects of content recommendation systems, and the new changes fail to address that." So it's still a bad bill.

But just because they're claiming they have the votes in the Senate, it's not a done deal yet -- and it still has to go through the House. So, if you're in the US, call your legislators! https://www.stopkosa.com/

[-] thenexusofprivacy 4 points 1 year ago

As you say though it's only shared to any other instance listening. The point of consent-based federation is that you get to choose which instances do and don't get to listen. So if your comment hasn't been sent out out to other instances, they don't have it.

view more: ‹ prev next ›

thenexusofprivacy

joined 1 year ago
MODERATOR OF