• 11 Posts
  • 114 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle
  • There is way too much sensationalism around this law. All this law calls for is an OS-level “Are you over 18?” button, the kind that’s been all over the internet for decades. See the Ubuntu mailing list discussion for a possible technical approach. There does not appear to be any requirement for age verification beyond that of the system administrator, and reporting is by a total of four age brackets, so even the privacy impact is limited.

    The benefit of something like this is that age can be enforced by the system administrator rather than the user, so parents can set their kids’ computers with an accurate age bracket. Meanwhile, all of us with just a single user can set the highest age brackets and move on with our lives. Now, as the CEO of System76 says, kids will find ways around it, and we shouldn’t discourage kids from controlling their own computers, but he says “If there is any solace in these two laws, it’s that they don’t have any real restrictions”.

    But that same article notes that New York has a proposed bill S8102A that is much more draconian. California’s law is a minor nuisance, while New York’s bill sounds like an outright danger. Please focus on a real threat, especially considering it’s much easier to change laws while they’re still only bills.


  • randytoLinux@lemmy.mlAsteroidOS 2.0 Released
    link
    fedilink
    arrow-up
    2
    ·
    22 days ago

    AsteroidOS mostly supports watches that come stock with Wear OS, which is a modified version of Android, which, guess what, runs a Linux kernel. These watches are on the more powerful end of the computing spectrum. As you say, there are a lot of smart watches that use pretty lean MCUs, but those aren’t running AsteroidOS or Wear OS, as noted in this FAQ entry.






  • randytoLinux@lemmy.mlWhat do you think of loss32?
    link
    fedilink
    arrow-up
    13
    ·
    2 months ago

    Follow the link and go down to the third point:

    Isn’t this just ReactOS?

    ReactOS tries to reimplement the Windows NT kernel, and that has always been its Achilles heel, holding it back from a hardware compatibility and stability standpoint. The loss32 concept is to achieve a similar-feeling end result to ReactOS, but built on a more usable foundation, using components known to work well (the Linux kernel, WINE, everything that glues those together, and a sprinkling of ReactOS userland niceties). As a bonus, the OS would still technically be a Linux distro, so it would be possible to run Linux software when necessary, something ReactOS can’t do.




  • My knee-jerk response is to be indignant about a cop being let off lightly, but the article does describe him as remorseful of his behaviour and taking steps to deal with his own issues. So he sounds like someone who is unlikely to reoffend, and therefore should not be punished harshly. In our justice system, I believe a non-cop would have been sentenced similarly.

    But I don’t like the idea of him continuing to work as a cop, at least beyond in-office work, as the police should be held to a high standard. He’s going to work on his own issues, but such work isn’t always quick or smooth. Being in the field dealing with challenging people raises the risk that he runs into another situation where he loses control. I don’t know what the policies are of the Guelph police, but I hope they keep a high standard here.








  • randytoActual Discussion(WEEKLY) Voting Systems
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 months ago

    I’d like to get into an even broader discussion. I’ve noticed discussions about voting systems tend to assume a single winner, because most of our political systems are set up to require a single winner. Most commonly, this is the people in an area choosing a single representative. But if we’re flexible with our political systems, we can expand the possibility space in all sorts of interesting ways.

    A simple example: the city of Guelph elects two councillors per ward, with each voter choosing two of the candidates and the winners being the top two (see 2022 election results for details). This is almost like a blend of plurality (aka first-past-the-post) and approval voting systems. Anecdotally, I feel that this creates a better political climate in Guelph, because candidates can’t be at each others’ throats when they will end up sharing voters and eventually sharing power.

    Some other examples:

    • BC-STV would have created multi-member ridings with an instant-runoff-style voting system (proposed but rejected for BC provincial elections).
    • MMP (Mixed-Member Proportional) creates two categories of representative to create proportionality by party (used in a number of countries, was proposed but rejected for Ontario provincial elections).
    • Or completely rewrite the concept of representatives and do direct representation and have an unlimited number of representatives independent of ridings with varying voting power in the house (and then we can argue about voting systems for legislatures).


  • This is exactly how I use Syncthing, and as the author says, it sure would be nice if more things were just files. Really, most things are stored locally as files, but not always in a way that plays nice with syncing. Like, I can sync my Firefox profile between machines (it’s all in one folder), but I found it prone to conflicts, with little to resolve those conflicts.

    In a similar vein, local-first apps built with Conflict-free replicated data types (CRDTs) can be another way to avoid server dependency. I haven’t seen any significant apps built this way yet (just occasional blog posts about it). I imagine the CRDT approach would work better for individual apps, since conflict resolution can be written in a way that works best for a given app, but I also imagine that such apps would not play nicely with a generic sync solution like Syncthing.