@movq@www.uninformativ.de ha ha in this case I think I’m OK with a broken thread ha ha

@prologic@twtxt.net See, that’s what edit/delete is good for. 😅🤪

@movq@www.uninformativ.de yeah it’s one of the fundamental principles of Yarn social and everything that I’ve poured into the ecosystem that we’ve collectively built here over the last, What is it six or seven years now?

@zvava@twtxt.net oooos 🤣

@david@daiwei.me That’s a good thing. I still use it heavily, but I also realize that it is addictive. This whole idea of getting likes and boosts is horrible. Seeing “number goes up” is inherently addictive design, if you ask me. This should never have been added to a Free Platform like Mastodon, and I’m glad that twtxt doesn’t have anything like it.

@movq@www.uninformativ.de That’s crazy… Do not want!

@david@daiwei.me @prologic@twtxt.net No worries, I was just trying it on for size.

I played it again today (10/12 on first try), but I can’t say that I love the format of the “share link” (the unnecessary yellow and green circles).

I think if I did want to post daily scores or something (for posterity), I’d likely setup a separate feed just for my “achievements”. 😁

accidentally just pasted my twtxt.net password in the compose field

@misskatie@twtpub.com Awesome!!! Welcome 🤗

and I’m not really sure I’ll ever add an edit or delete button to be honest 🤣

Hmmm

also, just to clarify, we built the hosted Service as the last lowest rung ladder for non-technical people. I fully expect most technical people will spin up their own publishing backend or use Github or similar so that long-term the ecosystem still remains very much decentralized.

@balloon-fu-sen@tw.fus.f5.si yes I wouldn’t go and change your feeds location the location a fourth time that’s for sure! 🤣

Just finished putting together my new cwm setup!

@lyse@lyse.isobeef.org Ha, I technically never went too far, just haven’t been too actively posting admittedly :<

@david@daiwei.me Thank you! 🙏

@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. :-)