• 0 Posts
  • 490 Comments
Joined 2 years ago
cake
Cake day: July 9th, 2023

help-circle






  • Yes! What the Dems have been is history. What voters make it is the future. That’s what primaries are for. So imagine what you want them to stand for and vote for the candidates that fit that vision.

    Everyone should vote in their primaries, even if they can’t make the general. Your vote is higher impact there than in the general election for a few reasons:

    1. The folks who usually vote in the primaries, bless ‘em, are not good at picking winners
    2. Participation tends to be so low that it doesn’t take many additional votes to elect progressives
    3. Progressives are MAGA kryptonite; people will actually show up for them in the general.

    Also voting in primaries is easier, since early voting can often be completed digitally or by mail. You don’t have to take off work. And if you vote in person, you don’t have to be registered beforehand. Just show up to your polling center and they’ll have you fill out a special affidavit ballot that’s submitted in an envelope with your registration info.

    Vote in your primaries people.




  • I think you’re describing an important step of online mental hygiene. The reality is that humans have not evolved with the daily emotional bandwidth necessary for one to handle a planet’s worth of grief responsibly and without inuring oneself to others’ suffering.

    I’ve seen people criticize this as head-in-sand, that you should remain available to amplify voices and causes in online discourse (especially theirs). I see that criticism as unthoughtful, bordering on unkind, and a critical problem with how we do online advocacy.

    (Aside: “conflict” appears twice in keyword list, which has no effect now but can cause unexpected behavior later)



  • I’ve been checking out the localhost tracking vulnerability and there’s something I can’t work out: it’s not even a terribly obscure or convoluted exploit, especially Yandex’s implementation that’s been chugging for more than 8 years over basic HTTP. It’s just a glaring sandboxing workaround that’s been exclusive to this OS for more than a decade.

    No matter how many ways I look at it, I haven’t come up with a reasonable explanation for how it was ignored, by demonstrably capable engineers, unless Google itself had use for it in the first place. And that fits a pattern of selective competence in information security that they just can’t seem to quit.

    In short it’s the data collection backdoors they leave themselves that defeat the otherwise top-tier security of their consumer offerings, and it’s why I’ll probably never trust anything they’ve touched until I’ve taken it apart and put it back together again.

    So no, you probably shouldn’t use it. Trusting the privacy or security claims of any adtech company will always be a mistake.



  • IME this sort of error is often related to the aggregation of traffic through a single IP address. (Commonly: VPNs, public WiFi hotspots, large commercial networks, and so forth.)

    The safest workaround is to temporarily change your server location (if using a VPN, which is advisable).

    Another easy solution is a different connection, such as switching to mobile data (less safe due to ISP fingerprinting).

    Also, since this error is often generated by simple time-based access quotas (throttling), you can confirm the root cause by refreshing once the next hour or day ticks over. (If due to throttling, the error will suddenly disappear.)