@doesnm@doesnm.p.psf.lt So the user should then set nick = _@domain.tld in the twtxt.txt?

It seems more intuitive and userfriendly to just use: nick = domain.tld and have then convention for clients to render the handle as @domain.tld instead of @domain.tld@domain.tld

For a feed with no nick defined (eg. https://akkartik.name/twtxt.txt) it will also be simpler and make more sense to just use the domain as the nick and render it as @domain.tld

@eapl.me@eapl.me A way to have a more bluesky’ish handles in twtxt could be to take inspiration from Bridgy Fed and say: If NICK = DOMAIN then only show @DOMAIN
So instead of @eapl.me@eapl.me it will just be @eapl.me

And it event seem that it will not break webfinger lookup: https://webfinger.net/lookup/?resource=%40darch.dk (at least not for how I’ve implemented webfinger on my sever for a single user;)

QOTD: Do you have a way to get back into your home network if you get locked out?

I have a Tor hidden service that lets me SSH into my server from anywhere. I never had to use it until last week. I was playing around with the port forwarding configuration on my router for Wireguard (migrating to a new server, very exciting), forgot to change it back, and found myself an hour away from home hoping to watch a show on Jellyfin. All it took to fix it was an SSH port forward through that hidden service to (very slowly) access my home router’s Web interface.

My 400th Twtxt Post will be about you: wishing you, reader of my Twtxt feed, all the best for the coming year and most of all love, health, and that your projects and work may contribute to the greater good of all mankind. I will be taking a social-media break for a couple of weeks to enjoy this special time with my family. I hope you will be able to do this with your family and friends too.

Does anyone else declare a computer dead after extensive testing, let it sit on a shelf for 2 weeks or a year, try it again, and have it work fine? It seems like that’s happened to me a lot more than it should.