@david@daiwei.me Found it. Some bugs in the “claim limiter”. Fixing…

@david@daiwei.me Please write an issue for this 🙏 I don’t mind which way we go!

Ahh crap, I didn’t take any 😅

I see 🤔

I also set this to local years ago:

$ go env | grep TELEM
GOTELEMETRY='local'

When this came out I was also outraged. But it doesn’t go anywhere, there are no network connections. It is effectively “off” like this.

@lyse@lyse.isobeef.org Ahh yes, but tt has a “draft” mode right? You didn’t publish, then edit over and over did you? 😅

@lyse@lyse.isobeef.org LOL 😂

let’s just see if something like this crops up again.

I will very likely add a way to delete your feed(s) from the search engine, because I do thing that’s important. But as Art 17 points out, we can’t really guaranteed deletion in everyone’s caches around the planet haha 😆

The only place where this would be an issue is the Twtxt Search Engine – But as the GDPR also points out:

Art. 17

The one place the “it propagated and I can’t recall it” problem is legally acknowledged is Art. 17(2), and it explicitly scales to what’s technically feasible:

“…the controller, taking account of available technology and the cost of implementation, shall take reasonable steps, including technical measures, to inform controllers which are processing the personal data that the data subject has requested the erasure…”

Best-effort, given the technology. A decentralised, append-only, content-addressed feed is the available technology, and its limits are baked into the standard the law applies. Nobody — not the user, not you — is obliged to guarantee every cached copy vanishes.

So just because I enjoy this kind of thing (looking into laws and trying to understand them…):

GDPR is about roles, not ownership

There’s no property right in personal data under GDPR. The whole regime hangs on three roles:

• Data subject — the person the data is about.
  
• Controller (Art. 4(7)) — “the natural or legal person … which, alone or jointly with others, determines the purposes and means of the processing of personal data.”
  
• The rights in Arts. 16 and 17 are exercised by a data subject against a controller. They compel a third party to rectify or erase. They are not self-executing duties that a piece of software must expose.
  

That’s the key. In your architecture, for a user’s own posts about themselves sitting in their own feed on their own device:

• the user is the data subject, and
  
• the user is also the only person “determining the purposes and means” of that data.
  

There is no third party controller to compel. The “right to erasure” is a right to make someone else delete — and there is no someone else. It is satisfied the instant the user can change the file. A UI button is a convenience, not a legal requirement. Omitting it removes zero rights, because the data is a plain-text file the user can edit or delete by any means — editor, sed, git, their file manager. Full practical control is retained; nobody is being denied anything by anyone.

@david@daiwei.me you had to poke me, eh?

@david@daiwei.me You mean, you mean… like mowing down a whole rain forest in a thunderstorm’s brutal heat? :-?

Show us today’s rain. :-)

Now, that’s cool shit, I have to say! Discovering so many hidden sounds… With Fotric Acoustic Imager: https://youtu.be/CKJT_ECOsK4

@david@daiwei.me Hahaahaaahaaaaa, that was funny as heck, mate! I had to laugh really hard! :‘-D

@david@daiwei.me Hahaha, for sure. (But my observation wasn’t meant as a complaint.)

@david@daiwei.me 🤣

@david@daiwei.me :-D

@lyse@lyse.isobeef.org Yeah, okay, the default being local means it only stores this stuff offline. So they claim. I don’t trust this and I don’t want to go anywhere near it.

Wow, 79 new messages over night, similar numbers in the past days. Looks like we’re surfing a high-traffic wave again. :-)

@prologic@twtxt.net @david@daiwei.me Thanks! Hahaha, rest assured, it was not right from the beginning at all. I had to fix it over and over again.

Uuhh, nice, @eldersnake@we.loveprivacy.club is back!

@prologic@twtxt.net Perhaps somebody tried to register “yarn_secret_service”. 8-)

@prologic@twtxt.net Where’s the before picture!? :-D

@movq@www.uninformativ.de Yes, this is absolutely a no-go!

