pretty much the title.
You must log in or register to comment.
RISC-V
I want open-source hardware
Is there a good resource out there for wrapping my head around RISC-V? Last time I read a wiki my head hurt haha. Seems cool, though.
In principle it’s just “slimmer ARM”. RISC-V is also extremely dedicated to using memory mapped IO rather than older style IO x86_64 supports.
Think lots of registers, a fun zero register that is always zero, and memory mapped IO.
ARM is also reduced-instruction set but I don’t know how they differ. Is the instruction set somehow more reduced?
Aren’t they more like a hybrid instruction set and architecture?
some good news on that front https://github.com/OpenXiangShan/XiangShan
Imma stick with ARM and x64 ngl, ik it’s not open hardware but I don’t really mind that but cool to hear.
Pipewire, Wayland, Matrix.
JPEG-XL (someone already mentioned it as .jxl below) image files.
- competitive with AVIF compression levels
- not recycling video compression, so you get benefits like progressive loading
- JPEG transcoding - can take existing JPEG files (so much of the existing images online) and shrink their size by ~20% with literally no change to the presented image, and this is easily reverable. The amount of data this would shrink without risk of altering the data is HUGE.
There are a ton of other benefits but those are the three I’m most excited about.
Wayland
ActivityPub, I’m sick of corporate social media
Fedora moving forward with UKIs, bootc and composefs
First thing that comes to mind is RISCV. Although it’s not new, it is gaining traction in consumer computing
I want ECH (Encrypted Client Hello) to finally take off. https://support.mozilla.org/en-US/kb/faq-encrypted-client-hello
Implementation is still lacking unfortunately.
I doubt it. Today there is a huge trend towards censorship in the world. And ECH is exactly what a censor would not want. It is already blocked in Russia after Cloudflare enabled it by default and I would expect it to be blocked in the west “for anti-piracy reasons” very soon.
ECH is intended for privacy, not for circumventing censorship.
If the next TLS version enforces ECH, plaintext SNI will die out at some point on its own.
Intensions do not metter in this case. It can be used for that and that’s enough. If you block any connections that use ECH (by blocking cloudflare-ech for example) users will have no choice but to fallback to unencrypted CH.
for me, currently the problem is over reliance on Cloudflare, which is yet another big tech company
In what sense? ECH does not rely on Cloudflare anymore than QUIC relies on Google.
i may be wrong here, but if i remember correctly, in ech, essentially our first communication is done with some central server (which as of now is mostly cloudflare) and then they make some connection with target server, and then a channel is established between us and target. my google-fu brought me this , which is basically this only
https://cf-assets.www.cloudflare.com/zkvhlag99gkb/3C9ceBTx5AQXu8tS0lgzdF/55ea89f5a56843db15296b2b47f7b1c2/image3-17.png (https://blog.cloudflare.com/encrypted-client-hello/)
I am unfamiliar with QUIC, and quick search basically tells it is kinda like multilane highway for udp.
If I have to compare, (not a network engineer or a person who has studied networking, to me anything beyond the simple protocols seems magic), QUIC seems like a techt which is only used after you have made connection with target, so its implementation is google independent (they seem to be lead developers for this). Whereas in ECH, cloudflare are the primary devs, but also the holder for the public keys (someone else can also be the holder, but i dont know of any other provider currently, maybe my lack of knowledge here)
Essentially just an extension of your point that implementation is lacking
essentially our first communication is done with some central server
No, the first communication is made with your DNS server to fetch the key for encryption from an HTTPS record. If a record with key is found it is used to encrypt the Client Hello, otherwise it falls back to the unencrypted variant.
Cloudflare is not involved, unless you are hosting your domain through Cloudflare of course.
I am unfamiliar with QUIC, and quick search basically tells it is kinda like multilane highway for udp.
QUIC is primarily used for HTTP/3. The protocol was engineered and proposed by Google, same as with ECH and Cloudflare.
Maybe HDR on linux? I’m fairly clueless about how it all works under the hood, but I’m currently on debian 12 and I’m hoping that by the time 13 comes around it will just work without me needing to do any manual system tweaks. As I understand it, it’s currently semi-working or fully-working in KDE6, but I’m still on KDE5 until debian 13 comes out.
I’ve recently switched to Fedora KDE running version 6 and HDR looks great. Well worth the wait.
The Solid protocol specification or anything similar (it doesn’t have to be that specific protocol).
For example, registering to a website or service actually creates a local secure database/bucket/pod where that website/service organizes/sort/manipulates our data and stores all generated modified data/metadata within our local personnal server, every time we interact with that same external website/service it gets access to the database/bucket previously created. (Ideally) no personnal data should be stored on external servers/machines outside our control and without our explicit consent.
VRR that works with multiple monitors connected. Unfortunately that’s an Nvidia driver issue rather than a missing Linux protocol, so could be waiting a while.
lol. I searched “nvidia 570 Linux” less than a week ago and nada. Just did it again based on you comment and it looks like it was released 2 days ago.
You’re an absolute legend! Thanks for the heads up.
JXL.
Being able to pinch to zoom on my laptop touchpad
You should be able to… Are you still on x or Wayland?
I am on Mint Cinnamon 21.3 and I cannot use Wayland
IndieWeb in general and the h-entry and WebMentions specifically.
Collectively they promise a highly personalised web experience that maintains ownership of your own content while encouraging socialisation across platforms, while avoiding the sustainability and scale limitations of activitypub.
I also want to see XMPP/OMEMO have a comeback.
Hi, does it have any advantage over greping your RSS feeds for your blog’s URL?
What is “it”? Webmentions? Webmentions can be sent from anywhere, not just places you’re actively monitoring. They can be used for example to create a comments section on your blog which amalgamates comments from various syndication points.
That is, you post to your blog, you post a link to your blog post to twitter/Facebook/lemmy etc, and comments or replies from any of those can show up on your blog itself if you so choose.
Alright, that’s pretty cool, sorry – I thought it was a list of links automatically inserted in lieu of comments.
I’ve been trying to get into the IndieWeb for years, but I’ve been struggling to implement it. Doesn’t it rely on a central server too? Can we use it in a fully e.g. decentralized or federated way – would it even make sense, or could we easily switch to another flagship server, as we did with the Freenode takeover?
Please feel no pressure to reply, I can do my own research ^_^
