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
OpenSSL 3.5.0 released
Version\
3.5.0 of OpenSSL has been released. This release adds support for
server-side QUIC ( RFC 9000), a
new configuration option ( no-tls-deprecated-ec
) that disables
support for TLS groups deprecated in RFC 8422, and more. ⌘ Read more
twtxt
, the voting period has started and will be open for a week.
https://eapl.me/rfc0001/
thanks @prologic!
@bender the idea of the RFC was to reach an agreement on a difficult problem, receiving proposals, and the voting is a simple count to gauge the sentiment of “is this a problem worth to be fixed?, are we committed to implement a change in our clients?”
But that’s a fair point. What do the community expect? What do y’all expect?
[$] Multiple memory classes for address-space isolation
Brendan Jackman has been working to try to get ahead of the next hardware CPU
vulnerability
before it gets discovered. In January, he posted the second version of
a patch set that introduces
address-space isolation (ASI) as a way of
preventing future CPU vulnerabilities from leaking important
information. The core concept is to ensure that data that is not currently
ne … ⌘ Read more
TIL that RFC means Request For Comments
Hi everyone,
I’ve drafted a Request for Comments (RFC) to improve how threads work in twtxt:
https://git.mills.io/yarnsocial/twtxt.dev/issues/18
I’d love your feedback! Please share your thoughts on anything that could be better explained, check if the proposed dates work for everyone, and I invite you to join the discussion…
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.
@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
interesting RFC dated April 1st, 1998: Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0):
looking at the date this was published, i think the authors originally meant this as an apil’s fool joke/prank.
funny because now we have IOTs and this is somewhat a reality today :P
@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
@kas@enotty.dk The only thing stopping me from implementing webmentions by myself is RFC 5988. Crazy stuff…
@kas@enotty.dk The only thing stopping me from implementing webmentions by myself is RFC 5988. Crazy stuff…
briefly thinking about using RFC 5147 for message identifiers, e.g. https://buckket.org/twtxt_news.txt#line=2