Searching yarn

Twts matching #twtxt.
Sort by: Newest, Oldest, Most Relevant

Good riddance 2024…
2025, be good or else.

Happy new year Twtxt people. I’m grateful for getting to meet/talk to you all, It certainly was the best thing to have happened to me in this “2024” chapter of my life.

⤋ Read More
In-reply-to » Are there any good Registry? I like to check the mentions.

I found 2 active Registries: tilde.instite and twtxt.envs.net . I think that is missing a repository or system for them to find each other. It is easy to share registry users. Your work is awesome! Maybe you are supporting twtxt with the pod and software around them. I am very busy with the Emacs client, but I like to work creating my own version of Registry using Django.

⤋ Read More
In-reply-to » It must already be New Year here. Full continuous fire for ten minutes.

@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. :-(

⤋ Read More
In-reply-to » 3°C today, it was quite nice in the sun. A lot of hunting and tree felling going on in the forest. And we met the heron again, that was very cool: https://lyse.isobeef.org/waldspaziergang-2024-12-28/

@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.

⤋ Read More
In-reply-to » ROFL 🤣 I've found myself a new insult: :diffoff a vim command...

@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)

⤋ Read More
In-reply-to » 3°C today, it was quite nice in the sun. A lot of hunting and tree felling going on in the forest. And we met the heron again, that was very cool: https://lyse.isobeef.org/waldspaziergang-2024-12-28/

@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.

⤋ Read More
In-reply-to » @prologic 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).

@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.

⤋ Read More
In-reply-to » @emmanuel oh! Nice! You've now got a nice avatar 👌

@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).

⤋ Read More
In-reply-to » 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

@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)

⤋ Read More
In-reply-to » 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

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

⤋ Read More
In-reply-to » 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

@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.

⤋ Read More
In-reply-to » @doesnm So the user should then set nick = _@domain.tld in the twtxt.txt?

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

See it live at:

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

⤋ Read More