• 2 Posts
  • 1.15K Comments
Joined 2 years ago
cake
Cake day: July 29th, 2023

help-circle

  • mlg@lemmy.worldtoLemmy Shitpost@lemmy.worldLibraries are cool
    link
    fedilink
    English
    arrow-up
    27
    arrow-down
    2
    ·
    2 days ago

    Unless the library is tracking book reader stats or you actually check out the book, maybe remember how the classification system works like they were supposed to teach you in school?

    Half the time I’m literally standing in front of the shelf perusing the book, it would be dumb to throw it in the book return unless I don’t know or can’t find the exact position where it came from.



  • This one is funny because it 100% still exists somewhere, but I haven’t had the chance to verify it again.

    Okay so basically its a data recorder box (ex: brainbox) that connects to a bunch of industrial sensors and sends the data over the network with your preferred method.

    Builtin firmware gives you an HTTP webui to login and configure the device, with a user # and password.

    I think the user itself had a builtin default admin which was #0, which everyone uses since there wasn’t really much use for other users.

    Anyway, I was looking at the small JS code for the webui and noticed it had an MD5 hashing code that was very detailed with comments. It carefully laid out each operation, and explained each step to generate a hash, and then even why hashes should be used for passwords.

    Here’s the kicker: It was all client side JS, so the login page would take your password, hash it, and then send the hash over plaintext HTTP POST to the server, where it would be authenticated.

    Meaning you could just mitm the connection to grab the hash, and then login with the hash.

    I sat there for like 10 minutes looking at the request over and over again. Like someone was smart enough to think “hey let’s use password hashing to keep this secure” and then proceeded to use it in the compleltly wrong way. And not even part of like a challenge/handshake where the server gives you a token to hash with. Just straight up MD5(password).

    It was so funny because there were like a hundred of these on a network, so getting a valid hash was laughably easy.

    I never got to check if this was fixed in a newer firmware version.


  • Lots of games that ship with kernel level anticheat have an android port that doesn’t have that feature because android (also linux) similarly doesn’t hand out root access, let alone kernel access to anything in userland.

    Huge example being Fortnite.

    Already ignoring the fact that kernel level anticheats have well known bypasses, cheaters can also just use the Android version to make cheating easier if that was really an obstacle.

    Anyone peddling kernel anticheat as a requirement is just using it to cut costs in running moderation staff. Epic Games specifically is just being a dick to linux because they know they have zero leverage in that market, and don’t want to give Steam more traffic.

    All Valve really has to do is sell enough units to tip the percent of linux users that these publishers would not want to miss out on. That’s how so many updated and expanded with the steam deck. Currently the estimate is about 4 million monthly active users on a linux platform. I think if they can reach 10 million (I think 6-7%), it would be enough to incentivize the change.

    I never would have thought Microsoft would allow Halo Infinite or MCC on linux 5 years ago, but they actually changed their minds because they knew people wanted to play on the steam deck. I would even take a guess that the new CoD stuff will shortly follow since MSFT is taking a more open platform approach anyway.

    EDIT:




  • Even though LTT said valve gave a cold stare at a $500 price tag, the BOM estimate is sitting around $420 (compared to $300 for the deck).

    If they follow the same path as the steam deck, they could still comfortably sell the base model at $600 or $550 if they want to get aggressive with consoles.

    Valve basically broke even with the base model steam deck, so I’m assuming the remaining $100 per unit cost is all the external stuff like production shipping etc. They make profit on the higher level models by charging more for storage and OLED.

    Valve’s plan was never to compete with consoles, but they’re sitting on a golden opportunity here with Xbox flailing in the water and being able to price match without loss. Their major blocker is the anti cheat holdouts though, and I don’t think they’ll be willing to change unless steam machine itself becomes very popular, which forms an annoying loop.

    I think they’re probably having some great arguments behind the scenes on what point exactly they should settle on based off of the public response everyone is giving from this statement lol.



  • VLC sucks ass when you want to do any type of live transcoding or remuxing without setting up a video stream. Especially with multichannel audio:

    This has been an issue ever since feature added, the maximum bitrate you can set is 512 kb/s on every codec, despite codecs that support more.

    The bug thread for this was basically “stop complaining about our shit UI and use the CLI”

    Much prefer Kodi for this purpose, and an ffmpeg based player for lightweight stuff.





  • Its still lagging is its MRs, like HDR coming in just less than a year ago.

    Valve’s complaint was that even after getting approval from at least 3 DE projects, protocols were not getting merged due to hypothetical discussions and implementation baggage.

    I imagine it all started with them making their gamescope compositor a few years ago and realizing a bunch of stuff was still missing.





  • proper HDR

    Is completly up to each compositor to implement properly. Its still experimental in KDE because afaik theres no proper SDR + HDR tone mapping for mixed apps on the display, like a desktop.

    Valve made their own compositor and cheats the problem by ensuring their client and overlay supports HDR colors + only having to handle the HDR from game output.

    full VRR support

    Not if you have an Nvidia GPU before 2017, and again already a thing in X11.

    no screen tearing and reduced latency

    Again, VRR and wayland’s ingenious solution to this was triple buffering, which is a pure software solution that adds latency making it unsuitable in several cases like this: https://github.com/hyprwm/Hyprland/issues/3373

    The clipboard also works fine

    Welcome to Xwayland clipboard hell: https://github.com/hyprwm/Hyprland/issues/6132

    Its not that Wayland can’t easily fix any of these issues or that the other major improvements you mentioned are not worth it, its that it took Wayland like 13 years to do so.

    Most of this should have been sorted out in the first couple years of development. People were already making fun of Wayland back in the day for pretending to be “decoupled from the graphics hardware” and then deciding on the aforementioned triple buffer.

    Wayland didn’t even merge in HDR support until 9 months ago: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14#note_2777587


  • Fedora (with KDE Plasma) or OpenSUSE tumbleweed (with KDE Plasma)

    Mint is good but its kernel is usually slightly out of date and it still has upstream Ubuntu issues.

    Other Ubuntu downstreams are subpar imo.

    Plus Fedora & OpenSUSE ships with SELinux if you want MAC security support.

    The only downside for Fedora is you have to enable 3rd party software after install and run a couple of commands to swap to full ffmpeg and Nvidia drivers if you have Nvidia hardware. I think OpenSUSE might ship with these enabled but I forgot.


  • mlg@lemmy.worldtoTechnology@lemmy.worldScrew it, I’m installing Linux
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    19
    ·
    8 days ago

    Wayland is responsible for kneecapping linux desktop in so many ways its infuriating, especially since linux basically figured out the golden standard of UX design back in the 2000s with stuff like GNOME 2 and Compiz.

    It’s such an unnecessary burden with progress as slow as ripoff projects like star citizen.

    I hope valve picks up the slack with frog protocols or at least gets PRs merged, because it would be stupid to ship steam machine and then explain to the user that the clipboard doesn’t work yet, even though it used to work perfectly fine in X11.