I’m probably completely insane and deranged, but I actually like assembly. With decent reverse engineering software like Ghidra, it’s not terribly difficult to understand the intent and operation of isolated functions.
Mnemonics for the amd64 AVX extensions can go the fuck right off a bridge, though. VCVTTPS2UQQ might as well be my hands rolling across a keyboard, not a truncated conversation from packed single precision floats into packed unsigned quadword integers.
If you’re using a decent development system, you’ll have an executable called diff installed already :)
Video game grading is a massive scam. Karl Jobst did a series of videos on it, and it’s basically price rigging and speculation investments for profit.
I’m surprised nobody has mentioned porn yet. Like it or not, it does drive growth.
It’s not the Chromium team. Google could have added JPEG XL to Android, but that’s been stalled for nearly two years with zero explanation as for why.
The whole thing smells of managerial interference somewhere.
Interestingly, the reference implementation libjxl appears to be a Google project. They’re all over the patents file and CLA.
If Mozilla isn’t merely being hopeful about having the same team create a Rust implementation, that might actually mean there’s internal interest within Google. Assuming they pull it off, the bullshit reason for refusing to add JPEG XL to Chromium might finally stop being a blocker.
Google created the original reference implementation, libjxl. It’s not stupid that they would prefer a Rust rewrite be created by the same team.
Time to have your own local library integrated with an *arr or two?
I’m not sure which two trolls decided to downvote your comment saying “fair points,” but here’s an upvote for being a good sport about listening to me explain why your preferred implementation of blocking might not be more effective than what we have now.
A privately-stored salt would fix that :)
Chaotic good admins are my favorite kind of admins. 👍
The easiest way to to take a look through a kbin/mbin instance, which exposes the vote information through the interface for everyone. The harder but equally valid way is to run your own Lemmy instance. Other instances will tell yours exactly who voted for what, and as an admin, you even get an option on Lemmy’s web interface to see it.
I’d be great if the block would make them unable to downvote you and your posts as well. And it’d be nice if it wouldn’t even let them reply to your posts.
I’m not entirely sure that’s going to work out the way people think it will.
Suppose I’m some jackass that gets off on harassing you: if blocks prevented me from interacting with your content, and you blocked me, I would have confirmation that I’ve successfully gotten under your skin. I can then just make another account and continue what I’m doing.
If blocks don’t notify or provide indication to the blocked party, they would either escalate their behavior (while you are blissfully unaware) and get banned by a moderator, or give up and move on to someone else.
There’s also considering how that’s going to work with moderators and admins: do they get to bypass the block and continue to comment and interact with you against your wishes? Does it hide your posts from them if they’re blocked? It’s a lot harder to design this type of blocking on a community-centric platform than it is to do for a microblogging platform like Twitter or Tumblr.
Because muting doesn’t stop the poison the spread, just my personal ability to not see it.
That’s what mods and admins are supposed to do. It’s not the users’ responsibility to moderate the behavior of others, and it’s a lot less stressful than trying to stop toxicity when you only have words in your moderator toolbox.
I’d go for the block and move on approach as well. Nobody is entitled to an explanation.
Exactly. If private votes were intended, Lemmy servers would have had voting privacy setting where the vote is federated as @privacy-vote-{sha256sum userid & postid}@instance.foo instead of the actual voter’s username.
Yeah. Just look from a kbin instance, or if you host your own instance, you can run a Postgres query to find them there’s a dropdown in the web interface to see who voted on a post/comment.
They’re already public if you look via kbin or run your own instance.
If that’s not photoshopped, props to him. Wild pigeons don’t like being picked up, and that would be a pretty difficult photo to pull off.
I wouldn’t call it surprising or confusing, unfortunately.
That assembly is for a DOS application. It would be more verbose for a modern Linux or Win32 application and probably require a linker script.
Technically, not quite. Python is interpreted, so it’s more like “call the print function with this string parameter” gets fed into another program, which calls it’s own functions to make it happen.