A long time ago when the first telemetry shitstorm happened, I added export GOTELEMETRY=off in my ~/.zshrc. But it doesn’t seem to be picked up at all (I actually call this sabotage!):

$ go env GOTELEMETRY
local

$ go env -w GOTELEMETRY=off
go: GOTELEMETRY cannot be modified

$ go telemetry off

$ go env GOTELEMETRY
off

@prologic@twtxt.net @david@daiwei.me I just want to bring up the following: From a data protection point of view, edits and deletions are important. But that’s about it, I will not join discussions on that topic. :-)

Nice!

based on this, it’s entirely possible that there may still be a subtle bug somewhere with the app

🤣

oh man, that voice dictation didn’t come out quite right I think it’s because I still have a cold

as upset repeatedly in the past and many debates and discussions, I don’t think there’s any other viable way to do, threatening in a purely decentralized way because I think you’re just create another set of problems that are probably likely far worse

and to be clear, I voice dictated that last reply so please excuse any miss speech to text recognition errors

@david@daiwei.me well I happen to agree because one of the fundamental problems is that you can’t have a tax file specification and assume that you can edit it freely by hand as a human and then clients that deal with that specification in machine possible mechanisms the two kind of conflict because humans get things wrong machines don’t

I don’t think I’m going to add edit and delete support in this app because I think it was a horrible mistake to add those features to a client 🤣

@movq@www.uninformativ.de please don’t waste your time to bugging this. I’ll figure out what’s going on with these new clients.🙏

@prologic@twtxt.net It’s from Gabe’s feed: https://gabesarcade.com/twtxt.txt

Yeah, lol, fuck off. Tried to reproduce that hashing issue, thus playing around with Go a little bit. And what did I find?

$ tree ~/.config/go
/home/user/.config/go
└── telemetry
    ├── local
    │   ├── asm@devel-devel-linux-amd64-2026-07-14.v1.count
    │   ├── compile@devel-devel-linux-amd64-2026-07-14.v1.count
    │   ├── go@devel-devel-linux-amd64-2026-07-14.v1.count
    │   ├── link@devel-devel-linux-amd64-2026-07-14.v1.count
    │   ├── upload.token
    │   └── weekends
    └── upload

4 directories, 6 files

It collects and uploads “telemetry” now.

No.

(Don’t tell me how I can turn that off. Not interested. This is a compiler and it wants to track me, without asking for consent. That’s a no-go.)

@david@daiwei.me It really is almost impossible to debug these hash issues. Only thing I can do is some trial-and-error, to see if I somehow end up at pmrf6ftxsdhr instead of ksou5aqw7w5a. So far, no luck. 😅

what feed was tha from?

@david@daiwei.me LOL 🤣

@kat@yarn.girlonthemoon.xyz Welcome back 🥳

@eldersnake@we.loveprivacy.club Ahh awesome! No worries mate! 🙌

@prologic@twtxt.net seems to be working just fine mate! Thanks for your efforts and especially making the upgrade painless.

@itsericwoodward@itsericwoodward.com Well I clearly suck 🤣 putt.day #62 ⛳ 22/12 +10
🟡🟢🟡🟡🔴🔴🟡🟢🟢🟢🟡🔴🔴🟢🟢🟢🟡🟢🟢🟢 +2
https://putt.day/s/b4UKsjw0olkS

Free daily 3D mini golf in the browser? I smell a new obsession…

putt.day #62 ⛳ 10/12 Eagle
🟡🟡🟡🟡🟡🟡🟡🟡🟡🟢
https://putt.day/s/1VAFIDIxqpbT

@prologic@twtxt.net 🧨🎉✨

@prologic@twtxt.net 🔥🔥🔥

Took me two days to clean this off properly 😳

I believe the tree that we stayed under was some kind of fig tree and on top of dropping little fig fruit and another little debris. I think we also got a bunch of butt poop and shit on top of the van’s roof. 🤣

had to clean a lot of gunk off the top of the van I have to wake up back from our holiday! 😱