@movq@www.uninformativ.de How cool! So, that’s the last thing for the year, eh? :-)

My cat, @terron@duque-terron.cat has his own twtxt account. Would you follow him? #catsoftwtxt

@movq@www.uninformativ.de Beautiful! Well, today is also a rather foggy gray soup here.

@movq@www.uninformativ.de No, that was a wide open field, absolutely nowhere to hide. I reckon it was just a very brave individual. We somehow managed to radiate a sense of calm. :-) It might have been the same heron I saw the other days a few hundred meters west.

@prologic@twtxt.net it offends someone with a different opinion? 🤣

No, seriously… :diffoff is used to disable vim’s diff mode that’s usually started running vim -d someFile someOtherFile or by having both files on a split window and applying :diffthis on both panes. (just learned this this morning)

@rrraksamam@twtxt.net LOL. Crypto rubbish backed? 🤦‍♂️

@movq@www.uninformativ.de All my cameras have an optical zoom. The current one even reaches 18x optical magnification. This feller was very relaxed as we snuck up on him. We didn’t want to scare him off, so we stopped at around four meters. Still, some zoom factor was used to caputure him. :-)

The last few days were very sunny, so is today and the next couple days. One just has to keep moving, or it gets too cold.

@movq@www.uninformativ.de That sounds really great! :-) Happy hacking!

@doesnm@doesnm.p.psf.lt I guess it worked 🤣

Test Mention for Goryon! @doesnm@demo.yarn.social

@emmanuel@wald.ovh Btw I already figured out why accessing your web server is slow:

$ host wald.ovh
wald.ovh has address 86.243.228.45
wald.ovh has address 90.19.202.229

wald.ovh has 2 IPv4 addresses, one of which is dead and doesn’t respond.. That’s why accessing your website is so slow as depending on client and browser behaviors one of two things may happen 1) a random IP is chosen and ½ the time the wrong one is picked or 2) both are tried in some random order and ½ the time its slow because the broken one is picked.

If you don’t know what 86.243.228.45 is, or it’s a dead backup server or something, I’d suggest you remove this from the domain record.

@prologic@twtxt.net It’s hosted at home on an computer I didn’t use anymore. It worked well for a few months, and since maybe the beginning of December, it begun to be very slow. But like I said, I have no time for that now, but if I have questions when I’ll look, I’ll think of you 😅 (but I was thinking about installing a new OS before these problems, I may just do that).

@movq@www.uninformativ.de How about now? 🙏

@prologic@twtxt.net I might do it some day. 😅

@mckinley@mckinley.cc Thanks!

@prologic@twtxt.net I might do it some day. 😅

@emmanuel@wald.ovh oh! Nice! You’ve now got a nice avatar 👌

@mckinley@twtxt.net @prologic@twtxt.net or just be like… “We don’t need Microshaft’s Minecraft, We already have one at home!” 🤣

#Luanti/#MineTest FTW!

@doesnm@doesnm.p.psf.lt Why are they doing that?

@emmanuel@wald.ovh It is working! I’ve just noticed your feed link in my access.log and came by to say Hello! 👋 just give it a minute and others will notice your feed as well.

@prologic@twtxt.net, do you run a Minecraft server for your children? If so, which one?

Sorry @prologic@twtxt.net, I’ll take advantage of the sunny weather tomorrow. So, I won’t make it to the call.

@movq@www.uninformativ.de Oh yeah, that’s really nice! :-)

@maurice-renck@maurice-renck.de 🤔

@prologic@twtxt.net No I’m not trying to standardize the domains themselves xD I was just hinting at filtering cases where nick is identical to a level of a domain; in order to show shorter format nicks within clients, i.e: @nick.domain.ltd or @nick.ltd instead of a @nick@nick.domain.ltd or @nick@nick.ltd. Just like what @sorenpeter@darch.dk already did with the nick = domain case. (unless I’m missing the point)

@doesnm@doesnm.p.psf.lt Hahaha! :-D

@bender@twtxt.net @prologic@twtxt.net Reminds me of: https://img.ifunny.co/images/d07b9a2014e3b3901abe5f4ab22cc2b89a0308de8a21d868d2022dac7bb0280d_1.jpg :-D

@bender@twtxt.net Bahahaha in hindsight I got rid of that 🤣 Just silly nonsense, just one of those things when you create an account on yet-another silly centralized platform(s) and go “fuck” someone’s already taken the username I want 😅

