oops https://x.com/_markel___/status/1828112469010596347

progress https://www.neowin.net/news/microsoft-is-bringing-annoying-windows-11-start-menu-ads-to-windows-10/

Considering Durov's arrest, it is not huge surprise since:

1. Telegram's security is not that great. Not sure if it is legislation compliant but I doubt it.
2. It has become the place for buying malware and stole data.
3. It has become the place for buying narcotics.

For two last I have no idea why is Telegram preferred over Tor these days.

https://en.wikipedia.org/wiki/Arrest_of_Pavel_Durov

Hands off the best Skin for @uheplugins #Diva:

https://plugmon.jp/product/mona/

There's also one for Tyrell N6:

https://plugmon.jp/product/mona-n6/

#plugmon

Just in case anyone's still stuck with the SBAT issue on the Linux systems and can't easily disable secure boot for whatever reason - boot a live Fedora image, open a terminal, run

sudo mokutil --set-sbat-policy delete

and reboot. shim should now clear the sbat policy and you're back in business. Don't allow Windows Update to run again until things are sorted.

If you need help trying to figure out what version of Node, Ruby, Postgres, Redis, Elasticsearch, Libvips, FFmpeg, ImageMagick you need to upgrade your Mastodon instance you can always check out https://www.mastoreqs.com in addition to reading through the release notes of the new version.

#MastoAdmin

Learning new cool stuff for the upcoming work, i.e. extending LLVM IR processing :-) There's no pressure to do that but cannot help myself.

If I have a options, I try to pick jobs based getting to do something I've watched from the audience but would require way too much focus without being primary job.

I find it very clever and disruptive to consider RVA20U64 as a bytecode format with only less than 50 opcodes, which trivially map to ARM and x86 user space code. LLVM plugins should be able to do all kinds of optimizations in the JIT architecture, speeding up both the turnaround time of the compilation and quality of the compiled code for the target architecture (i.e. aarch64 or x86_64 in practice).

RISC-V CPU "softcore" (invented this term now because no idea what it is) is at least the first bytecode I actually like.

https://github.com/riscv/riscv-profiles/blob/main/src/profiles.adoc#rva20u64-profile

#riscv

Can I buy "BTW, I don't use Arch Linux" T-shirt? Came to mind and could not help myself 🤐

After using Aerc over a year I suddenly realize that I can emulate set records= simply by commanding for a selection :move Trash.

Despite this, I’ve been using :move a lot like probably the same day I started using aerc in the first place 🌻

#email #aerc #mutt

PolkaVM is based on RVI20U64, which is a RISC-V profile lacking machine (M) and supervisor (S). The ALU of RVI20U64 has 47 opcodes in total.

I also noted FENCE and FENCE.I are in the profile. Are they useful for a single core CPU package?

Does this architecture have pmpcfg* registers? It would not make any possible sense to me so I’m only sanity checking here.

#polkadot #riscv

" It’s a paradigm shift for the Linux desktop, crafted in Rust."

OK great it is written in Rust, but what is the paradigm shift? I see windows, icons, a docker and shit.

https://www.both.org/?p=7014

Here's a fascinating look at the first IBM PC 5150, from my friend David who wrote the training documentation.

https://www.both.org/?p=7098

LOL, apparently #Wickr is these days an #AWS product. AFAIK, it has been like the choice of modern world drug dealers acting in #Tor. Famous from umh tabloids 🤷 #Amazon

I had missed that AWS discussed how they use #eBPF to implement network policies, optimize TCP performance, and reduce Lambda function cold starts.

Recording: https://youtu.be/pVJHljuz1F0

Microsoft breaking a bunch of dual-boot systems by revoking insecure versions of grub during a standard Windows update is, uh, not great and was not supposed to happen, but it's worth mentioning that systems broken by this were running known insecure bootloaders and anyone running a distro that's actually on top of security updates was unaffected

(Edit to add: I wasn't terribly clear here. It's not the user's fault if their distro fails to deal with this, it's the distro's)

https://www.hs.fi/suomi/art-2000010645468.html

Here's a link to the slides for my "Why are there so many kernel CVEs?" talk I gave at OSS China yesterday:
https://kccncossaidevchn2024.sched.com/event/ed2b39a9a0cdfc1df18de67ce0c2f6be

Link to git repo for the slides if the schedule site acts odd for you:
https://git.sr.ht/~gregkh/presentation-security

It was fun, and will be the "set up" for my Kernel Recipes talk in Paris in a few weeks (only 3 conferences to go between now and then, travel is back in full swing.)

https://www.youtube.com/watch?v=yBv4kWsi4TE

At Profian I did Rust with managed wasm bytecode payloads.
At Tampere University I hacked RISC-V SoC's.
At Parity Technologies, I'll do Rust with managed RISC-V *bytecode* payloads.

My work career seems to move forward by combining patterns.

I think Linux would be better off not supporting async feature of Rust.

It's not that it cannot be done but it will result long-term maintained code that is hard to reverse to opcodes at the CPU core just by looking at the snippet code.

This is exactly the gist of any possible kernel patch review..

I'm not disregard its usefulness in user space code but it could be even counter-productive tool in kernel code.

It's the added cost of time for kernel maintainers that weights here. Most (all) could cope with non async Rust from the perspective of what CPU does when it executes a specific peace of Rust code. Developer productivity is the most insignificant portion of kernel development cycle. I'm 100% sure that async is not existential feature, meaning that any possible feature could not be implemented without it.

#rust #linux #kernel