• 2 Posts
  • 320 Comments
Joined 8 months ago
cake
Cake day: August 31st, 2025

help-circle


  • The sponsor of this bill is Josh Gottheimer. Ballotpedia says the Democratic primary is on June 2, but doesn’t list any challengers. If you’re a local, maybe you know if he has a challenger?

    In any case, do the following if you live there:

    • Add “fire Josh Gottheimer” to your calendar for both June 2 2026, and November 3 2026

    • Send him a letter/email explaining why this issue is important enough for you to vote Republican if it goes through, and maybe include a screenshot of that calendar entry just for fun

    If enough people send a message like that, he’ll hopefully work to kill it.

    If you don’t live in New Jersey, write and send a similar letter/email to your own representative. If you’re a Republican, say you’ll be willing to vote Democrat instead.

    Regardless, what you shouldn’t do is removed and complain on the internet to strangers on the internet.

    Congress people are mostly tech illiterate and willing to eat whatever bull$hit big tech lobbysits feed them. They are not, however, stupid enough to ignore constituents who are angry enough to send them a letter. Why? Because most Americans only ever vote in presidential elections, so the population of people who will vote in a midterm (much less a primary) is very small. Going through the effort to write an email (or mail a physical letter) is a strong signal that you are one of those people who will get their ass out to the polls on election day and hurt their chances.








  • I don’t think this is accurate. If your only interaction to Americans is the terminally online dipshits, I can see why you’d think that. Americans are just ignorant, especially now with how consolidated mainstream media has become. Fox News is never going to report on the real tragedies the American military creates when it bombs civilians, and for a lot of people Fox, CBS, CNN, etc are their only source of news. They’re very effective propagandists.

    But try as they might, not even the most adept propagandist can hide the gas prices. It’s an inconvenient truth not even Trump can lie his way out of.


  • I guess they found it difficult to resist the temptations of the data broker industry, and are now trying to pivot to a being iPhone style security theatre while profiting off selling their customer’s data?

    Either that, or they have reason to think their users are stupid enough to fall for this? Personally, I have the same opinion of /e/os and fairphone users: they bothered to spend the time researching alternatives to the duopoly, yet they made the wrong choice anyways lmao

    Graphene just can’t stop winning.



  • This is kinda weak IMO. Here’s the “conflict of interest” they point out for Lennart Poettering:

    Co-founded Amutable seven months earlier. Amutable’s stated mission is “cryptographically verifiable integrity for Linux workloads.” Every new identity field in systemd strengthens the market case for commercial integrity tooling. Poettering made no disclosure of his commercial interest.

    So apparently his eyes turned to Looney Tunes dollar signs when he saw one new identity field? That’s ridicuolous, especially since he can add whatever he wants to systemd, whenever he wants.

    Another conflict they point out is that systemd has no community steering committee or voting structure. Everyone knows this, it’s not new, and it’s part of the reason why people dislike systemd. It’s also why the previous conflict doesn’t make sense.

    The rest of the article is a dump of random facts and timelines, likely designed to build credibility in the minds of people who are already pissed about the age verification thing, and are looking (uncritically) for anything to make them more pissed. Aka, this is ragebait more than anything substantial.

    The only part that I think is actually worth pointing out is that the person who merged the PR is a Microsoft employee, and Microsoft is one of the companies that has lobbied for age verification. Idk if that’s legally actionable, but it sure is useful context I didn’t have before (although I’m sure many people did know that)

    Edit: LMAO and I forgot, Devuan is an anti-systemd distro. That’s a conflict of interest they didn’t disclose in this article either



  • I self-host forgejo on a spare machine in my home. I also set up automatic encrypted backup using Restic on Backblaze (but any S3 compatible host will work). It might not be a perfect backup strategy, but it’s good enough for me, and perfectly manageable with my limited skills. Using wireguard, I can easily access it from outside my home. I also get much better uptime than Github lol

    Importantly, I do NOT share this with anyone. It’s purely for my own private development and personal projects (I have a ton of these). Even when contributing to something on github, I work in a mirror on my private forgejo, and only push to github to create the PR when it’s ready.

    Any open source projects I’ve released (I only have a few) go on Codeberg, but I still have a lot of projects I contribute to and rely on that are on Github. That’s really the hard part: getting other people to migrate to something else.






  • Yes and no. It depends on how you manage symbol visibility. There is such a thing as a “private” dependency. For example:

    • libA uses a patched version of libZ, and breaks ABI compat with the upstream version
    • Your program links with libA and upstream libZ dynamically

    If LibA links with libZ statically, and doesn’t expose any internal libZ structures through its own APIs, then there’s absolutely no problem. Your code will never directly interact with the internal libZ of libA.

    If LibZ is exposed by LibA, or LibA dynamically links with LibZ, then you have a problem. I’m not an expert on dynamic linkers, but they’re might be some platform specific workarounds you can do.

    Something else I’ve seen before is some libraries use preprocessor macros for their namespaces. That way, you can change the namespace (and thus symbol names) at compile time. That way, you can have multiple copies of the same library coexisting, even with type safety at compile time.