Aha, yesterday’s newly added support for LC_TIME to render localized timestamps also broke the feed parsing with my LANG=de_DE.UTF-8 and LC_CTYPE=de_DE.UTF-8 environment. :-)

Atom feeds make use of RFC 3339 timestamps. They are first converted into RFC 882 timestamp representation, which is the one that RSS feeds use. However, this conversion now results in localized RFC 882 timestamps, which cannot be parsed into Unix timestamp numbers via curl_getdate(…). I bet that it doesn’t know about the localization at all and expects English month and weekday names. Looking at its docs, I reckon that function was selected because of its myriad of supported timestamp formats: https://curl.se/libcurl/c/curl_getdate.html RFC 3339 is not included, though, hence the transformation up front.

The intermediate Item objects in the parser domain use std::string for the timestamp representation. This isn’t all that silly, because Newsboat supports all sorts of different feed formats with different timestamp formats. These RFC 883 timestamps are centrally parsed into time_t.

Speaking of time: It’s time to go to bed after this late bug hunting fun. :-)

@movq@www.uninformativ.de Right, they messed up the signing key rotation: https://blog.denic.de/technische-storung-bei-de-domains-behoben/

@lyse@lyse.isobeef.org Yep, this was a big oopsie at DENIC:

• https://blog.denic.de/denic-informiert-uber-storung-im-dnssec-fur-de-domains/
  
• https://blog.denic.de/denic-informiert-uber-die-behebung-der-dnssec-storung-fur-de-domains/

All sorts of .de domains don’t resolve right now. But not all, movq.de for example still works. All on our server and basically all major other sites are cactus. Maybe some DENIC problem? I’m too tired to investigate, but I’m looking forward to tomorrow to read some report on that. :-) Good night.

The auDA, and some 3rd-party identify service and my Registrar are a joke!

WOW! I just had to share this little story I ran into today.

I tried to register a .AU Domain the other day, only for it to instantly fail.

I emailed support, which took several days to respond, only for them to respond by saying (paraphased):

We’re sorry, but the identify checks failed. The 3rd-aprty service doesn’t tell us why, But, please make sure that the ID you used matches the Full Name, including any Middle name(s).

I used my Passport number. Which of course has my First, Middle and Last Name.

I can only assume at this point that the checks failed on the missing “Middle name”. Why? Because the Registrar I use has a database and user interface for “contacts” that only have support for First name and Last name. NO Middle Name.

🤦‍♂️ This is basically stupid at this point. Systems cannot be trusted at the most fundamental level, no matter how good they are.

Until we figure out how to build a system that allows an individual to prove to another entity that they are who they say they are without a shred of doubt (i.e: cryptographically), we’re stuffed.

There is literally nothing I can do in this case. The auDA are at fault. The 3rd-party identify service (unknown) are at fault. The registrar are at fault. Hell, even the Passport office are at fault for even bothering to or requiring a Middle name.

How has “identity” come to this?

Transferred my last domain over from Infomaniak to Dynadot 🙌🏼

@movq@www.uninformativ.de I still think that your original domain is cool as fuck! :-)

I didn’t change any subscriptions, and I still see your messages, so whatever you did worked fine. :-)

@prologic@twtxt.net Well, you can associate your identity to the apex domain with a bit of Webfinger wizardry, but I don’t. Mine are always attached to the sub-domains. I find it easier to migrate between instances that way without risking borking federation.

@aelaraji@aelaraji.com does that mean your identity gets associated with your Apex domain or your sub domain?

@shinyoukai@neko.laidback.moe yeah, that’s the only reason why I use sub-domains when trying anything federated (I believe Matrix has the same problem), in case things didn’t go as planned I can just migrate and take it down.

I’m kind of tired of late of telling support folks, for example, ym registrar, how to do their fucking goddamn jobs 🤦‍♂️

Hi James,

Thank you for your patience.

There are several reasons why a .au domain registration might fail or be cancelled, including inaccurate registrant information, ineligibility for a .au domain licence, or issues related to Australian law.

For a full list of possible reasons, please see this article: https://support.onlydomains.com/hc/en-gb/articles/6415278890141-Why-has-my-au-domain-registration-been-cancelled

If you believe none of these reasons apply to your case, please let us know so we can investigate further.

Best regards,

Yes, so tell me support person, why the fuck did it fail?! 🤬

@prologic@twtxt.net I am telling you that is extremely easy: https://docs.gotosocial.org/en/latest/advanced/host-account-domain/. Now, if you are putting into account your rather… unique setup, then that’s another story.

