@movq@www.uninformativ.de Implementing my own TUI rendering in the tt rewrite, I know what a headache this can be. :-)

@movq@www.uninformativ.de It’s not any better on the “ground” with trees and buildings around. They don’t dampen at all, in fact the houses just cause reverb and amplify the bangs. Rest assured, I did not hear any people laughing or anything in that nature. Just grenades going off. Talking to my mates, it appears that I live in an especially bad shithole, they reported a noticable reduction of explosions around 00:20. Over here, there was constant fire till around 02:00.

Yep, that’s exactly how I imagine a war zone, too.

@kat@yarn.girlonthemoon.xyzHello 👋 Welcome!

@prologic@twtxt.net this is so fucking real i’m so sick of AI/LLM crap

@kat@yarn.girlonthemoon.xyz oh shit that worked

@kat@yarn.girlonthemoon.xyz this is lonely!

@kat@yarn.girlonthemoon.xyz god damn it

@kat@yarn.girlonthemoon.xyz god damn it why aren’t icons working

@kat@yarn.girlonthemoon.xyz testttt

@news@yarn.girlonthemoon.xyz fuck

Whoops, this of course should have read “other than on the last three days”. Yeah, people give a fuck, @movq@www.uninformativ.de. And police doesn’t care either. https://de.wikipedia.org/wiki/Feuerwerk#Bundesrepublik_Deutschland_(Gegenwart)

@movq@www.uninformativ.de Wow, quite an elaborate editor you’ve programmed there!

@prologic@twtxt.net Do you have any data about the #twtxt health? How many people are currently using twtxt?

@bender@twtxt.net For sure, we have isolated bangs since at least 12th December, too. That day I also noticed piles of cracker garbage in the forest. What assholes. Luckily, it’s illegal to sell fireworks other than after the last three days in the year. However, people can still import them and they do. :-(

Lol, seems yarn do not display metadata on @terron@duque-terron.cat

@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