FEPs, SLEPs, APEs, AIPs, PEEPs, CEPs, SKIPs, SPECs, TIPs, CFEPs, NEPs, JEPs, BIPs, DEPs, DEPs, KEPs, JEPs, WEPs, IPEPs...
A lot of projects name proposals after PEPs rather than RFCs.
What are they? Where did PEPs come from? Here's @flufl on the origin!
https://hugovk.dev/blog/2025/peps-and-co/
#Python #PEP #RFC #etymology #history #blog
"This ABNF could have been a regular expression."
RFC 9743: Specifying New Congestion Control Algorithms, M. Duke, Ed., et al., https://www.rfc-editor.org/info/rfc9743 #RFC RFC 5033 discusses the principles and guidelines for standardizing new congestion control algorithms. This document obsoletes RFC 5033 to reflect changes in the congestion control landscape by providing a framework for the development and assessment of congestion control 1/2
Pixelfed Friend Discovery 
Check your contacts to see if they are on Pixelfed, without compromising their privacy, or sharing their info by using the k-Anonymity algo:
- Your address book/contact list stays on your device
- We only send anonymized, partially-hashed data
- k-Anonymity ensures no individual can be identified
- Discovery service operated by the Pixelfed Foundation, and opt-in per user
We would love your feedback!
PSA: die Weiterverwendung der obsoleten DNS-Blockliste "NixSpam" / ix.dnsbl.manitu.net führt zu Fehlern bei der Zustellung von E-Mails. Administratoren der E-Mail-Server müssen hier selbst aktiv werden.
Hinweise dazu:
https://nixspam.net/help/enduser/
Interesting #cryptography thing I stumbled upon: the #RFC for #PrivacyPass.
https://www.rfc-editor.org/rfc/rfc9576.html
"Privacy Pass is an architecture for authorization based on #privacy-preserving authentication mechanisms. In other words, relying parties authenticate Clients in a privacy-preserving way, i.e., without learning any unique, per-Client information through the authentication protocol, and then make authorization decisions on the basis of that authentication succeeding or failing. Possible authorization decisions might be to provide Clients with read access to a particular resource or write access to a particular resource."
RFC 9748: Updating the NTP Registries, R. Salz, https://www.rfc-editor.org/info/rfc9748 #RFC The Network Time Protocol (NTP) and Network Time Security (NTS) documents define a number of registries, collectively called the NTP registries.
L'Internet est aujourd'hui un service indispensable à toutes les activités humaines. Un accès correct à ce réseau est donc crucial. Mais plusieurs problèmes limitent l'accès à l'Internet ou à plusieurs de ses services. L'#IAB avait organisé en janvier 2024 un atelier sur cette question, atelier dont ce #RFC 9707: "Barriers to Internet Access of Services (BIAS) Workshop Report" est le compte-rendu.
I just put together a big long post on what if anything @pidgin 3 should do when it comes to original messages after their authors have edited or deleted them.
We're still a long way away from this, but it's good to thing about these things before we actually get to implement.
Voting and registration is required via our identity provider which is just meant to fight spam.
At any rate, let me know what you think!
https://discourse.imfreedom.org/t/rfc-archiving-of-edited-redacted-and-ephemeral-messages/251
And another new RFC I have co-authored: DNSSEC Trust Anchor Publication for the Root Zone
https://datatracker.ietf.org/doc/rfc9718/
→ RFC 9421: HTTP Message Signatures (par @bortzmeyer)
https://www.bortzmeyer.org/9421.html
« Ce RFC spécifie comment on peut signer cryptographiquement et vérifier des messages HTTP, afin de s'assurer de leur authenticité. »
They say when you use regex you have two problems. I tend to have one less problem...
Case in point, here's a tokenizer for https://www.rfc-editor.org/rfc/rfc5801.html#section-4.
^(?:(?P<nonstd>F),)?(?P<cb>[npy])(?:=(?P<cbname>[^,]+))?,(?:a=(?P<authzid>[^,]+))?,
Validation still has to be done in the application, but this is still way easier than writing and maintaining a lexer.
This cheetah SHOULD receive regular cuddles, otherwise he MAY get sad. That SHOULD NOT happen, as his performance is degraded otherwise.
RFC 9639: Free Lossless Audio Codec (FLAC), M.Q.C. van Beurden, et al., https://www.rfc-editor.org/info/rfc9639 #RFC This document defines the Free Lossless Audio Codec (FLAC) format and its streamable subset. FLAC is designed to reduce the amount of computer storage space needed to store digital audio signals. It does this losslessly, i.e., it does so without losing information. FLAC is free 1/3
Extending the meta tags would be fairly straightforward. In addition to the existing "INDEX", "NOINDEX", "FOLLOW", "NOFOLLOW", we could introduce "MODELTRAINING" and "NOMODELTRAINING".
Of course, just because there is an RfC does not mean that anyone will follow it. But it would be a start, and something to push for. I would love to hear your opinion.
3/3
This is not an acceptable situation and therefore I propose to extend the robots.txt standard and the corresponding HTML meta tags.
For robots.txt, I see two ways to approach this:
The first option would be to introduce a meta-user-agent that can be used to define rules for all AI bots, e.g. "User-agent: §MODELTRAINIGN§".
The second option would be a directive like "Crawl-delay" that indicates how to use the data. For example, "Model-training: disallow".
2/3
RFC 9636: The Time Zone Information Format (TZif)
Ce nouveau #RFC documente un format déjà ancien et largement déployé, #TZif un format de description des fuseaux horaires. Il définit également des types MIME pour ce format, application/tzif et application/tzif-leap. Il remplace le premier RFC de normalisation de ce format, le RFC 8536, mais il y a très peu de changements. Bienvenue donc à la version 4 du format, spécifiée dans ce RFC.
