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

@ljs have not noticed so far. it has felt pretty reliable to me :-) if i would really want to put cash to training watch I would go for something from Suunto.

My Casio looks rad too: https://www.amazon.de/dp/B09C65FS32?ref=ppx_yo2ov_dt_b_fed_asin_title

And its data connects to Apple's app ecosystem (can upload through bluetooth) so have been happy :-)

@ljs my fancy gshock casio watch counts my steps ;-)

@kernellogger afaik slackware still uses lilo in the default install ;-)

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 🤐

Without having a clue I'm 100% sure that UK has that kind of businesses scattered around the island.

@ljs My parents take their apples to some kind of juice factory and then you can get it as juice and//or jam. If I had to deal with apples, I'd probably do the same, take them somewhere, pay and support a small business and get consumable products :-)

@raggi Actually I'll stretch this a bit and try to find something modest to contribute to rust-linux from areas where I hover in the kernel domain (maintain or contribute), and I can somehow convince myself that it would be a fit for using async.

That is probably for a kernel maintainer the best possible to draw bridges than do any possible low-hanging fruit alike random contribution. I wait week or few but proactively keep this idea in my mind.

Thanks for the inspiration!

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

@raggi [an CC if you, might take next week not sure

@raggi hmm.... I'll just grep async use and write a doc :-) I already have material for the commit message in this thread.

@raggi Right, and lowers the barrier a bit for new contributions. We can probably all admit at least that async can be "a bit" a daunting at first so something to hold on to does make a real difference. Something is at least always better than nothing.

@raggi Hmm…

So one option would be to create Documents/rust/async-guidelines.rs and document pre-existing usage patterns in Linux. I think it would be better try not to over-engineer the document. One example would documenting async itself. It is probably the best idea to keep it compact and punctual.

All you need to do then is just modifying the existing guidelines and adding sometimes completely new guidelines based on the patches.

Now, if I send a Rust patch with some async code, it will now be less likely to be against maintainers expectations. That results less noise in the mailing list, and patches landing more quickly. Or that’s I’d see it.

Way more important benefit would be that async would be “existentially” sealed to the kernel ecosystem early on.

I think this just like basic governance and risk management, not IMHO a big deal :-)

@ljs the idea is so stupid that my best guess is that someone made it on purpose

i should get a fellow position at DARAP from doing [1] if that idea is considered sane

[1] https://idle.slashdot.org/story/18/12/01/2331223/developer-misinterprets-linux-code-of-conduct-suggests-replacing-f-word-with-hug i