archomrade [he/him]

  • 7 Posts
  • 299 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle




  • People forget that nationwide elections are ordinarily determined by infrequent voters to begin with.

    It wasn’t high-propensity voters voting for trump, third party, or abstaining, it was ordinary non-political americans who didn’t see a point in voting for a status-quo center-right candidate.

    People have been screaming at democrats since at least 2008 that they need more progressive, more radical policies, and they’ve repeatedly avoided addressing those concerns. Trump ran in 2016 as a moderate. He came out on the left of fucking hillary clinton on the war in Iraq and interventionism. She lost to trump because he maneuvered to the left of her, and democrats still have not fucking learned.

    Democrats need to let go of their moderate progenitors and re-build their base from the bottom left. They’re leaving millions of voters on the table because they keep hamstringing themselves on a bygone era of popular neoliberalism, and there’s nobody left to blame now but the party itself.










  • Browsing their coms can be a pretty unique experience, especially if you go in with a preformed idea of what their communities are like. There’s a huge spread of interests and experiences, and sometimes you can be browsing a niche community and forget that these were the people posting BPB on lemmy.world threads a year ago.

    Knowing the academic writings and history they’re referencing helps a lot with understanding where they are coming from, even if you may not agree with all of it.


  • This is the most reasonable response.

    A lot of people here have long since made up their mind about hexbear based both on repeated meta posting on the topic and possibly a bad experience or two with them on a topic they assumed was uncontested but is a landmine topic for communists of a particular bent

    I’ve personally never had a bad experience with hexbears, possibly because I’m more empathetic to their perspective, but more likely because I know when it’s time to disengage. There are users on lemmy who feel strongly about a certain topic that’s abrasive to hexbear users and dig in their heels when jeered at (or maybe feel a personal responsibility to stand them down) and are usually the users here who have the most complaints, because the standard reaction from hexbear users is irreverence (both the users and the mods).

    Unlike a lot of liberals coming from reddit, communists often don’t have delusions about the neutrality of moderation and so they’ll ban you on a whim if they think you’re there to stir shit. They use the ban hammer judiciously even with users on their own instance. That’s often the biggest complaint both with hexbear and with lemmy.ml.




  • It depends on the attack vector. Typically you’re right, but malicious .lnk files are often paired with other malicious methods to infect machines. Sometimes they’re configured as a worm that copies and spreads when a flash drive is connected, sometimes they’re configured to download a remote payload when another script or program is started. The problem is that it’s a type of file that’s often overlooked because it seems innocent.

    It isn’t necessarily the case that the Trojan needs to be interacted with by the user in order to execute the malicious code. Just having the file on your machine opens the door for all kinds of attacks (especially if you’re using a headless setup: you wouldn’t necessarily know you have the .lnk file in the system unless you’re manually unpacking your downloads yourself). All it needs is for another piece of infected code to run and look for that file, and it can open the door for more traditional malicious code.


    Edit: just as a for-instance - If I was a black hat and wanted to spread some malicious code, I could include this .lnk file in a torrent (innocuous enough to slip by unnoticed by most people/unscrupulous pirates), and then maybe place a line of code in a jellyfin plugin or script that looks for that file and executes it if it’s found. Because the attack isn’t buried in the plugin or script itself (most people wouldn’t think much of a line of code that’s simply pointing to temp file already on your system), it could theoretically go unnoticed for long enough to catch a few hundred or thousand machines.