Tootfinder

Opt-in global Mastodon full text search. Join the index!

@fanf@mendeddrum.org
2025-09-08 15:56:41

looking at an old rfc i was reminded of how pointless “security considerations” sections used to be
which made me wonder what rule the authors were supposed to be obeying
the first security considerations section was in RFC 1060 which set a bad example that almost everyone followed
r…

@jtk@infosec.exchange
2025-09-05 17:54:35

Weekend Reads
* Preventing route leaks
blog.apnic.net/2025/09/05/prev
* IPTV piracy network report

@timbray@cosocial.ca
2025-08-23 10:29:54

Three small announcements:
1. RFC 9839, a guide to which Unicode characters you should never use: rfc-editor.org/rfc/rfc9839.htm
2. Blog piece with background and context, “RFC 9839 and Bad Unicode”:

@grifferz@social.bitfolk.com
2025-08-09 14:32:09

"I just want my life back!"
New from Chuck Tingle. This Summer don't stray too far from the standards track, lest you be…
Pounded in the Ass By the RFC Process
mailarchive.ietf.org/arch/msg/

@stf@chaos.social
2025-07-24 20:15:14

Woohoo #OPAQUE now is an #IETF #RFC 9807!
rfc-edi…

@frankel@mastodon.top
2025-08-02 08:11:03

Working with the new #Idempotency Keys #RFC
httptoolkit.com/blog/idempoten

@azonenberg@ioc.exchange
2025-09-08 07:32:59

What's the go-to for non-Microsoft non-Google email hosting these days?
Requirements:
* Supports proper RFC compliant SMTP/IMAP TLS access. No oauth, no EWS, no exchange nonsense. Needs to be usable on e.g. a headless box without a web browser, command line clients, etc.
* Reasonably priced for a handful of accounts across a bunch of domains
* Setup and forget third party hosting, I don't have an IP block suitable for mail hosting in house and I don't want …

@awinkler@openbiblio.social
2025-08-13 08:59:54

Has anybody seen #RFC9727
(api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs) implemented anywhere on the internet yet?
rfc-editor.org/rfc/rfc9727.html

@fanf@mendeddrum.org
2025-07-30 08:42:03

from my link log —
Intra-procedural lifetime and borrowing analysis in Clang.
discourse.llvm.org/t/rfc-intra
saved 2025-07-15

@arXiv_csCL_bot@mastoxiv.page
2025-10-07 12:05:12

JSON Whisperer: Efficient JSON Editing with LLMs
Sarel Duanis, Asnat Greenstein-Messica, Eliya Habba
arxiv.org/abs/2510.04717 arxiv.org/pdf…

@mgorny@pol.social
2025-10-04 16:01:41

No to poprawcie mnie, jeżeli się mylę, co do aktualnego stanu #OpenPGP.
Po pierwsze, jest dawne #RFC4880bis, aktualnie przepychane jako "#LibrePGP", używane przez

@adulau@infosec.exchange
2025-10-04 06:48:40

OpenSSL Security Advisory [30th September 2025]
#openssl #vulnerability

@zachleat@zachleat.com
2025-07-21 22:30:00

@… Temporal seems to use RFC 9557 which is a much stricter date format developer.mozilla.org/en-US/do

@gwire@mastodon.social
2025-08-05 12:51:59

TIL that chatgpt signs HTTP requests with RFC 9421 signatures, which initially seems over the top, until you consider the scope of what agentic systems might end up doing.
fedi.simonwillison.net/@simon/

@qbi@freie-re.de
2025-07-16 07:34:47

#PGP bzw. genauer #OpenPGP gibt es in verschiedenen Standards:
- RFC 2440
- RFC 4880
- RFC 9580 und
- LibrePGP
Johannes Roth und Falko Strenzke haben die Unterschiede zwischen den wichtigsten Standards herausgearbeitet:

@timbray@cosocial.ca
2025-08-29 16:14:17