@bender@twtxt.net That’s not the problem. The problem is the complex DNS setup and delegation. I’ve gotten it working once before, but it’s not that easy if you don’t intend to run it on the APEX Domain.

Tired to re-enable the Ege route to git.mills.io today (after finishing work) and this is what I found 🤯 Tehse asshole/cunts are still at it !!! 🤬 – So let’s instead see if this works:

$ host git.mills.io 1.1.1.1
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:

git.mills.io is an alias for fuckoff.mills.io.
fuckoff.mills.io has address 127.0.0.1

PS: Would anyone be interested if I started a massive global class action suit against companies that do this kind of abusive web crawling behavior, violate/disregards robots.txt and whatever else standards that are set in stone by the W3C? 🤔

To everyone previously asking, what my (and other developers) endless complaining about Google, to both every EU body, with a form on their website and every relevant team at Google accomplished…
WE FUCKING WON!!!
“While security is crucial, we’ve also heard from developers and power users who have a higher risk tolerance and want the ability to download unverified apps.”
-source

I was also able to work with my new webhost, to bring back “🐕.fr.to” - everyones favorite vanity redirect domain, for my site, Googles changes to SSL warnings in Chrome, killed at the beginning of this year.

The lesson: I NEED TO COMPLAIN MORE

@bender@twtxt.net Hahaha! :-D But I actually do like their approach. I don’t know what staff should do differently when they are not involved in the channel topic. At least in the general case. Maybe in this specific scenario here they could have cross-checked domains, git repos and stuff like that. But I also reckon that it’s only fair if they treat everybody the same.

@prologic@twtxt.net FWIW, I love the idea and I do the same with my email domains. It’s the most effective way to fight spam, IMO. 🥳

@prologic@twtxt.net hehehe, yeah, it isn’t mine neither. Most obscure TLDs are in small registrars. I like to stick to one register (even though when Google Domains ceased to exist I was forced to have two, as Cloudflare doesn’t support the .ONE TLD).

@bender@twtxt.net Makes me wonder whether somethingarather.zip is a good primary domain for the service I’m building? 🤔

Buscame en Yggdrasil http://dev1ls.ygg.at/ #NixOS #ipv6 #yggdrasil #Domain

Today, I experimented with Linux Capabilities as a continuation to my Unix Domain Sockets research from a few months ago: https://lyse.isobeef.org/caller-information-via-unix-domain-sockets/#capabilities

I learned that I don’t know hardly anything and there is heaps more to explore. Tomorrow, I will do the same in Go and see how that feels.

@zvava@twtxt.net @bender@twtxt.net At first I added it without thinking when planning the possible fields based on other UIs I was researching.

I was about to discard it but after thinking about it a bit I noticed that the services allowing to have a separated nick and display_name could unlock some good uses.

