• 0 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle





  • o wow didn’t know this. such horrible design decision! So if I understood correctly ALL the apps that want to screenshot need to write independent code for each desktop environment??? I was just mostly ignoring Wayland until becoming mature, but now I actively dislike it with passion.

    So, if this is true and I understand correctly, it means that if I chose to use Xfce (as I do), I’ll have to hope really hard that zoom, skype, slack, discord… decide to provide support for not only linux,… but XFCE or give up and abandon XFCE? yeah f*** Wayland, they really didn’t think about the open source community when designing their solution. I don’t wat to even think of people that use other smaller desktop managers…

    I mean, screen sharing is basic functionality these days, in the interview for my current job I needed to use… I think it was teams. Is not even something you can chose, is bad enough to be exclusive linux user as it is, always wondering if in such cases something will not work.

    Honestly, long live Xorg. if deprecated and I have to switch to gnome/kde or lose functionality I might as well switch to windows after 20 something years of not using it.


  • I use xfce, I have nvidia card, I sometimes capture a video of my screen and I regularly share my screen. Didn’t even try.

    I’ll use Xorg until its deprecated or Wayland offers me some benefit other than “is new and shiny and the internet told me is cool”

    I also became a bit sceptical about it with so many open source projects and basic functionality not supporting it yet after sooo many years of “Wayland is here”… so yeah, I’ll wait until someone gets xorg from my dead cold hands 😁

    also I don’t get how aggressive people get about what other people have in their desktop, dude let me live my linux life alone 🤷‍♂️


  • I already unsubscribed and start sailing when the account share thing happened, but people are willing to take anything these days… so good for netflix I suppose.

    101 businessman logic: slowly stretch it until numbers go down, and then back down a bit, just to keep trying stretching it further in a later time. Repeat.

    infinite growth guaranteed.

    This is why at this point I don’t trust any subscription type thing, they are all destined to end up in that cycle, which, good for them, I think it’ll have to explode eventually, or not, who cares, I’m already out anyway


  • One thing to think about is the encryption quality of a zip file, which I ignore.

    One danger that I see is that you have the risk of having the passwords on the clear all over the place many times. Not an expert so don’t quote me on this, but password managers are careful avoiding passwords on the clear as much as possible.

    I don’t trust any online service for that, I am using keepass/syncthing for myself, with android as the only client decrypting (as I always have my phone with me). one example of advanced security measures is that while using the app I can’t take screenshots, and I hope/expect that it uses images backed by secure memory to show them to me and is careful with things like RAM and temporary files (didn’t check personally though, although being open source I could)

    Having to be sure that your zip app handles that seems like a hustle honestly. On top of having random passwords without the biases I would add for each separate site.




  • you seem to know what you are talking about and I looked into this very long ago, maybe you can help me understand.

    From what I can understand reading most of the article this forces browsers to accept the certificates, but it doesn’t force the websites to use them, right?

    So what is stopping Firefox from showing a warning (like the lock icon being orange, but it could also be a more intrusive message) stating that the certificate was issued by a country and/or doesn’t fullfil modern security standards in case one of these CAs is used?

    On top of that, the CA doesn’t really encrypt the private key of the domain, it just adds a signature stating that the message with the salt and the public key are legit, right? everyone seems to think the government itself will be able to passively see the traffic, but if I remember correctly they would have to gateway the whole transaction (I’m guessing the browser will also have a cache of keys and this could become a bit tricky to do in a global way)

    But of course we all know how technologically illiterate governments are (there could be one good, but there will be some “less good” for sure). So yeah, it does sound like a horrible idea to begin with. Because if a CA starts being insecure nowadays browsers can just remove them and go with their life, but if there is a law forcing browsers wouldn’t be able to.

    I’m just curious about the specifics in case I’m outdated on what I remember.


  • making sure a small part is very secure vs having to verify every domain I visit? yeah, let me keep using the current system… are you aware of the amount of domains you connect to every day?

    Also, I might be wrong, but if I remember correctly browsers/OS-es tend to come with a list of trusted certificate keys already, which makes adding compromised keys to that list not as easy as you suggest. (I don’t even know if that happens or if they just update as part of security updates of OS/browsers)