Seattle / Basketball / Urbanism / SWE Building: coves.social @coves.team

  • 2 posts
  • 9 comments
Joined 3 months ago
Cake day: August 22nd, 2026

From the technical side anyone can spin up their own Lemmy instance and view all votes, but I’m curious at what the community’s perspective on how “private” that is. I think Mbin already shows upvoters? Piefed allows anonymous voting. I also know there are sites which show all voting history, but assuming those are fairly disliked.

My general questions to the community: - Do you expect your votes to be private, or just not shown in the UI? - Would per-voter votes showing up on another aggregator platform bother you, even though your instance already shares them with other servers?

For context I’m the dev doing some two way bridge interop between atproto + Threadiverse, in atproto the votes/likes are generally publicly accessible, you just look at the users repo through something like pdsls.dev, they’re readable and archivable by anyone. In my opinion this isn’t that big of a problem since it’s fairly hard to look at and discern (Ex all my votes: https://pdsls.dev/at://did:plc:lmdkqemqrqnfiix72pyjhfey/social.coves.feed.vote). Ultimately trying to figure out if there’s already a mutual understanding that they are public and we can just mirror them or whether they should stay hidden as an aggregate.

  • I’m not surprised it’s moving this direction, but I am surprised it’s moving this direction now.

    Hardware is extremely difficult to find right now and token prices are falling off a cliff in terms of price per intelligence. About 6 months ago I was talking about how it’s only going to get cheaper from here and still seems to hold up today, we really don’t need anything better than Opus 5.5 and compute is only going to keep increasing (price decreasing) who knows what the field will look like next year.

    Either way I’m happy to live in a world pushing towards that, just surprised.

  • I was also impacted, you need to remove the payload that got dumped:

    Payload: /tmp/.pxb/{curl,wget}, /tmp/.spid

    Two processes named khungtaskd / cron

    They also stole your admin token so go to the Plex UI and log out of all devices for whichever account has ownership of the instance.

    Then you can reclaim ownership and it resets the admin token.

    You should likely be fine, I didn’t have any crypto miners on mine, it was just in a docker instance and didn’t have access outside of it. I would be much more worried if it was a direct install on a main PC.

    Also install watch tower

  • These research papers talking about AI leading to cognitive decline seem so asinine when certain people’s productivity has just skyrocketed under AI.

    Sure the hand coding capabilities decline, but that’s replaced by thinking around the actually product or architecture.

    A huge sect of new Linux users and Selfhosters are talking about how much AI has enabled them yet we’re still bringing up papers on cognitive decline that were written on models from 3-4 years ago when Claude Code didn’t even exist.

  • Probably the right decision given there’s no way to truly tell what level of AI generation or effort within the project itself with AI has taken place.

    I understand the willingness to ban low effort low quality one shot projects, but given most software nowadays incorporating some level of LLMs, I can’t ever see a blanket ban working out anywhere.

  • It’s interesting I have the exact opposite perspective with AI in regards to selfhosting.

    The customizability is now endless for me, I can do anything, customize anything, problems that are typically 1-2 hours are fixed in <5 minutes.

    Don’t want to fiddle w/ a GUI? Shoot off a message and it’s done.

  • OP if you don’t mind running this through a Hermes / OpenClaw harness this is probably the easiest way with pre built email connectors. Also if you don’t mind spending a few bucks a month DeepSeek v4 will blow out anything you run locally for pennies (or gpt luna as of last wed.)

    It can also set up its own custom connector if needed and run as needed via CRON.