(#hfal6kq) So let's openly discuss this. cc @lyse @movq who have had strong (IIRC) opinions on this in the past, our existing pod owners @laz @jlj @adi @fastidious @eldersnake and to our brand new (Welcome!) pod owner @meff

(#hfal6kq) If the complexity and upkeep far outweighs the usefulness and utility, I vote removal. Don't get me wrong, I've used the feature plenty of times, but reducing code complexity, bugs and making people be a little more mindful and literally "thinking before they post" might not be a bad thing 😅

(#hfal6kq) @eldersnake 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

(#hfal6kq) I vore againt removing the edit and delete feature! If I'm the minority here then it should at least be replaced with a preview before posting similar to some shuttlebutt clients and a waring that you can not undo this after you pressed send.

(#hfal6kq) I think that it'd be better to remove it (it doesn't work well enough to justify it being a thing), but I 100% agree that there should be a preview thing, to let users check that their pictures, links and markup work correctly (especially since the markup buttons in app still don't always do what they should) and just see it in this new way, so they can read it again in this new way and have one last chance to notice the typos. *This should be a button, not something that has to happen before every post is sent - obviously.

(#hfal6kq) it should be state cleary somewhere that you can always ask the podamin to manually remove a post from your twtxt.txt if needed. otherwise we might conflict with GDPR. it could be on a Getting started or FAQ page.

(#hfal6kq) @darch Can you clarify the GDPR and link and/quote the relevant section? 🤔

(#hfal6kq) @prologic In regards to GDPR I was thinking of the Right to rectification and the [Right to erasure (‘right to be forgotten’)]()

(#hfal6kq) @darch Hmm 🤔

(#hfal6kq) @darch 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.