Mama told me not to come.

She said, that ain’t the way to have fun.

  • 2 Posts
  • 855 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle
  • There are a few decent options, all with some caveats:

    • Seafile - wicked fast, but uses a funky disk format, so you need either a FUSE layer or the web UI/API to access anything
    • OCIS/OpenCloud - default install uses a funky file format, but you can change this to POSIX if you want (experimental on OCIS, might be default now on OpenCloud?)
    • others - probably work fine, but they get less blog attention

    I’m playing with OCIS and I like it so far. There was some funkiness when I had things misconfigured, but now that it’s working, I like it.




  • It usually comes down to privacy and independence from big tech, but there are a ton of other reasons you might want to do it. Here are some more:

    • preservation - no longer have to care if Google kills another service
    • cost - over time, Jellyfin could be cheaper than a Netflix sub
    • speed - copying data on your network is faster than to the internet
    • hobby - DIY is fun for a lot of people

    For me, it’s a mix of several of reasons.





  • Are you really going to take it into the woods with just two seats, mediocre suspension (likely, given the limited payload and towing), and limited range? Just get a Polaris side-by-side or something, they’re built for that.

    I get it, a cheap truck is appealing, but at this price target, it’s going to make a lot of compromises. It should do fine in plowed roads (might need sandbags in the back though), so it’ll probably be fine for around town use, which seems to be its target.


  • Let’s look at a scenario where there’s an exploit that requires a change to an API. With JavaScript, the browser vendor can ship a fix to the API, and web devs update their code. With a plugin, the browser vendor ships a patch, then the plugin vendor needs to ship a patch, and then web devs need to update their code. Some plugin vendors will be slower than others, so the whole thing will see massive delays and end users are more likely to stick to insecure browser versions.

    Plugin vendors are going to demand the same API surface as current web standards and perhaps more, so you’re not saving anything by using plugins, and you’re dramatically increasing the complexity of rolling out a fix.

    I think the current web is a decent compromise. If you want your logic in something other than JavaScript, you have WebAssembly, but you don’t get access to nearly as many APIs and need to go through JavaScript. You can build your own abstraction in JavaScript however to hide that complexity from your users. The browser vendor retains the ability to fix things quickly, and devs get flexibility.











  • The modularization was good.

    The modularization was a security nightmare. These plugins needed elevated privileges, a d they all needed to handle security themselves, and as I hope you are aware, Flash was atrocious with security.

    Having a single “plugin” system means you only need to keep that one system secure. That’s hard enough as it is, but it’s at least tractible. And modern browsers have done a pretty good job securing the javascript sandbox.

    That was better back then, people had realistic expectations

    I don’t think that’s true. I think there just weren’t as many attacks because there weren’t as many internet users. Yet I also remember getting viruses all the time (at least once/year) because of some vulnerability or another, and that’s with being careful.

    You should take off those rose colored glasses.

    I appreciate that people not knowing as much about security is problematic, but that’s because the average person is far more secure than they were even 10 years ago. Getting a virus is pretty rare these days, Microsoft has really stepped up their game with Wndows and browsers have as well. I haven’t worried about getting a virus for many years now, and that’s thanks to the proactive security work in sandboxing and whatnot that limits exploits.

    A lot of the scams and whatnot these days either attack outdated systems (esp. insecure routers running default creds) or merely use social engineering because you can’t simply use an off-the-shelf flash exploit or something to get privilege escalation to install your malware. Attacks certainly exist, but they’re far less common than they were 10-20 years ago as people started being online constantly.

    those plugins being disabled by default

    Yes, I am annoyed at JavaScript being enabled constantly and not having fine-grained control over specific permissions (mostly just location, mic, camera, and storage).

    Unfortunately, that ship has sailed. But I still very much prefer the modern “everything uses JavaScript” to the old insecure Flash and Java applets.