@prologic@twtxt.net “therealprologic”? Really? 🤦‍♂️😅

@sorenpeter@darch.dk Here are two more cases:

• nick = subdomain: https://aelaraji.com/timeline/profile?url=https://lyse.isobeef.org/twtxt.txt -> lyse.isobeef.org
  
• nick = second level domain: https://aelaraji.com/timeline/profile?url=https://aelaraji.com/twtxt.txt -> aelaraji.com

@sorenpeter@darch.dk @bender@twtxt.net @prologic@twtxt.net Right. Also, generally speaking, if you come across a new feed URL, it’s probably either via some mention in another feed or the User-Agent in your access log. Both cases typically advertise also a display name. So, you just reuse whatever you’ve seen there.

hmm any ideas how to fix this case when there is no nick and it on a shared tilde hosting? http://darch.dk/timeline/profile?url=https://tilde.club/~deepend/twtxt.txt

@doesnm@doesnm.p.psf.lt How did you post from IndiePass? Did you add support for twtxt or use some kind of bridge?

I’ve implemented Use only nick as handle if nick and domain is the same · sorenpeter/timeline@8c12444

See it live at:

• nick = domain: https://darch.dk/timeline/profile?url=https://eapl.me/tw.txt
  
• nick ≠ domain: https://darch.dk/timeline/profile?url=https://twtxt.net/user/prologic/twtxt.txt
  
• no nick, use domain: https://darch.dk/timeline/profile?url=https://akkartik.name/twtxt.txt
  

I’m not sure I like the leading @ thou…

What should the advantage be to nick = _compared to just not defining a nick and let the client use the domain as the handle?

What is not intuitive is that you put something in the nick field that is not to be taken literary. The special meaning of _ is only clean if you read the documentation, compared to having something in nick that makes sense in the current context of the twtxt.txt.

No, i mean just _. If my nick = _ and my twtxt is located at https://doesnm.cc/twtxt.txt then just display me as @doesnm.cc. Why it’s not intuitive?

@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

@bender@twtxt.net Le Me is very tempted to spin up my own but not sure my pet computer(/server wannabe) and stone age bandwidth can withstand the Fedi-load 😅

and going back to a handle you could input in your client to look for the user/file, like @nick@domain.tls I think Webfinger is the way to go. It has enough information to know where to find that nick’s URL.

@prologic@twtxt.net does that webfinger fork made by darch work OK with yarn as it is now? (I’ve never used it, so I’m researching about it)
https://darch.dk/.well-known/webfinger/

@prologic@twtxt.net /ME taking notes… 📜✍

@prologic@twtxt.net there’s @deadblackclover@deadblackclover.net’s twtxt-el already, I couldn’t use it correctly when I’ve had just discovered it (yes, #emacs skill issues) … but it has been updated since then. I should give it another spin 👌

Have fun @johanbove@johanbove.info and see -(or read?)- you soon!

@movq@www.uninformativ.de Absolutely! Truly amazing work and excellent explanations.

I’m pretty sure they didn’t tell us this in school either.

I don’t remember what topic it was, but some of the maths lectures at uni were heaps better in linking several matters together. In school we were always told: And now for something completely different, we start a new topic, so when you kids haven’t understood the previous one, worry not, now you got the chance to maybe get this one and improve your maths grade. Only at uni we were actually taught that it’s in fact basically exactely the same thing as something else, just with some slightly tweaked rules. If I only were told this a decade earlier or so. It would have made stuff sooo much easier.

@movq@www.uninformativ.de Opps! My bad, I had a BotFilter activated which lead you to a 403. Fixed!

@movq@www.uninformativ.de Hmm, works here. Maybe some temporary problem that has been fixed by now?

Thanks @prologic@twtxt.net !

@lyse@lyse.isobeef.org Hmmm:

Could not fetch: HTTPError('403 Client Error: Forbidden for url: https://uplegger.eu/twtxt.txt')

🤔

@movq@www.uninformativ.de Hahaha, no worries. :-)

Thanks @bender@twtxt.net for the feedback. I fixed and expanded the article. I’m sorry for my poor interaction. Furthermore, I’m reading and writing while programming a client in Emacs.

You are clearly a time traveler, @xuu@txt.sour.is!

@prologic@twtxt.net That also has the downside of fitting right in the write-only code category. :-D

@movq@www.uninformativ.de Ha, that’s cool, I wasn’t aware of 2024 being one of these years.