@movq@www.uninformativ.de Yeah, that would also be fine with me. I certainly do like the “arbitrary” in your comment.

While writing the article, I also thought about something like that:

date := time.Date(2026, 6, 19,
    17, 0, 0, 0, time.UTC)

Or possibly:

date := time.Date(
    2026, 6, 19,
    17, 0, 0, 0, time.UTC,
)

But it’s four lines for a damn timestamp. I also contemplated whether a comment acting as a separator is all that’s needed:

date := time.Date(2026, 6, 19, /**/ 17, 0, 0, 0, time.UTC)

I might like that the most. Not entirely sure yet. It kinda feels like a hack, but still a little elegant. Add your comment on top and we’re golden. Maybe?

I deliberately excluded them as this only distracted from the points I wanted to make. And I also realized that this example was just not ideal at all. Perhaps I should add them nevertheless?

If I ever invented a programming language, a much more human readable timestamp representation of some sort, RFC 3339 or very close to that would be part of that language. Something along the lines of /pattern/ for regexes in certain languages.

@movq@www.uninformativ.de Great to be asked for feedback! I just noticed that the first wcwidth version was derived from Markus Kuhn’s C code. I came across him in my ISO 8601 and RFC 3339 endeavors the other day. https://www.cl.cam.ac.uk/~mgk25/iso-time.html What a surprise. :-)

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

DynIP – Dynamic DNS with RFC 2136, IPv6, DNSSEC, and BYOD
Article URL: https://dynip.dev/

Comments URL: https://news.ycombinator.com/item?id=48276363

Points: 8

# Comments: 3 ⌘ Read more

The retirement of the PHP license
The PHP project has long shipped under its own license — except for
the parts under the Zend Engine License. The PHP project has now announced
that the PHP license has been retired, and the PHP code has been relicensed
under the three-clause BSD license. See this\
blog entry for more details.

