• 0 Posts
  • 30 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle

  • arc@lemm.eetoTechnology@lemmy.worldI use Zip Bombs to Protect my Server
    link
    fedilink
    English
    arrow-up
    27
    arrow-down
    1
    ·
    1 month ago

    Probably only works for dumb bots and I’m guessing the big ones are resilient to this sort of thing.

    Judging from recent stories the big threat is bots scraping for AIs and I wonder if there is a way to poison content so any AI ingesting it becomes dumber. e.g. text which is nonsensical or filled with counter information, trap phrases that reveal any AIs that ingested it, garbage pictures that purport to show something they don’t etc.




  • arc@lemm.eetoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    5
    ·
    2 months ago

    Depends what you mean by bloat. It has a very large repo, but it compiles into little commands with least privilege execution. A lot of those commands are specifically there so someone doesn’t have to pull in other repos with a larger attack surface. e.g. there is a time sync daemon to replace having to pull in ntp which is a lot more complex and fraught and the one thing most desktops need of NTP which is to set the clock.


  • arc@lemm.eetoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    2 months ago

    Why do you still exist? I try understanding what the purpose of your reply could be? Screenrecords do not work. For plenty of people. Google it. Yet you feel entitled to share you smalldick energy wisdom of “proper way”. That is exactly the vibe of the shit ppl. You do not help Wayland or x11 or anything, you just fap into your own mouth because nobody can ever love you like that. Go get help.

    Wow, someone needs to grow up. You laid into Wayland when screen recording doesn’t even go through Wayland. The app asks the WM to screen record via DBus. A more constructive response would have been “thanks I didn’t know that”, or perhaps “oh it’s a driver issue”, or “it’s an issue with that WM/ffmpeg/pipewire or whatever”, or anything else likely to be the underlying cause. But it’s not Wayland. Have you got that? Not Wayland. There is no need to be sore and immature about it.



  • arc@lemm.eetoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    2 months ago

    Screen records do work providing the app asks for a screen cast in the proper way (which BTW is not via Wayland but through a message to a DBus service). The service and the desktop then ask permission from the user if necessary. X11 didn’t give a damn about protecting the contents of your screen and any app whether it was beneficial or malicious could do it with impunity. So you should see this as a major security improvement - you can screen record but only if permission is granted.


  • arc@lemm.eetoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    6
    ·
    2 months ago

    Yes it’s been stable for some time with a couple of caveats - you need a decent graphics driver and not be using apps with edge cases.

    Here is a simple example of an edge case and it’s not hard to find people blaming Wayland even though with some thought this was a security issue - apps like Zoom, Discord, MS Teams want to do screen sharing which is easy in X11 because it has non existent security - just steal the screen bitmap. That’s a problem.

    Wayland (the protocol) provides no means for one app to grab the screen, or other apps. This is by design for security. Instead the app must be a good citizen and send a “i want to screen cast” message to the xdg-desktop-portal (a service provider implemented by GNOME, KDE etc.), the desktop asks for user consent and then the app gets a video stream. So it’s a lot more secure but it requires the app and the WM do things properly.

    Desktops and apps have matured and these issues are thankfully going away. I think the biggest hurdle left is proper graphics drivers, especially the problem of getting NVidia drivers working.








  • arc@lemm.eetoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    31
    ·
    3 months ago

    I do not believe for a second that communications within the Whitehouse are inadequate, or if they were, could not be solved in a secure manner. Slapping a Starlink in a few places sounds like an invitation to backdoor all communications. Not only that, it is an invitation to sidestep obligations to preserve government records.


  • I followed Abramson from 2016 for 3+ years and I was disillusioned because as time went on, his narrative didn’t line up with reality. Yes Trump was and is a horrible piece of shit and much came out to confirm how much a piece of shit he was, e.g. Muller report, rape, fraud trials. But nothing like Abramson was saying. I believe that is because he was treating every rumor as fact and then expounding / extrapolating on it to heap another rumor (as fact) on top. Nobody should be doing this let alone a scholar who should know better - veracity matters.

    And to repeat - I truly hope Musk is having a miserable shitty life. I really hope he goes nuts and checks into a funny farm or uses razor blades to test if he is living in a simulation as he has wondered occasionally. I just don’t trust his “biographer” when he claims anything given his past record on such things.




  • arc@lemm.eetoTechnology@lemmy.world*deleted by creator*
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    3 months ago

    Tesla doesn’t have that excuse. The original Roadster, Model S and Model X all had fairly conventional controls. They deliberately undermined the safety of their vehicles over time by aggressively removing physical controls in the model 3 and Y and revamped S. It probably saved them a few bucks, but at the cost increased risk to human life. If they get penalized in safety tests for their penny pinching then so be it.