I’m thinking about moving my blog/page from uninformativ.de over to movq.de (because the name “uninformativ.de” really isn’t great, never has been). How much in the twtxt/Yarn world will that break? 😂 I’ll obviously install redirects, so it should be relatively painless, right?
@movq@www.uninformativ.de movq.de is cool. I don’t see any problem as long as you set up redirects.
@movq@www.uninformativ.de FWIW, I find “uninformativ” quite cool. :-) When you move, my client will show me duplicates, as my parser doesn’t look at the first url meta data field but uses the feed URL instead. I think. It’s been too long since I worked on that. Either I implement the spec correctly or I simply do not change the subscription URL.
@movq@www.uninformativ.de FWIW I always liked uninformativ.de myself 😅 However that being said, as @lyse@lyse.isobeef.org points out, you’d only need to shove a # url = on any old feed files you move across, and I’d start with a new empty feed once you migrate over. I think 🤔 Moving feed locations affects the way individual Twts are hashed, as the Twtxt spec never had the concept of an “identity” the location of your feed more-or-less becomes your identity or the first # url = field in your feed’s metadata.
One last thing, @movq@www.uninformativ.de. I really do like that interesting stuff is hosted at uninformativ.de. Not only is this great irony, but it suggests that you don’t take yourself too seriously. I love that. When I first encountered your domain I thought – and still do – that it is a funny name. Anyway, don’t wanna push you.
well, I like that name uninformativ.de ! Has more personality than the other one, I think
And I read this article, and didn’t make the connection to your domain!
https://www.uninformativ.de/blog/postings/2022-04-21/0/POSTING-en.html
I’m still looking for a typed Python, but let’s see if it comes natively in 3.13 or something