• 1 Post
  • 143 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle
  • Yea, I wasnt entirely clear, I brought up Manifest v3 as a “this is already complicated, and a browser engine is even more complicated” example

    No Chromium fork maintains Mv2 anyways even though it is easier, and yes some do have their own builtin AdBlock and are able to function well that way. But I do not consider that ideal, one would be entirely dependent on their AdBlock implementation where as if a fork maintains Mv2 then you would be able to just change your extension if you don’t like something about it


  • I work in IT and have implemented quite a few MDM systems. For Android, a work profile will be entirely isolated personal data wise. IT can’t see anything beyond the work walls, however, there are a few shared things.

    If work enforces a tougher screen lock setting, it’ll take precedence over your regular lock screen setting. You might also have a few other things change while it’s active, like display time out (if work has a shorter setting).

    We can also see certain shared info like device serial number, IMEI number, OS version, security update version etc. Depending on the configuration, GPS/location info can be obtained as well (via an force-installed policy app for example)

    You can pause the profile at anytime which suspends ALL work profile app activity (So if there was an app they install that they could get GPS info from, that app would no longer be functional until unpaused again (no it can’t “run in the background” and collect info on the background either, it’s wholly suspended)) and the pause feature can be set on a schedule so if you have a 9-5 you can set it to that and avoid the whole “always available” problem.


  • None of the forks are immune to Mozilla enshittifing the engine itself.

    Browser engines are complicated beasts, the w3c specifications are thousands of pages and a proper engine would have to implement it all.

    It’s the reason why not a single chromium fork is able to maintain manifest v2 in defiance of Google, because they would have to then maintain the engine themselves for the most part



  • And re: phones—you can see that’s a camera. Also, they have a bright LED that indicates recording. These glasses do not.

    Umm when was the last time you…you know what, let’s do an experiment, start recording a video on your phone, flip it over and look at the back and tell me where the red recording LED is LOL

    Anyways, the other commenter here cited specific cases and a supreme court ruling which tied recording in a public space as a 1st amendment issue (which I didn’t know either) so now short of a new federal law passed by congress, it ain’t changing. It’s not my opinion, it’s a fact.


  • Lol that has nothing to do with the other, and courts have already set precedent for recording in public spaces and have generally ruled that with current laws there’s no expectation of privacy in public spaces.

    The fact the camera being on someones face is almost assuredly going to be an insignificant factor in any future court case considering the sheer amount of cameras pointing at you as-is from phones (How do you know if someone is just on their phone or recording?) and security cameras and now that businesses are heavily investing in ever more cameras for their AI BS…yea, sorry to say, but nothing is going to change on that front for the foreseeable future.






  • Here’s a comment about it I made a few weeks back in the context of why Jellyfin came to be and why I only ever recommend Plex or Jellyfin

    This is going to go back quite a ways, and much of my knowledge is old at this point so some details might be off.

    ~15 years ago Plex as we know it started out as an OSX fork of the 0G Xbox homebrew software XBMC (Later renamed Kodi (For those who don’t know, XBMC was XBox Media Center and would turn the 0g Xbox into the cheapest Home Theater PC you could get at the time, man those were the days lol))

    Plex was only briefly open source and then was quickly closed when they incorporated a year or so after they had something functional. They never made any promises about not charging or being open source or anything, so that’s why I’m generally fine with Plex

    Sometime around 2012ish Emby came along as THE open source alternative to Plex and things were good. MOST of it was supposed to stay open source as was promised. From the beginning they kept build scripts n such closed source, probably should have caught on them, but heh ya know hindsight and all that.

    Then around 2014/5 they took it all closed source, relicensed it and introduced their paywall including locking away already existing features. This is what pissed me and many others off and this is when and why Jellyfin split off promising to be truly fully open source forever. (There was a ton of drama about it at the time, but it looks like Embys Q&A thing a bit back doesn’t even bother to mention it, imagine that lol)

    I don’t have a problem with subscriptions on open source software myself, but the way they went about it…yea. fuck em


  • I try not to be, but attention does need to be called to it, and I see a lot of handwaving away in regards to Mozilla. People should be demanding more answers from them to at least delay enshittification a little to give more time to the alternatives like Ladybird and Servo to develop and refine for widespread usage

    Which thanks for pointing me towards Servo, I missed that one lol, but I still don’t think it has yet achieved feature parity with Gecko or Chromium


  • The big problem is the browser engine at the heart of all browsers, all the FF or Chromium forks very rarely modify the core. When they do, it’s minor stuff. That’s why AFAIK not a single chromium fork is maintaining manifest v2 in defiance of Google.

    If Mozilla goes full tilt enshittification, all the FF forks will suffer a similar fate, they’ll make changes all over, custom interface, cool little features here and there etc; but they’ll never make major changes to the core and that’s assuming they keep the core open source. If they take the core closed source and the forks can no longer get upstream updates for it they’ll wither and die

    A browser engine is kinda like the Linux kernel, it’s large, complex and takes a lot of time and effort to make and keep it usable. I’ve seen estimates that if we needed to start from scratch on the Linux kernel it’d take 2-4 years just to get something decently usable.

    Browser engines are similar, Ladybird for example, is a new open source browser AND engine from scratch that’s been in development for about 2 years, they’re estimating to have something “generally usable” in 2026