I was actually surprised to find out QUIC is fairly close to being default.
Wikipedia
HTTP/3 uses QUIC, a multiplexed transport protocol built on UDP.
HTTP/3 is (at least partially) supported by 97% of tracked web browser installations (thereof of 98% of "tracked mobile" web browsers), and 29% of the top 10 million websites.
Unfortunately the reality of IPFS is that despite its huge funding it was poorly designed from the start and still to this day has much slower loading times then my I2pd instance (despite i2p transmiting messages through multiple encrypted proxies), to the point where the company working on the rust implementation determined it was so bad they had to scrap the whole thing to make something that actually worked. Not to mention that I managed to have my server taken over by some kind of malware by downloading a particular piece of content.
Thanks, that was an interesting read! I always felt IPFS wasn’t ready yet, but the value it tries to provide of being a file system, I’ve found no real alternative to. Very good to read that iroh is willing to look beyond the IPFS spec to provide its values with better performance. I hope it works out.
Technically yes by rewriting ipfs’s code, but due to ipfs’s flaws you would be better off using something like freenet/hyphanet which has been designed for that purpose and has been successfully running since 2000, with the added benefit that the data is actually stored in the network by others instead of just by you (at least when you often request the data)
Also the user interface and builtin solutions for torrenting, hosting, address booking make it way more user friendly for people to start using I find.
OpenTelemetry and in particular I wish more protocols had Traceparent propagation support and more software had support for sending spans and traces to an OTLP endpoint to construct a full picture of everything that is going on in a distributed system.
There are a bunch of message broker services out there, and having a consistent set of common keys along with a documented process for transforming events to/from different systems means that this kind of data can move through different systems without getting mangled. It does have a spec for JSON, so it can be considered just a standardized JSON blob with transformation rules. But it also has a protobuf spec, specs for MQTT, NATS, HTTP, Avro, etc. It’s a common language for all these systems.
I wish Microsoft Office would use the .odf standard by default. Or, failing that, it’d implement its own published .docx specification correctly, so other office suites can be compatible.
The entire purpose of Microsoft standardizing OOXML and implementing it wrongly in Office was to make other office suites irrelevant. ODF was already standardized and countries would have adopted it if MS didn’t do the same with OOXML. They stuffed the ISO with members supporting them to do it.
And now that OOXML is a viable standard, they implement it wrongly so that other office suites can’t be compatible with MS Office without a lot of extra effort. Any incompatibilities with MS Office will be considered as the fault of other office suites by the general public and government officials.
Expecting MS to do what’s right for the customers is putting too much faith in their nonexistent sense of ethics.
Markdown. Its only in tech-spaces that its preferred, but it should be used everywhere. You can even write full books and academic papers in markdown (maybe with only a few extensions like latex / mathjax).
Instead, in a lot of fields, people are passing around variants of microsoft word documents with weird formatting and no standardization around headings, quotes, and comments.
Man, I’ve written three novels plus assorted shorter form stories in markdown.
There’s a learning curve, but once you get going, it’s so fluid. The problem is that when it comes time to format for release, you have to convert to something else, and not every word processor can handle markdown. It’s extra work, but worth it, imo.
Publishers are pissy about such things. Even self publishing (which is what I do now), the various outlets still have limits to what they will use. Amazon accepts something like three file formats, including their own, and pdf isn’t on the list.
I could just do pdf for directly giving them away to people, but even then, epub is usually a better pick in terms of readability since that’s the standard for actual books since ereaders tend to display it better than pdfs. Most people reading books via files would be using something that can give a better experience with epub vs pdf.
Pandoc + [your markdown editor of choice] is magic. Some editors even come with Pandoc as a dependency so you can export to more or less anything from the GUI. I think GhostWriter and Zettlr at least (I honestly can’t be sure, I’ve changed editors so often and now I just have some Pandoc conversion scripts in my file manager menu).
ReST (restructured text) is a good middle ground. I just wish it had more support outside of the python community. It could use some new/better tooling than Sphinx
Markdown is terrible as a standard because every parser works differently and when you try to standardize it (CommonMark, etc.), you find out that there are a bajillion edge cases, leading to an extremely bloated specification.
What’s the alternative? We either have everything specified well, or we’ll have a million slightly incompatible implementations. I’ll take the big specification. At least it’s not HTML5.
Commonmark leaves some stuff like tables unspecified. That creates the need for another layer like GFM or mistletoe. Standardization is not a strong point for markdown.
I believe commonmark tries to specify a minimum baseline spec, and doesn’t try to to expand beyond that. It can be frustrating bc we’d like to see tables, superscripts, spoilers, and other things standardized, but I can see why they’d want to keep things minimal.
Asciidoc is a good example of why everything should be standardized. While markdown has multiple implementations, any document is tied to just one implementation. Asciidoc has just one implementation. But when the standard is ready, you should be able to switch implementations seamlessly.
Markdown is awesome, I agree! I did not realize you could extend markdown with anything other than html. The html extension is quite nice to do anything that markdown doesn’t support natively, but I wish there was an easier way to extend markdown. Maybe the ones you listed are what I need.
My main wishlist for markdown, is a better live collaborative markdown editor. Hedgedoc works, but it’s showing it’s age, and they don’t seem to be getting close to releasing v2.
Etherpad also has a markdown extension, but it doesn’t import / export that well.
Depends on the type of book. Since you need HTML for all non default styles. Therefore, it raises the bar… you need a bit of web dev knowledge which removes the biggest benefit of markdown: simplicity / ease of use.
IOT devices shouldn’t connect to wifi. ZWave or zigbee is much better suited to IOT stuff, but it seems to mostly get adopted in very limited, locked down proprietary shit like Hue Lights.
Yes but at least Hue (and IKEA and LIDL and many other brands’) lights work well with open Zigbee coordinators, like deconz and ZHA in Home Assistant.
I wish there were more Zigbee and Zwave and less WiFi IoT devices too. I don’t even have a Zwave coordinator because I never found anything I wanted with Zwave support.
There’s only one case I’ve found where Wi-Fi use seems acceptable in IoT: ESPHome. It’s open-source firmware for microcontrollers that makes DIY IoT sensors and controls accessible over LAN without phoning home to whatever remote server, without trying to make anything accessible over the Internet, and without breaking in any way if the device has no route to the Internet.
I still wouldn’t call Wi-Fi use ideal even there; mesh can help in larger homes and Z-Wave/Zigbee radios tend to be more power efficient, though ESP32 isn’t exactly suited for a battery-powered device that’s expected to run 24/7 regardless.
Google has used RCS as their latest attempt at entering the messenger market. I really don’t see why anybody else would want to adopt it under these circumstances. I mean Samsung did but Samsung is playing their own little paranoid game with Google, they don’t really give a crap about RCS.
Basically Google killed RCS. They will never be able to make anybody adopt it against their will in the EU, people will stick to what messenger services they’re already using. If they ever attempt to turn it on by default in their own app it will turn into a regulatory issue so fast their head will spin.
Rcs was designed from the ground up to be handled by the carrier in clear text like sms, it doesn’t incorporate encryption in any way and doesn’t do much at all to address the untrustworthy nature of carriers and law enforcement nowadays.
It’s like those two protocols started developing at the same time and only google kept extending rcs to keep some degree of feature parity with imessage.
If we had to ditch iMessage it ought to be for some third type, not for questionably secure rcs and what new bubble color can be used to indicate that someone’s using an unencrypted rcs server?
I want us to stop using communication protocols that are tied to our connectivity providers. Let alone tied to a specific piece of hardware (SIM card).
“Telephone providers” should be just another ISP. And whatever I do over the network shouldn’t care if it is running on a mobile network or a landline fibre.
While we are at it let’s fuck off with this SIM shit. You don’t get to run code on my device. Give me an authentication key that I can use to connect to your network and then just transfer my packets. My device runs my code.
Add comment