GCUMstlyHarmls
https://almalinux.org/blog/2026-10-30-cve-2026-98432/#tempor...
> This one I still don't know whether is an RCE or DoS in practice!
It is. It depends on dumping (potentially) a lot of traffic at you to "luck" into the cpu core scheduler but obviously computers can increase their luck by doing something a lot. The RCE is real, the risk is probably lower if you're not high profile simply because it requires some about of CPU spend on the attackers side, not something that you just fire off at anything that will respond to a ping or `GET /config.php`.
> I don't know whether a computer blocking connections via a "normal firewall" protects me or not! It's incredibly frustrating.
It doesn't. Apply the above rules until your kernel is updated.
Radicle has some association with cryptocurrency, which is a bit ick to me, but as far as I understand it, it's actually a non-profit and the crypto was more of a grant than buy-in.
> Radicle’s Collaborative Objects (COBs) provide Radicle’s social primitive. This enables features such as issues, discussions and code review to be implemented as Git objects. Developers can extend Radicle’s capabilities to build any kind of collaboration flow they see fit.
I think siblings are correct that the more widespread this is, the less effective once every dump is run through a "also look for keys in the binary" step.
You can generally request to get off it though, at ~1-5$/m extra cost.
Now (after ... gosh, 6, 7, 8? years probably) I love it, use it everywhere and other monospace font feels super w i d e and weird.
What quantization are you running for these? Like, you cant just run the "real" ones on your laptop right?
Wouldn't the performance of Qwen3.6-35B-A3B be drastically different if its quantized to 2b, 4b, 5b, etc? And also be effected by who did the quantization?
When I do something "heavy", my 9800x3D will kick on the fans and start making lot of heat. This is fine when I'm intentionally doing say a transcode, but if I'm just querying syntax it could get pretty annoying. Do you "feel" it? I know that will be pretty machine dependent.
Lies?
They even list it in the user guide https://remarkable.guide/guide/access/ssh.html along with an "developing software" guide https://remarkable.guide/devel/index.html.
Maybe other tablets are like that too, to be honest I'm too poor to swing the 700-1000$ for what I can cover with an paper note pad (with the bonus of being able to comfortably sit my coffee cup on it, use any pen or pencil, rip pages out, drop it, forget it somewhere, etc etc) to buy one but at least it seems like a product I would support.
Yes, I'm using RADV :)
Proceeds to literally loop around 6 times.
> users are still served only by the proprietary driver [...] An open source Vulkan driver on Windows opens up a number of possibilities: a shared codebase across platforms, easier debugging and experimentation, faster turnaround on fixes, and a path for the community (e.g., game developers) to report problems or contribute improvements that benefit everyone regardless of operating system.
To me, the argument against a proprietary driver seems extremely weak if you're running Windows anyway, but I guess they see it more that if more game devs can run the RADV driver, they can get wider testing (or a simpler story for devs to test at least) and backdoor improvements into the Linux side?
I guess I dont understand the "a shared codebase across platforms, easier debugging and experimentation," comment. Shared RADV codebase? Or shared game engine code, at least the specific parts of the engine that target Vulkan x Radeon (how big is that really?). Similarly I guess "debugging" here is tracking down odd ball RADV bugs where you could then run it in windows to see if its a linux thing or a RADV thing?
He searched his pockets. No more coins; nothing.
“I’ll pay you tomorrow,” he told the door.
Again he tried the knob. Again it remained locked tight.
“What I pay you,” he informed it, “is in the nature of a gratuity; I don’t have to pay you.”
“I think otherwise,” the door said. “Look in the purchase contract you signed when you bought this conapt.”
In his desk drawer he found the contract; since signing it he had found it necessary to refer to the document many times. Sure enough; payment to his door for opening and shutting constituted a mandatory fee. Not a tip.
“You discover I’m right,” the door said. It sounded smug.
From the drawer beside the sink Joe Chip got a stainless steel knife; with it he began systematically to unscrew the bolt assembly of his apt’s money-gulping door.
“I’ll sue you,” the door said as the first screw fell out.
Joe Chip said, “I’ve never been sued by a door. But I guess I can live through it.”
- Ubik
The nature of them being basically forced to inherit the module name means its pretty obvious that `MyAppWeb.Admin.Components.EmailValidator` is in the `MyAppWeb.Admin.Components` module. I also think it probably strongly depends on how much JS you actually have, most of my liveview apps have it "here and there" to enhance something or minor DOM fiddling, if you are booting react components everywhere and have some other pile of existing js code, its probably not so good.
I dont think its inherently any more insecure than another method, you just have to recognize that clients can create malicious requests to `handle_event(my_event, params, socket)`, just like you might to `my_action(params, conn)`. It's also pretty painless, normal, to just crash on bad data, it will only effect that one naughty lv process.
You could also send "control" signals to the phoenix liveview process via the same socket but I dont think that actually as much surface outside of heartbeats and closing the socket.
Commercials, 45 – 60 mins
"Standing Around" & Stoppages, 65 – 75 mins
The Halftime Show, 25 – 30 mins
Replays & Commentary, 15 – 20 mins
Actual Football Action - The ball is live and in play, 11 – 16 mins
Actual Football Action - The ball is live and in play, 80 mins
"Time-Off" Stoppages, 30 – 40 mins
Commercials, ~15 mins
Scheduled Breaks, 32 mins
Also this says nothing of on-ground and around-ground ads which I always found depressing, which I guess must exist in all sports.
Can you expand on what you mean by stale? I don't get how an artefact-producer can get "stale" besides literally out-of-data information which I dont think you mean because you mention fable.
https://windupstories.com/books/pump-six-and-other-stories/
Also I guess Silo / WOOL by Hugh Howey is perhaps closer to what you wrote literally but probably not quite the vibe maybe.
I know its all volunteer work and extremely not fun at the moment, but it feels weird to not even have some sticky-no-reply on the AUR sub forum with a list of compromised packages. You have to instead try and scrape them up from around threads like here or reddit.
> information above is fucked. For example
I imagine at some point writing "fucking" was rebuffed, or maybe you can write "fucked" but not "fucking", or there was some time between those paragraphs.
> https://www.amazon.com.au/stores/author/B001H6Q2TE/about
> This is awkward and a little creepy. They tell me I have to do it for promotional purposes, but I've already got a blog. I've already got a website. Being told that setting up an author page on fcuking Amazon is essential to success? A company that treats us all like such goddamn children it doesn't even allow us to correctly spell an epithet with a venerable history going back 900 years or more? That just sucks the one-eyed purple trouser eel.
>
> Also the bio information above is fucked. For example, my work has only appeared in 36 BoY collections, not 350; the noms and awards info is out of date too, but apparently it was all written by some publishing house and I can't change it from this interface.
>
> Still, here I am. But if you're really all that interested, go check out my actual blog/website. Google is not your friend (any more than Amazon is), but at least it'll point you in the right direction.
>
> I'm the one on the left, by the way.
Hell yeah brother.
Wonder when it was written and what it would say if written today.