👋 Q&A: Let’s discuss the removal of Editing and Deleting your last Twt. This is something @fastidious@twtxt.net has raised to me on IRC and something I find quite a valid approach to this. Over time I believe the utility and value of “Editing” and “Deleting” one’s last Twt isn’t as valuable as we’d like and increased complexity and introduces all kinds of side-effects that are hard to manage correctly. I vote for the removal of this feature from yarnd, the mobile app nor API support this anyway…

So let’s openly discuss this. cc @lyse@lyse.isobeef.org @movq@www.uninformativ.de who have had strong (IIRC) opinions on this in the past, our existing pod owners @laz@tt.vltra.plus @jlj@twt.nfld.uk @adi@f.adi.onl @fastidious@twtxt.net @eldersnake@yarn.andrewjvpowell.com and to our brand new (Welcome!) pod owner @meff@yarn.meff.me

@eldersnake@yarn.andrewjvpowell.com FWIW I used it a fair bit too, but I am quite mindful of being quick about a last minute edit (literally!) so there is that aspect as well. Once a pod or client fetches your feed, it’s all but too late! 😂 So the “utility” is highly questionable at this stage as we continue to grow 😅 IHMO

@darch@twtxt.net Can you clarify the GDPR and link and/quote the relevant section? 🤔

@darch@twtxt.net Hmm 🤔

@darch@twtxt.net Imho articles 16 and 17 relate primarily to data that is of a personal nature. I think the intent of those particular articles is not applicable to yarn as yarn collects and stores NO data of a personal nature- not even email addresses.
the articles do not specifically address opinions and the like which on other platforms are strongly linked to user’s personal information.

@darch@twtxt.net if a post contained personal information, this would be in violation of Yarn’s privacy and abuse policy. of course the pod admin could delete it. however as all things on the web… once it’s out there it’s difficult to contain. we could have a ‘dumbass’ clause that explicitly states ‘ Do not post personal or sensitive information on the web.’ 🤪

@ionores@twtxt.net hey you’re still alive! good to see you again!

@prologic@twtxt.net So, there is an API! This is offtopic for the thread (sorry) but can you link me to its documentation? I’m thinking about creating a single-user barebones “pod”, compatible with the mobile app but that manages a single twtxt file.

Yeah, removal+preview here too

@marado@tilde.pt https://dev.twtxt.net — But see my other replies 😁

@fastidious@twtxt.net I like the timer approach 👌

@fastidious@twtxt.net Yhe timer can actually just reuse the I/—fetch-interval 👌

@fastidious@twtxt.net I would do it like this, you can edit or delete your last Twt as long as:

• it hasn’t already been replied to on that Pod
  
• it hasn’t already been fetched by remote clients

@movq@www.uninformativ.de More just the implementation. Dsleting very old Twts from a feed is “okay”, can still break threading potentially but isn’t as big of a deal as “in flight” threads IMHO

@lyse@lyse.isobeef.org Interesring point 👌 Thanks for making it! 🤗 Perhaps we can consider rewriting the function DeleteLastTwt() to just DeleteTwt() — At worst it’s an O(n) scan of the backing Twtxt file, deleting from the Cache is already possible 👌

@movq@www.uninformativ.de Noted 👌

@fastidious@twtxt.net Hmmm given very strong and very valid opinions here in this thread I’m not sure we should bother with the idea of a “Timer” 🤔

@xuu@txt.sour.is Oh? 🤔 Is this Twt’s position exposed somewhere I can use in a new func DeleteTwt(conf *Config, feed string, twt types.Twt) error? 👌

@fastidious@arrakis.netbros.com

There should only be one captain per ship. You have the helm! 😊

That may be all well and good, but as my intentions have always been to run Yarn.social as a not-for-profit with a community “foundation” that runs/organises it, I’m not strictly speaking the “captain” per se. I should have to respect the opinions and voices of all involved 😅

Okay folks, how about this as a counter proposal:

• You can edit or delete your last Twt as long as:
  
  • it hasn’t already been replied to on that Pod
    
  • it hasn’t already been fetched by remote clients
    
  • otherwise the UI will remain the same, only showing “Edit” / “Delete” on
    your last Twt if the above conditions are met.
    
• You can edit and sync your feed via the yarnc sync (TBD) command or via the
  API /api/v1/sync (TBD) – Which is something I want to support anyway for
  backup purposes, import and enhanced flexibility, for example using a
  different command-line client like tt or jenny but syncing your feed to
  your Yarn hosted account on some Pod.
  

Thoughts? How does this sound in general @lyse@lyse.isobeef.org / @darch@twtxt.net re GDPR? 🤔
How does this sound UX wise to you @fastidious@twtxt.net / @thecanine@twtxt.net ?

@fastidious@arrakis.netbros.com Good point

@lyse @darch@twtxt.net @fastidious@twtxt.net @thecanine@twtxt.net @prologic@twtxt.net Seems to me that the sync is only useful if it allows a lot more editing (eventually even a complete rewrite). Which I am all for, but then the edit/deletion restriction on the UI becomes sort of an hassle, as someone more tech-savvy will be able to do things that less tech-savvy users will not…

With further discussion on #yarn.social on IRC I believe we have resolved this:

• Add support for Edit/Delete everywhere.
  
• Add support for yarnc sync and /api/v1/sync API endpoint.
  
• Revert to old Cache behaviour of overwriting cached feed entries (DONE).
  
• Stop worrying about the very rare occasion an Edit splits a thread.
  

#resolved

@fastidious@arrakis.netbros.com It actually won’t be that hard to implement honestly. The hardest part will be the UI/UX which I know I’ll do a terrible job of 😂

@adi@f.adi.onl

So no removing of Delete last twt, but Edit/Delete any twt?

The UI/UX will change slightly. There will be no “Edit” or “Delete” buttons/links on your last Twt anymore. Instead there will be an ellipsis drop-down ⠇ with 3 options: “Share | Edit | Delete”.

@adi@f.adi.onl Yes

Whoa. Had my head down in a problem this evening (that, happily, I think I’ve resolved). Good discussion. Sounds fine to me.

@jlj@twt.nfld.uk 👌

@darch@twtxt.net Cool appreciate it! 🤗

What will the share do?

I don’t know! 🤣 But on the mobile app it copies the link to the Twt to the clipboard. I’m afraid doing something similar on the Web frontend is going to require a little JS 😅 But there’s already a non-JS way of copying the Permalink to a Twt so that shouldn’t freak out too many folks that don’t enable JS or use JS-free browsers.