@GabesArcade@gabesarcade.com I may be blocking that provider due to abuse from bots using VPN(s) – What was your last IP?

@david@daiwei.me I think yhwre was 😅

@david@daiwei.me I think it might be a bug i just fixed 🤞

@movq@www.uninformativ.de I can’t do Java ever again 🤣

Fair*

@movq@www.uninformativ.de Dair enough

😅 so my understanding is correct 😅

@dce@hashnix.club So let me get this straight… You want to store your feed on a Codeberg repo right? But you want to clone that repo down somewhere else to serve it on a different location. Right? And you’d like to use the Twtxt App (https://twtxt.app) to front all of this? Right?

@bender@twtxt.net LOL 😂

Actually… no. We can do something here maybe…

In theory, it’s Gitea anyway. So it should work.

@david@daiwei.me Yes, but then I have to create and maintain an account I’ll never use 🤣

@dce@hashnix.club Ahh! Let’s fix the 403 error then? I don’t have access to Codeberg, so I can’t reasily test. Can you walk me through what you tried and any other details? I’ll get this fixed.

@dce@hashnix.club You may also be interested in the Twtxt App and the little tiny twtd publishing backend? 🤔

@david@daiwei.me Of course 🤣 Incognito sessions store nothing once closed. 🤣

@movq@www.uninformativ.de @lyse@lyse.isobeef.org Are you clients remaining compatible with Hash v1 in case older clients are still well not upgraded? 🤔

@dce@hashnix.club which version of Twet are you using? I might see if I can get it updated for you.

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

@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 🤣

@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! 🤣

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

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.🙏

what feed was tha from?

@david@daiwei.me LOL 🤣

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

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