A few days back I tweeted and blogged about the brand-new RFC 9839, and also published the first draft of tiny Go library to help enforce the subsets defined in the RFC. Got lots of useful input on the library and have progressed it enough to do a v0.8.0 release: github.com/timbray/rfc9839

@khalidabuhakmeh@mastodon.social
2025-07-28 15:43:06

Some modernization planning for Duende IdentityServer. If you are in the #dotnet space, please leave your thoughts. github.com/orgs/DuendeSoftware

@kurtsh@mastodon.social
2025-08-20 22:03:15

Quantum Computing-resistant cryptographic algorithms now available for .NET developers.
✅ .NET 10 Preview 7 - Module Lattice Digital Signature Algorithm
github.com/dotnet/core/blob/ma

@publicvoit@graz.social
2025-08-23 08:08:24

«Unicode is good. If you’re designing a data structure or protocol that has text fields, they should contain #Unicode characters encoded in #UTF8. There’s another question, though: “Which Unicode characters?” The answer is “Not all of them, please exclude some.”
This issue keeps coming up, so [

@zachleat@zachleat.com
2025-07-18 13:50:17

@… I did look through those APIs and it looks like they parse RFC 9557 which is less forgiving developer.mozilla.org/en-US/…

@cketti@social.int21.dev
2025-08-19 00:42:06

I scored 20/21 on e-mail.wtf and all I got was this lousy text to share on social media.
This is an entertaining quiz. But RFC 5322 is not the right place to look for an answer to the question of what a (syntactically) valid email address is.

@arXiv_astrophEP_bot@mastoxiv.page
2025-08-22 09:07:20

Enhanced Predictive Modeling for Hazardous Near-Earth Object Detection: A Comparative Analysis of Advanced Resampling Strategies and Machine Learning Algorithms in Planetary Risk Assessment
Sunkalp Chandra
arxiv.org/abs/2508.15106

@gwire@mastodon.social
2025-09-01 06:51:00

The correct regional coding for a "London" IP address in RFC 8805 is
10.0.0.0/16,GB,GB-ENG,London,
This is because there is no ISO 3166-2 code for London, just for its individual boroughs. The code GB-LND is often used to represent London, but this specifically identifies City of London which has the property of being London's central point geographically, but is not London itself.
(I think that a "GB-LON" that covers City and 32 boroughs would be go…

@zachleat@zachleat.com
2025-07-25 14:37:56

@… so basically, I had the library and test suite already ready, just needed to make some small changes in the library for RFC 9557 compat (and to save ~55KB over the full Temporal polyfill lib)

@arXiv_csCR_bot@mastoxiv.page
2025-09-16 12:03:57

Time-Based State-Management of Hash-Based Signature CAs for VPN-Authentication
Daniel Herzinger, Linus Heise, Daniel Loebenberger, Matthias S\"ollner
arxiv.org/abs/2509.11695

@zachleat@zachleat.com
2025-07-22 21:24:33

One more entry in my epic date parsing adventure. I’ve shipped a breaking change to this library to ensure that all valid date strings supported in Eleventy v4 will be RFC 9557-compatible, ensuring friendliness with the standardized Temporal APIs coming to a JavaScript runtime near you. Our full test suite runs against both!
Read (a little) more:

@arXiv_csNI_bot@mastoxiv.page
2025-09-15 08:46:21

RFSeek and Ye Shall Find
Noga H. Rotman, Tiago Ferreira, Hila Peleg, Mark Silberstein, Alexandra Silva
arxiv.org/abs/2509.10216 arxiv.org/p…

@zachleat@zachleat.com
2025-07-17 22:04:22

Researching ISO 8601 and RFC 3339 date parsing and found this excellent resource: ijmacd.github.io/rfc3339-iso86
Tried a few packages to solve this problem (dayjs, date-fns, luxon, moment). Unfortunately they are either not accurate enough or very large 😭

@gtn@defcon.social
2025-07-12 17:27:43

Safefetch is close: currently rewriting commit messages closer to required style
Then it'll be off to linux-hardening for initial feedback and testing as an RFC
It's taken about a year to forward port the patchset