For example some added context or at-a-glance information like pronouns or statuses (like Artist [Accepting commissions] or App Name (v2.5)) while other used a more readable version of the nick (blog.domain.com became Person Name's Blog).

Of course it is absolutely optional and it can be safely ignored, but with my vision of being able to build more that a pure twtxt clients, giving it a first-class support just like the other known fields felt right to me.

Here is just a small list of things™ that I’m aware will break, some quite badly, others in minor ways:

1. Link rot & migrations: domain changes, path reshuffles, CDN/mirror use, or moving from txt → jsonfeed will orphan replies unless every reader implements perfect 301/410 history, which they won’t.
   
2. Duplication & forks: mirrors/relays produce multiple valid locations for the same post; readers see several “parents” and split the thread.
   
3. Verification & spam-resistance: content addressing lets you dedupe and verify you’re pointing at exactly the post you meant (hash matches bytes). Location anchors can be replayed or spoofed more easily unless you add signing and canonicalization.
   
4. Offline/cached reading: without the original URL being reachable, readers can’t resolve anchors; with hashes they can match against local caches/archives.
   
5. Ecosystem churn: all existing clients, archives, and tools that assume content-derived IDs need migrations, mapping layers, and fallback logic. Expect long-lived threads to fracture across implementations.

@kat@yarn.girlonthemoon.xyz Ahh what do you mean by images don’t embed? They definitely should! By default however all domains are blocked, so you might want to either allow some domains or just put in a .* entry to allow all/any domsins. Screenshot attached

I hear you, @movq@www.uninformativ.de! :‘-(

At work, too. For a few weeks now when I try to log into this horrible Outlook web intershit (Because why would they fix the Evolution integration?! It’s cactus for well over a year now. Probably more like two.), it forwards me to the corporate weblogin, I enter my credentials, even do the bloody MFA crap and get redirected back to Outlook. “Loading mailbox…” “Please wait for us to log you out, do not close this window while this process is underway.” Fuck you! I have to delete the cookies for this damn domain each and every fucking time. Otherwise, this goes in circles forever. I tried the game for 15 minutes, no joke.

But wait, there’s more! Why just fuck it up only a little bit? This week I get logged out at the middle of the day. Every. Single. Day. Not even close to eight hours since I started, no. What the hell!? I reckon I just don’t even bother reauthenticating anymore in the arvo. No more e-mails for Lyse after lunch. Fuck it. It’s just distraction, anyway, right?!

Woops, sorry if my Pod was offline for a few days, I hadn’t checked and needed to renew the domain xP

Domain-Specifc Google News RSS Feeds ?~L~X https://thenewleafjournal.com/b/7uu

@bender@twtxt.net Maybe one day I’ll take back over my prologic.blog domain from µBlog and redoit with my handy zs tool with some nice CSS 🤣

@bender@twtxt.net Muting on a domain level would be an option.

i have found my ultimate domain name 😄

it match exact my first, last & middle name in a way that satisfied me.

would lovely to see your creative nickname & brand tie to a nice domain name, rather than some threads.net or x.com 😝😝

that isn’t mine, a newly made friend bought the domain & code that simple site for me, i find it’s hilarious to have so i put it in the front

thank you!!!

Archaea
⌘ Read more

@kat@yarn.girlonthemoon.xyz Ahh but you’re like one of a very few that actually own domains and do interesting things 😅

wish i could join in on the domain age discussion but i registered my first domains last year

@anth@a.9srv.net happy birthday, “youngster!”

Domain Name: NETBROS.COM
Registry Domain ID: 1193243_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.cloudflare.com
Registrar URL: https://www.cloudflare.com
Updated Date: 2025-03-29T04:08:33Z
Creation Date: 1998-04-29T04:00:00Z

@anth@a.9srv.net 24 years is quite a long time. 😳 My blog domain is from 2006 (still, almost 20 years, oof).

@anth@a.9srv.net Congrats, that’s pretty cool! Quite some time, I’m impressed.

@prologic@twtxt.net You’ll sometimes find the “Creation Date” in whois. Our domain was registered in 2009. Woah. That’s also been a while, crazy.

According to a very old email one of my more personal family domains was registered in 2013 making it 12 years old, so I was closed 🤣 my public facing one is much much older 🤣

@anth@a.9srv.net I actually don’t have a clue how old my public-facing domain is 🤣 I have another more personal one that’s probably around ~15 years, but I’m not even sure how to check tbh 😅

My main domain name turned 24 years old today. That feels weird.

Yesterday, I had a look at Unix domain sockets and how to obtain the caller information: https://lyse.isobeef.org/caller-information-via-unix-domain-sockets/

@prologic@twtxt.net yup. Funny enough, the first twtxt should have sufficed, as if there is no domain, there will be no feed (at that domain). The edit to add that the feed will not be available is redundant.

Hi @lyse@lyse.isobeef.org, I canceled the domain, so neotxt or my feed there are not coming back.

@eapl.me@eapl.me I wouldn’t call it natural, it is the way Bluesky decided to handle handles (not meaning to make a pun, or anything). There is no other way, but that.

The bottomline is, there are agreed upon “standards”, right? From example, on Yarnd you show as “eapl.me”, from “eapl.me”. A kind of weird redundancy because on twtxt, ever since I started using it, one will expect to see a “nick” (equivalent to a person’s first name), from “a domain” (like a surname).

There is nothing holding back someone from giving themselves the nick:

thisismyawesomenickforwhichiwillbeknownforeverandeveritsgreatisntit

But, do we really want that? 😅

hehe, just catching up on this thread! I’ve replied in another that using periods/dots sounds good to me as it’s usual in domains, but perhaps some agreement would be needed. For now I think any character is valid as long as it is not a space.
For example we are using this for PHP twtxt.php#L153

on timeline the mention looks OK. Is there an issue on Yarn?

It’s an interesting topic. For example on Bsky it’s natural to allow domains https://bsky.social/about/blog/4-28-2023-domain-handle-tutorial

Although TwiXter only allows (letters A-Z, numbers 0-9 and of underscores)
https://help.x.com/en/managing-your-account/x-username-rules

I only just today learned you have an f(x) themed domain name

Zoom Outage Caused by Accidental ‘Shutting Down’ of the Zoom.us Domain
Comments ⌘ Read more

published: ‘Le Bureau’: a domain registrar cooperative https://copyleftculture.com/le-bureau.html