Programmer and sysadmin (DevOps?), wannabe polymath in tech, science and the mind. Neurodivergent, disabled, burned out, and close to throwing in the towel, but still liking ponies 🦄 and sometimes willing to discuss stuff.

  • 0 Posts
  • 25 Comments
Joined 3 years ago
cake
Cake day: June 26th, 2023

help-circle


  • AB 1043 passed the California Assembly 76–0 and the Senate 38–0. Not a single legislator voted against it.

    1798.503. (a) A person that violates this title shall be subject to an injunction and liable for a civil penalty of not more than two thousand five hundred dollars ($2,500) per affected child for each negligent violation or not more than seven thousand five hundred dollars ($7,500) per affected child for each intentional violation

    This device does not collect, store, or transmit the age of its user. This is intentional.

    Is there any reason to believe they won’t want to make an example out of intentional violators?


  • Yes, I get that they may want verification with government ID… but unless they do it at a firmware level, anything above a FOSS Linux kernel on my own unlocked hardware, is fully under my control.

    So far, it sounds to me like “age verif theatre” as applied to single user “jailbroken” systems. If they added this on a locked down Android system, as a requirement for network access (note: this is an actual proposal being floated around) then that would be of some concern… but systemd? 🤨


  • QUESTION: if I run my own system with local accounts, full root access, and no remote accounts… why should I care about whether systemd “MAY BE ABLE” to store someone’s date of birth?

    Sounds to me like, for all I care, they could add fields for ethnicity, religion, d size, political orientation, colonic maps, or whatever else they want.

    If it’s to build systems shared with underage family members, schools, or other public system… I personally DGAF.









  • TLDR: It’s a mess.

    Back in the day, I started migrating notepad stuff to Markdown on a Wiki. Then on a MediaWiki. Then DokuWiki. Then ZimWiki. Then Joplin. Then GitHub Pages and a self-hosted Jeckyll.

    Each, single, one, of, them, uses a slightly different flavor of Markdown. At this point, I have stuff spread over ALL OF THEM, much of it rotting away in “backups to migrate later”. 😮‍💨
    I’ve been considering “vibe coding” some converters…

    As for syncing… the Markdown part is easy: git.
    Working with a Markdown editor to update GH Pages, was a good experience.
    Having ZimWiki auto-sync to git, was good, but didn’t find a decent compatible editor for Android.
    I switched to Joplin lured by the built-in auto-sync options, but kind of regret it now, when it has a folder with thousands of files in it.

    Obsidian is not OSS itself, but has an OSS plugin to sync to git.
    I’ve read that using Logseq alongside Obsidian should be possible… and was planning to test that setup, keeping Obsidian in charge of sync. Possibly with GitHub/Jeckyll, git-lfs for images and attachments.


    PS: assuming one could have working back-and-forth converters for the different Markdown flavors, and everything stored in git, then one could theoretically use git hooks to convert to/from whatever local version used by a particular editor.



  • I was going to say that AI has a lot of implications in the online world that Mozilla was supposed to promote… but maybe you’re right, the AI genie is out of the bottle and there is little left to do about it. Its impact will be whatever it will be, no matter what people want to say about it.

    Not sure which “old Mozilla” you want, the 1998 one? the 2005 one? the 2015 one? It has changed a lot indeed, but kind of has been Google’s anti-anti-thrust shield for 20+ years.