I finally watched “C++17: I See a Monad in Your Future” and it was rather nice (at least in 1.8 times speed): https://www.youtube.com/watch?v=BFnhhPehpKw I finally also learned why the auto syntax exists (to allow specifying a return type that depends on the argument).

I loved to watch the “Curiosity Show” when I was a kid (the German version, of course – to this day, nothing in German television is in English, it’s all dubbed horribly). And it’s on YouTube now! 🥳 https://www.youtube.com/@CuriosityShow/videos

@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

Actually better than game console: https://elon.cucked.me/grapplingdev/status/1872013696077308284

@lyse@lyse.isobeef.org Haha 🤣

@doesnm@doesnm.p.psf.lt Haha 🤣

ROFL

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

Your nick is normal. After i delete gh account with nick doesnm i can’t reuse them. And my next nick is… doesnmisclown xD (without a)

python cgi script which handles micropub and writes content to twtxt file. I was want micropub+microsub for twtverse but seems i burned (due choice wrong stack?): https://privatebin.net/?0b598b91ac186855#BfRKjLUQz5KUFJNekJBb5V2qvtEe8xQN8nenYbkez2XR

@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? 🤦‍♂️😅

@aelaraji@aelaraji.com domains/subdomains I think are much harder to “standardize” hmmm 🤔

@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

@bender@twtxt.net Hahaha Hahaha 🤣 I’ve had this one for a while actually as well as https://prologic.blob (which I’m thinking of taking back from micro.blog and just using my own tools, namely zs) 😅

@prologic@twtxt.net we have been all guilty, at some point or another, of spending too much money on domains we don’t need. Pax vobiscum! 😂😂😂

What do we think? ==> https://prologic.dev/

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

@sorenpeter@darch.dk I think the use of ~ is so commonly used as a <username> that we should just suppose that out of the box by all clients for display purposes.

@soren@darch.dk you reach out and tell them to set a nick? Or parse the URL, and use the word right after the tilde as the nick?

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

Happy Christmas!

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

I saw a paraglider after sunset. Must have been super cold up there in the sky, we just had 1-2°C on the ground. And I passed a heron at just 5-6 meters distance. I think that’s a new record low. The sunset itself wasn’t all that shabby either. Hence, a very good stroll.

Merry Christmas ! 🎅🎄

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…

You are right: no advantage. Also your method can make backward compatible to feeds which doesn’t implement metadata extension

@sorenpeter@darch.dk No I agree. I think if the feed doesn’t hint at a nick, just default to displaying the bare domain. These sorts of things btw need to go into a Client recommendations / guidelines. If someone wants to start drafting up such I doc I will fully support this and help shape it 👌

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.

@doesnm@doesnm.p.psf.lt That can be done fairly easily I think/

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

Why not nostr way? https://github.com/nostr-protocol/nips/blob/master/05.md#showing-just-the-domain-as-an-identifier

@aelaraji@aelaraji.com I am sure it will run fine. I mean, mine is on a VPS, with 1GB RAM, 1vCPU, and shares it with Conduwit (Matrix), a few websites, Headscale, etc. 😂

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

Merry Xmas everyone! have a blessed and happy day! 🎉

Merry Christmas! Cute canine, as always! 🥰

Merry Christmas, everyone!

Merry Christmas 🥳

Merry Christmas everyone! Have a very low resolution sitting canine, to end this year with.

@slashdot@feeds.twtxt.net This is some real old-school malware. Maybe it’s not such a good idea to let motherboard vendors run whatever code they want inside your operating system. Pro tip: This only happens in legacy operating systems.

@prologic@twtxt.net Merry Christmas!

Merry 2024 Christmas 🎅 y’all 🥳 #Xmas24

GoToSocial snapshot has gained “editing statuses” capabilities (and the ability to see the update trail as well). That was one of the things I wanted to most to be implemented. Actually, that sits at the top of my wish list. Next is push notifications.

@eapl.me@eapl.me that’s such a good plan! Staying at home, comfy, is all I wanted. But nooo! This brings true the saying in Spanish, “Una cosa piensa el borracho, y otra el bodeguero.” 😂

Are we talking about profile view heading, heading of posts or inline mentions?

Image

In yarnd I recall there is a setting for changing the heading of posts, but not for the two others as of yet.
I like the hover option for inline mentions. For the other places some like how yarnd does it in two line or “ nick (domain.tld) ” could also work.

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/

Oh no!
Wife and I agreed on hibernate until January, just visiting relatives but avoiding any kind of shopping. I tried buying something like 2 or 3 days ago and it’s insane :o

Good luck! :)

I’m just having a similar issue with a podcast I just uploaded on Castopod (which supports ActivityPub).

My first thought was creating a subdomain with the name of the podcast mordiscos.eapl.me

Then I watched that the software allows many podcasts in the same domain, so I had to pick a handle:
https://mordiscos.eapl.me/@podcast

So now I have @podcast@mordiscos.eapl.me when this one is ‘more correct’ @mordiscos@podcast.eapl.me or it could even be @mordiscos.eapl.me
I wasn’t aware of all that when I setup Castopod (documentation might improve a lot, IMO)

My point here is that it’s something important to think from the start, otherwise is painful to change if it’s already being used like that.