Getting here required more than [writing an\
> RFC](https://wiki … ⌘ Read more

[$] One Sized trait does not fit all
In Rust, types either possess a constant size known at compile time, or a
dynamically calculated size known at
run time. That is fine for most purposes, but recent proposals for the language
have shown the need for a more fine-grained hierarchy.
RFC 3729 from David Wood and Rémy Rakic would add a hierarchy of
traits to describe types with sizes known under different circumstances. While
the idea has been subject … ⌘ Read more

Rust 1.95.0 released
Version\
1.95.0 of the Rust language has been released. Changes include the
addition of a cfg_select!
macro, the capability to use if let guards to allow conditionals based on pattern\
matching, and many newly stabilized APIs. See the release\
notes … ⌘ Read more

OpenSSL 4.0 Released With Encrypted Client Hello, RFC 8998 Support
OpenSSL 4.0 was just released as a big update for this widely-used SSL/TLS and crypto library… ⌘ Read more

AMD Revives Linux Kernel Patches For Hardware-Accelerated vIOMMU
Back in 2023 AMD posted hardware-accelerated virtualized IOMMU patches for the Linux kernel as a request for comments (RFC). In 2024 they then posted a second iteration of the AMD vIOMMU patches but then seemingly fell off the radar. This morning is now the first set of updated AMD vIOMMU patches sent out on the Linux kernel mailing list with the RFC tag now removed… ⌘ Read more

AMD Posts Latest “pghot” Code For Overhauling Linux Hot Page Tracking & Promotion
One of the core Linux infrastructure improvements that AMD engineers have been working on recently is pghot as a hot-page tracking and promotion subsystem. This proposed addition to the Linux kernel could be quite beneficial especially for those using modern AMD EPYC servers with CXL and multiple memory tiers… ⌘ Read more

Linux Patches Updated To Steal Tasks For Improving CPU Utilization
Huawei engineer Chen Jinghuang posted the latest request for comments (RFC) patches for stealing tasks from overloaded CPUs in the same last level cache (LLC) in order to improve overall CPU utilization with today’s large core count servers… ⌘ Read more

Linux Kernel API Specification Framework Advances Past RFC Stage
After going through five rounds of review under a Request For Comments (RFC) flag, today the latest round of Kernel API Specification Framework patches were sent out with the RFC flag removed… ⌘ Read more

AMD DPTCi Driver Posted For Linux To Better Enhance Ryzen Gaming Handhelds
A request for comments (RFC) patch series was posted today to the Linux kernel mailing list to introduce the AMD Dynamic Power and Thermal Configuration Interface “DPTCi” driver. With this driver it would provide better upstream Linux kernel support for tuning the power / performance / thermals of modern Ryzen-powered gaming handheld devices. Though don’t get too excited right away as the driver was assembled in part by AI that is already ca … ⌘ Read more

ML-LIB: Machine Learning Library Proposed For The Linux Kernel
Sent out today as a request for comments (RFC) by a Linux kernel engineer employed by IBM is a machine learning library for the Linux kernel. The intent is on plugging in running ML models to the Linux kernel that could be used for system performance optimizations and various other purposes… ⌘ Read more

“DHEI” Proposed For Linux To Help Cloud-Native Orchestrators & High Frequency Traders
Sent out today as a request for comments is a new patch series for Dynamic Housekeeping and Enhanced Isolation (DHEI). DHEI aims to provide run-time adjustments to kernel behavior around CPU isolation for helping with latency-sensitive tasks. The expressed goal is for helping cloud-native orchestrators and high frequency trading platforms dynamically re-partition CPU resources without downtime… ⌘ Read more

RFC Patches Posted For Klint Integration With The Linux Kernel: Rust-Based Linting Tool
A request for comments (RFC) patch series was sent out today for providing Klint integration with the Linux kernel. Klint is a new linting tool written in the Rust programming language that helps with static code analysis for errors/bugs as well as code styling inconsistencies… ⌘ Read more

LLMinus Working On AI/LLM-Powered Merge Conflict Resolution For The Linux Kernel
Building off an initial request for comments (RFC) patch series posted during the winter holidays, an updated RFC patch series was posted this weekend for LLMinus. LLMinus is an effort led by NVIDIA Linux kernel engineer Sasha Levin to provide a large language model (LLM) assisted merge conflict resolution tool focused on Linux kernel development… ⌘ Read more

Qualcomm Sends Out Linux Patches For RAS Support On RISC-V For Reporting Hardware Errors
The latest work by Qualcomm on the RISC-V CPU architecture is sending out their first non-RFC patch series for enabling Reliability, Availability and Serviceability (RAS) support by making use of the RISC-V RERI specification. This RISC-V RAS support is useful for conveying hardware errors to users and will be especially important with future RISC-V Linux servers… ⌘ Read more

Linux Kernel Considers Linking The Relocatable x86 Kernel As PIE In 2026
To allow for additional security hardening of the Linux kernel, a patch series has been updated more than one year later to link the relocatable x86_64 kernel as Position Independent Executable (PIE) code… ⌘ Read more

‘IPv6 Just Turned 30 and Still Hasn’t Taken Over the World, But Don’t Call It a Failure’
Three decades after RFC 1883 promised to future-proof the internet by expanding the available pool of IP addresses from around 4.3 billion to over 340 undecillion, IPv6 has yet to achieve the dominance its creators envisioned. Data from Google, APNIC and Cloudflare analyzed by The Register shows less tha … ⌘ Read more

LLVM Considering An AI Tool Policy, AI Bot For Fixing Build System Breakage Proposed
Last week a request for comments (RFC) was issued around establishing an LLVM AI Tool Use Policy. The proposed policy would allow AI-assisted contributions to be made to this open-source compiler codebase but that there would need to be a “human in the loop” and the contributor versed enough to be able to answer questions during code review. Separately, yesterday a proposal was sent out for creating an AI-assisted fixer bot to hel … ⌘ Read more

PEP 819: JSON Package Metadata
This PEP proposes introducing JSON encoded core metadata and wheel file format metadata files in Python packages. Python package metadata (“core metadata”) was first defined in PEP 241 to use RFC 822 email headers to encode information about packages. This was reasonable in 2001; email messages were the only widely used, standardized text format that had a parser in the standard library. However, issues with handling different encodings, differing handling of line breaks, and other differences between i … ⌘ Read more

New Patches Lay Out Linux Kernel Adjustments For RISC-V RVA23 Hardware
With the first of RISC-V RVA23-compatible hardware expected to be released in 2026, we are beginning to see more Linux developers prepare for this RVA23 profile and the now-mandated extensions. Sent out this week was an initial “request for comments” patch series on RVA23 adjustments for the Linux kernel… ⌘ Read more

AMD Working On Push-Based Load Balancing For Linux To Further Enhance Performance
One of the new Linux engineering initiatives out of AMD is working to further enhance Linux performance on today’s large core count systems by introducing push-based load balancing… ⌘ Read more

I kind of hate conventional commit messages: https://www.conventionalcommits.org/en/v1.0.0/#summary

but I am loving reading RFC 2119: https://www.ietf.org/rfc/rfc2119.txt

HQspinlock Proposal For Linux Shows Very Nice Performance Benefits For Large Servers
A Huawei engineer has sent out patches proposing HQspinlock as a Hierarchical Queued NUMA-aware spinlock for the Linux kernel. HQspinlock aims to addresss inefficiencies within the Linux kernel’s spinlock on modern NUMA-systems due to frequent and costly cross-NUMA cache-line transfers… ⌘ Read more

All my newly added test cases failed, that movq thankfully provided in https://git.mills.io/yarnsocial/twtxt.dev/pulls/28#issuecomment-20801 for the draft of the twt hash v2 extension. The first error was easy to see in the diff. The hashes were way too long. You’ve already guessed it, I had cut the hash from the twelfth character towards the end instead of taking the first twelve characters: hash[12:] instead of hash[:12].

After fixing this rookie mistake, the tests still all failed. Hmmm. Did I still cut the wrong twelve characters? :-? I even checked the Go reference implementation in the document itself. But it read basically the same as mine. Strange, what the heck is going on here?

Turns out that my vim replacements to transform the Python code into Go code butchered all the URLs. ;-) The order of operations matters. I first replaced the equals with colons for the subtest struct fields and then wanted to transform the RFC 3339 timestamp strings to time.Date(…) calls. So, I replaced the colons in the time with commas and spaces. Hence, my URLs then also all read https, //example.com/twtxt.txt.

