eleijeep

joined 3 months ago
[–] eleijeep@piefed.social 9 points 13 hours ago (7 children)

Is this game a casino?

[–] eleijeep@piefed.social 3 points 14 hours ago

Huge gap in the market for some talented ASIC engineers.

[–] eleijeep@piefed.social 4 points 22 hours ago

This year I have been mostly using:

  • Debian 13
  • Bazzite
  • Vanilla OS
[–] eleijeep@piefed.social 3 points 22 hours ago

I've always thought of it as being a measure of the "WTF is that one again?" factor of a distro. Maybe it represents how unmemorable the name is.

[–] eleijeep@piefed.social 3 points 22 hours ago (1 children)

This is about debt-collection for unpaid bills. According to the article, it's clearly a broken system that punishes the most vulnerable in society, but still, the headline is an inflammatory (and clickbait) way to present that.

[–] eleijeep@piefed.social 8 points 1 day ago

Blockchain is a decentralized distributed-consensus protocol that uses proof-of-{work/stake} to prevent a Sybil attack (>50% malicious nodes) from taking control of the consensus algorithm.

To recap, blockchain gives you:

  1. decentralized
  2. distributed consensus
  3. with Sybil attack resistance

If you don't need any one of those 3 attributes then you do not need blockchain.

For the Fediverse, only property 1 (decentralized) is required/desirable. 2 (distributed consensus) is not required since the architecture is Federated; that is, each server decides on it's own set of available posts, comments and moderator actions, and chooses which of those things to show to users and to federate to other servers. Since property 2 is made redundant by federation, there is no risk of Sybil attack, so property 3 is also redundant.

If you actually wanted to have a decentralized distributed consensus algorithm to ensure that all posts/comments/etc. were replicated exactly across all servers then you could use a distributed consensus algorithm like Raft or Paxos. If you then also wanted to mitigate Sybil attacks on the network then you could simply use a whitelist of trusted peers, as each Fediverse server already uses for federation.

Only if you wanted a truly peer-to-peer decentralized distributed consensus protocol that is resistant to attack would you need to use a blockchain protocol. But, ask yourself why anyone would need such a consensus model when it would preclude localized moderation, "defederation" would result in hard forks of the ledger, and every action in the network would be publically visible for all time making post deletion (moderation) impossible.

Blockchain was invented for online currency where you actually need distributed consensus of a ledger in a Byzantine environment. It's not really a model that is suitable for social media, messaging, publishing or any of the other applications that it has been shoe-horned into.

[–] eleijeep@piefed.social 3 points 2 days ago (1 children)

🤖 LLM-generated lemmy post 🤖 LLM-generated README 🤖 AI-generated banner image in README

With that much AI use visible, it's an obvious question to ask.

[–] eleijeep@piefed.social 4 points 2 days ago (5 children)

Is this vibe-coded?

[–] eleijeep@piefed.social 9 points 2 days ago

Just because they're "officials" doesn't mean they shouldn't be on the sex-offenders register.

 

Maurice Ravel's Boléro performed on homemade 8-bit instruments. Official music video.

9 hours and 42 minutes of footage
52 mixer channels
13 neck- and bowties
9 different instruments
1 crazy automaton
0 regrets

 

If you just want to see the end product, skip to 26:34

 

In March 2024, Mozilla said it was winding down its collaboration with Onerep — an identity protection service offered with the Firefox web browser that promises to remove users from hundreds of people-search sites — after KrebsOnSecurity revealed Onerep’s founder had created dozens of people-search services and was continuing to operate at least one of them. Sixteen months later, however, Mozilla is still promoting Onerep. This week, Mozilla announced its partnership with Onerep will officially end next month.

 

I've been noticing recently that a lot of posts in large communities are from [deleted] users (see the image at the bottom of this post for an example). I assume this is a means of pre-emptive ban-evasion and block-evasion by a user who is either running their own instance or just signing up a lot of accounts.

I quite like piefed's warning labels that appear on posts by users with low karma, and I also quite like being able to block users who spam my feed, and I feel like this post-then-delete-account tactic is an exploit to bypass any kind of accountability on the poster's part.

Here are some suggestions for how this problem could be mitigated:

  • When a user deletes their account, their posts will no longer display in the Subscribed/Local/All feeds. Perhaps only showing if you visit the community page directly, or
  • A post by a deleted user is down-ranked in the Top/Hot/Popular ranking system so that it appears much further down the page, or
  • De-federate from the instance(s) that are allowing these post-then-delete-account tactics without intervention. Particularly if they are personal instances run by the individual who is doing this.

I haven't managed to catch a before/after of one of these posts to see what the username/domain looks like, but I imagine instance admins should be able to see the history of the post?

Example (and yes these were 7 consecutive posts in my feed all with the same issue):

EhlJXgEB48dNPbD.png

 

Another well researched and well presented video by Benn Jordan. He worked with some security researchers to analyse the security of Flock surveillance cameras, and presents what they found, and what that means for the communities being watched by these cameras.

view more: next ›