Time to remove two feeds that have not seen a single update for over a year. I reckon they’re just dead.

@david@daiwei.me Go ahead and grab something, mate!

@david@daiwei.me Cool! 😎 Though I think this can be improved somewhat.

@david@daiwei.me Might not have tested that path very well. Can you make a note of this on Gitea?

@david@daiwei.me you’re not missing anything. It is only set on grant / connection time. If you disconnect and reconnect, it should become an option. I haven’t figured out how to refresh capabilities.

@david@daiwei.me You’re not missing anything. It is set on grant / connection time. So disconnecting and reconnecting will give you that option. I haven’t figured out a way to refresh backend capabilities like this.

@movq@www.uninformativ.de Great, I had some cherries. :-)

Woah, this is absolutely crazy! Super interesting to watch. The precision with this tiny workpiece amazes me. Omega Seamaster Bracelet Machining Modification: https://youtu.be/t0iGXWcZxg8

@GabesArcade@gabesarcade.com You are most welcome! 🙏

@GabesArcade@gabesarcade.com twtd landed too 🥳 Hosted feeds (twtpub.com) and self-hosted twtd can publish # follow = now — the operator offers it with --allow-follows, then it’s the same toggle in Settings. Off by default at both ends 👌

Also a “Publish who I follow” toggle: writes # follow = + # following = N into your feed like yarnd does. Off by default (it is your social graph 🤔), and only on the GitHub/Gitea backends for now where the app owns the feed file. twtd next 🤞

@GabesArcade@gabesarcade.com Both 😅 Just shipped: Settings → Backup & restore. Export everything (or follows only) as a JSON file and import it back — or feed it any twtxt.txt and it’ll harvest the # follow = lines. There’s a copy-paste # follow = block in there too if you’d rather hand-edit 👌

@GabesArcade@gabesarcade.com So we going with an Import/Export feature? Or would you also like optionally to write # follow = into the feed too? 🤔 Can do either/or or both.

@david@daiwei.me This has now been fixed! 🎉

@GabesArcade@gabesarcade.com I think it would have to be specific to the App itself. So say you somehow didn’t save a recovery key or some shit™ You could still get back up and running with ease if you had exported a config? 🤔

Okay I’m fixing this in lextwt, yarnd and twtxt.app (takes a different path). Soon you’ll be able to write shit™ like (<this>) and it’ll get escaped and rendered correctly on the page. Basically you are really writing HTML here, but not intending to do so, Twtxt never supported HTML, and I don’t think it ever should. We extended the format to support basic Markdown, and I think that’s where it should end.

Probably time we wrote a Spec for this really.

Ahh no I was wrong. this is being stripped at the Markdown parsing level due to “unsafe” HTML. Which of course is a bit hard to tell between what is safe and unsafe HTML.

I think the problem here is that (i.e: <foo>) is being treated as HTML, which the browser renders as nothing, because that’s not even a valid element it understands how to render. Hmmm 🤔

@GabesArcade@gabesarcade.com Based on your description, I think it makes snse to have an Import/Export settings in the UI? RIght? 🤔

@david@daiwei.me Kk I’ll look into it 👌

@david@daiwei.me I mean we can probably do that I suppose. I’d make it an option in Settings though?

@david@daiwei.me I see it now. Is this also a problem in the app too? Or just yarnd or both?

@GabesArcade@gabesarcade.com Probably. How do you want this to work? An “Export” button to export all your settings in some form?

@david@daiwei.me Sorry, I’m not seeing what you’re saying? 🤔