But that was it. All test green. \o/

A tour of upcoming RFCs for the Hare programming language
Comments ⌘ Read more

RFC 5081: Using OpenPGP Keys for Transport Layer Security (TLS) Authentication
Comments ⌘ Read more

Nobody writes emails by hand using RFC 5322 anymore, nor do we manually send them through telnet and SMTP commands. The days of crafting emails in raw format and dialing into servers are long gone. Modern email clients and services handle it all seamlessly in the background, making email easier than ever to send and receive—without needing to understand the protocols or formats behind it! #Email #SMTP #RFC #Automation

**(#lnrgahq) @eapl.me@eapl.me@eapl.me@eapl.me What’s with your client not using the proper syntax for mentions?

$ bat 'https://twtxt.net/twt/ ...**
[@eapl.me _@eapl.me_](https://twtxt.net/external?uri=https://eapl.me/twtxt.txt&nick=eapl.me) [@eapl.me _@eapl.me_](https://twtxt.net/external?uri=https://eapl.me/tw.txt&nick=eapl.me) What’s with your client not using the proper syntax for mentions?

$ bat ‘https://twtxt.net/twt/lnrgahq’ | jq ‘.text’
”(#4xaabhq) thanks @prologic!
@bender the idea of the RFC was to reach an agreement on a … ⌘ Read more

TIL that RFC means Request For Comments

HTTP 代理的原理和實現
HTTP 代理可以說是每個開發者都繞不開的工具。幾乎每天都會使用，但你真的瞭解 HTTP 代理的原理嗎？ 說明：這裏討論的 HTTP 代理是指 HTTP Proxy Server，具體是正向 HTTP 代理服務端的原理和實現。想了解 HTTP 代理的原理，最嚴謹的方法是閱讀 RFC 文檔，但這同時也是最困難的方式。今天，我將介紹一種更直觀的學習技巧。從名字上就可以看出，HTTP 代理基於 HTT ⌘ Read more

@lyse@lyse.isobeef.org agree on the HTTP stuff. I mean we could mention that for optimization see RFC yadda yadda should be followed for caching. but not have it part of the spec proper.

RFC on e-ink readers ⌘ Read more

お知らせ：JPCERT/CC Eyes「RFC 9116「security.txt」の紹介（2022年8月）の続報」 ⌘ Read more

RFC 2646’s Format=Flowed and inline quoting ⌘ Read more

@prologic@twtxt.net Unfortunately the RFC’s are a bit light in this regard. While it makes mention of different kinds of accounts like mailto: or status services.. it never combines them. It does make mention of using redirects to forward a request to other webfingers to provide additional detail.

I am kinda partial to using salty:acct:me@sour.is, yarn:acct:xuu@txt.sour.is, mailto:me@sour.is that could redirect to a specific service. and a parent account acct:me@sour.is that would reference them in some way. either in properties or aliases.

I’m planning to include “gemini tinylogs” on the twtxt page on Antenna. As soon as I have the time and energy for it. (https://codeberg.org/bacardi55/gemini-tinylog-rfc)

@bml@twtxt.net Yup, several. My favorite is RFC 1149, another that’s since been implemented. https://en.wikipedia.org/wiki/April_Fools%27_Day_Request_for_Comments

Peter Saint-Andre: RFC 8838: Trickle ICE ⌘ Read more…

@xuu@txt.sour.is Not too happy with WKD’s use of CNAME over SRV for discovery of openpgpkey.. That breaks using SNI pretty quick. I suppose it was setup as a temporary workaround anyhow in the RFC..

RFC-61 — 365 RFCs https://write.as/365-rfcs/rfc-61

Update: scans of early RFCs — 365 RFCs https://write.as/365-rfcs/update-scans-of-early-rfcs

RFC-19 — 365 RFCs https://write.as/365-rfcs/rfc-19

RFC-5 — 365 RFCs https://write.as/365-rfcs/rfc-5

RFC-2 — 365 RFCs https://write.as/365-rfcs/rfc-2

RFC-1 — 365 RFCs https://write.as/365-rfcs/rfc-1

mnot’s blog: How to Read an RFC https://www.mnot.net/blog/2018/07/31/read_rfc

RFC 439 - PARRY encounters the DOCTOR https://tools.ietf.org/html/rfc439