Conversation

Notices

Embed this notice
iced depresso (icedquinn@blob.cat)'s status on Tuesday, 21-Apr-2026 19:46:31 JST iced depresso
in reply to
- Strypey
@strypey i can't believe content i published on the internet can be read.

In conversation about 4 days ago from blob.cat permalink
- Embed this notice
  Strypey (strypey@mastodon.nzoss.nz)'s status on Tuesday, 21-Apr-2026 19:46:33 JST Strypey
  
  The Public Not Public self-delusion rides again *sigh*;
  https://www.loomio.com/d/ASGoq9TQ/zeitgeist-and-other-fediverse-llms/112
  Putting aside the technical reality (which is unwise), what it boils down to is this; do you want to be able to speak to a global audience, with all the opportunities and privileges that come with that?
  (1/?)
  #PublicNotPublic
  In conversation about 4 days ago permalink
  Attachments
  1. Domain not in remote thumbnail source whitelist: loomio-uploads.s3.amazonaws.com
    
    Zeitgeist and other Fediverse LLMs
    
    Last week Laurie Voss announced that he’d released a new Mastodon client called Zeitgeist.blue, “a multi-social-network app that summarizes your feed for the last 24 hours.” As a Mastodon client, it appears to authenticate a given user with an existing instance (including social.coop, potentially) and, using Anthropic or GitHub Copilot, processes timelines for the purposes of summarizing one’s timelines using a large language model (LLM).Many replies to the announcement were critical of the project and took issue with the lack of consent and being subjected to AI surveillance. Voss was dismissive of those concerns, referring to people complaining about the lack of consent mechanisms as “tedious bastards,” and began blocking people replying in the thread.Voss was informed of an existing precedent for people to tag their bios in order to opt-out and subsequently added an opt-out for people who do not want their posts indexed. Initially Zeitgeist indexed everything, including DMs and follower-only posts, but now DMs are filtered out. There is also unique “User Agent” metadata that accompanies requests and theoretically could be used to block requests as an instance, if we chose to take that route.I’d like to start a discussion here of how the cooperative would like to handle this, or other projects that engage in trawling content and processing posts using LLMs. Setting aside the chaotic launch of this one project, do you feel okay with AI systems harvesting posts and training LLMs?Some related essays that might be helpful for thinking about this with:Eight tips about consent for fediverse developers by Jon PincusAdventures in Mastoland by Jan Lehnardt

Public

Conversation

Notices

Feeds