• 1 Post
  • 36 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle





  • Because most oss maintainers are more afraid of their work disappearing due to service shutdowns than they are being profiled by data miners.

    Everyone has seen some example of a tool or resource hosted on a persons private server end up taken down because they couldn’t afford it, the isp or university stopped offering hosting or because they simply couldn’t keep doing it due to death or old age.

    That’s what people who create software are afraid of. The loss of that creation, not the loss of the privacy of people who contribute to it or download it.



  • What matters is that the backups are done at the appropriate intervals and verified to be readable.

    You can figure out what interval is appropriate. Some people have to make sure every picture is saved, some people are fine losing a month of stuff.

    Verifying the backup is valid equally important. You don’t wanna find out it was misconfigured and didn’t get your user directories when you try to restore. Just open one up and look to see every once in a while.

    At least fifteen years ago you could set up windows backups through the control panel > backup or something menu. Now on 10 it’s settings > updates and security > backups.

    You can click add drive from there and designate a usb or something as your backup drive.

    Then set an alarm to make sure you remember to do it at the designated interval.

    With android the easiest thing is to sync it to a computer that gets backed up.

    You can use cloud services instead of a hard drive too, but often simple and easy to understand is the best place to start.

    Do you know why it’s important to have backups before using full disc encryption?









  • It’s interesting that I’m not supposed to infer the Mozilla groups stance on pwas, but also not supposed to believe what Apple has directly stated.

    I mean, the only thing Apple is preventing is the installation of pwas directly to the desktop, notifications and the use of persistent cache past a week, right?

    You can still do a link on the desktop to an online pwa just like a link to some website.

    And that’s only if the pwa is t distributed through their app store. Afaik if the developer goes through that channel of distribution they get to store data persistently (this is the running offline everyone’s up in arms about), use notifications, etc.

    Personally I hate pwas and hope they go away, but even if you like them, surely these small constraints which are in line with other platforms won’t be a problem.

    I don’t see any reason not to believe what apple says about needing to be safe with other browser engines since they gotta allow them in the eu. I mean, let’s give a real uncharitable look at ios security: maybe the vaunted secure platform is filled with undocumented flaws covered up by heavy integration between the rendering engine and the os. Maybe ios + safari sucks and they need to cover up as much of it as possible so the new browser engines don’t expose users to security vulnerabilities.

    Am I missing something here?


  • It’s weird then that Firefox on the desktop doesn’t support them.

    Just think on why that might be. Why both Mozilla and Apple would be opposed to something that Google is in favor of.

    I mean, if pwas are no big deal then surely a platform other than chromium and android combined would be gladly embracing this new technology.

    I’m really not trying to argue from a position of aged authority, but pwas are bad. I know because every time some way to make a webpage just like a program and also escape the browser has come up it’s been bad.

    And when you look at it as a power struggle between big corporations pwas are being pushed by Google, the bad one.

    I know that’s not convincing so let me ask you this: what would be? What would convince you that despite Apple being your enemy, pwas are bad?


  • I dug up my old development backups from that time and I had it backwards, the advice was to read user agent strings and link directly to the version of the browser your pwa was designed for if you saw they weren’t running the “right” one and were worried about it breaking.

    So I was mistaken but the reality was weirdly still bad.

    I don’t know if that’s still commonplace. Right now it seems like a lot of pwas target chrome because it’s the most popular browser.


  • If you don’t think users are part of the security equation I don’t know what to tell you.

    I’ll try to dig up a source for the second thing tomorrow morning when I’m in front of a computer. Four years or so when I dipped my toes into what was then a new technology to see what it’s all about that was the example in the site I looked at to learn how it worked and how to translate an interactive website into an offline pwa.

    As you can imagine I found that repulsive and dropped it like a bad habit. Seeing a multitude of pwas on every android device all doing out of band alerts and notifications just made me more opposed to them in general.

    Looking into the state of pwas today it really seems like the best support is through chromium/blink. Do you think once apple gets ahold of allowing other rendering engines they’ll allow them back on or what?


  • That sounds a lot like the old windows 95 and dos days where the expectation was that the os would never stand in the way of even the most obviously malicious software.

    I don’t want to go back to those days and even the most freedom loving environments have dropped support for operations like direct memory mapped io and more pertinent to the topic of our discussion, web technologies like flash and inline pdf rendering.

    I get that it feels like someone is trying to take something away from you, but you gotta recognize that the thing they’re taking away is basically a gun pointed at your own foot.

    I run a lot of systems that allow you to screw up, but I don’t have any complaints about one that doesn’t, especially when it’s on mobile: a platform with a much higher risk, reward for compromise, higher user trust and higher level of obfuscation regarding what’s happening under the hood.