sabreW4K3

joined 8 months ago
[–] sabreW4K3@lazysoci.al 4 points 3 months ago (7 children)

So I've been thinking about this and I would go for a different approach.

Admins can set voting to be public or private on a server wide level.

When users vote, a key is created as the userid

The votes table is essentially: voteid, postid, userid, timestamp, salt, public

If the vote is private, userid is salt(userid, password)

And it's that simple.

[–] sabreW4K3@lazysoci.al 40 points 3 months ago (1 children)

I fucking abhor capitalism!

[–] sabreW4K3@lazysoci.al 14 points 3 months ago (1 children)

Are you using hashtags?

[–] sabreW4K3@lazysoci.al 15 points 3 months ago (9 children)

Mastodon has a redirect. I believe that's the only thing missing.

[–] sabreW4K3@lazysoci.al 1 points 3 months ago

Off the top of my head… yes, in that they integrate tighter with Mastodon and thus increase the likelihood of a wider black audience partaking in discussions.

[–] sabreW4K3@lazysoci.al 3 points 3 months ago (3 children)
[–] sabreW4K3@lazysoci.al 31 points 3 months ago

Better for Linux? I'm not sure I would say it is. Better for the world in general? When you compare things like power consumption, you can definitely see that in some use cases (the average user), ARM is superior. But for Linux? Maybe by default owing to the fact that it's more modern. As for RISC-V, the core is open source and "all" the extensions are proprietary, so it's not as open source as it pretends to be. But it's definitely better than what we're currently accustomed to as mainstream.

[–] sabreW4K3@lazysoci.al 2 points 3 months ago

Sometimes people just want a moment to themselves.

[–] sabreW4K3@lazysoci.al -3 points 3 months ago (3 children)

Also, while we're here. Let's call out instances that don't update their Lemmy version because they want to make a point, even though doing so would bring quality of life improvements to black community members. Looking at you Beehaw and even Lemmy World.

Also Lemmy.ml for turning into fuck ups. Being the second largest instance, especially one that was less mainstream in their beliefs, they just had to keep doing them. They were never going to be popular, but different and well run was enough. Then they started making questionable decisions and not explaining them. Which, being that they're so well read, know never ends well. They had more time on their hands and started being overly involved in the instance and that hurts their community members in ways in which they're too up their arse to take stock of. Step away from the admin panel, let your moderators moderate.

[–] sabreW4K3@lazysoci.al 11 points 3 months ago (6 children)

The Fediverse does have a massive white slant and the default experience isn't very embracing of different cultures.

There's a bunch of people who would like to see things improved and as of yet, there's not much consensus. The only real idea I've seen floated thus far is blocklist subscriptions.

A massive part of the problem as I see it is, and don't get me wrong, this is a symptom, not a root cause, people are inclined to use the wrong tools. Mastodon is a microblog and yet people are determined to use it for groups and nuanced conversation where their instance only supports 400 characters.

Also WriteFreely is the only active blog service in the Fediverse and needs some love.

We need to encourage people to move to tools that better fit their needs and desires and honestly part of the problem with that is that people feel they'll lose their interactions/audience and that is about Mastodon being shit, because while they can focus on making things more seamless with Lemmy and soon to be Discourse, NodeBB, etc. They're seemingly not willing to.

In regards to Lemmy specifically. Lemmy has a problem. You can see that by the fact this has been voted down to oblivion. When people treat ALL like a personal subscription feed and vote down things they're not interested in or dislike, it creates a monoculture. And no, I'm not saying don't downvote things, but there's a difference between voting down something because it's not great in a community and because you're trying to curate ALL. Maybe a solution is to add local/subscribed only voting options for communities. Lemmy needs to learn to embrace things that aren't for you and sometimes, in fact most times, that's as simple as saying, "that's not for me, I'll ignore it."

[–] sabreW4K3@lazysoci.al 19 points 3 months ago (1 children)

This is great, you should post it to !dataisbeautiful@mander.xyz

 

YouTube is currently experimenting with server-side ad injection. This means that the ad is being added directly into the video stream.

This breaks sponsorblock since now all timestamps are offset by the ad times.

For now, I set up the server to detect when someone is submitting from a browser with this happening and rejecting the submission to prevent the database from getting filled with incorrect submissions.

 

Just trying to check and make sure I never missed any. Is it just writefreely and plume right now?

 

Pixelfed Discovery is about to get supercharged!

Install a new server, and it will fetch trending posts and accounts, populate hashtags and synchronize followers/following lists and counts using our new service!

Already have a server? Opt-in to many discovery feeds, profile and hashtag suggestions and comment/avatar backfilling with fine grained config settings.

We’re also improving hashtag federation and public/guest access, enabling non-users to browse trending posts and hashtags!

🧭 🚀 ✨

 

Looks like PixelFed Groups are coming along nicely.

 

LunaSea, the open source Usenet monitoring app is pronounced dead for the most part. The developer via a Reddit thread said this:

tl;dr: development focus has shifted to a successor to LunaSea and is slowly being worked on. No timelines at this time, as I’m working on it when I have the drive to spend time on it. LunaSea is in maintenance mode and won’t be receiving any updates unless there is a major breaking issue discovered due to one of the supported modules having a breaking change.


LunaSea was started over 5 years ago and in truth has a really poor code base. Mix of inexperience at the time with good design patterns alongside rapid feature releases has grown LunaSea to a point of being a huge time investment to make any major changes to the project.

  • Mix that in with a few other things, I have lost a lot of interest in working on LunaSea. Some things include:
  • A tale as old as time in the industry: major burnout. This has triggered me to spend a lot more time investing in hobbies outside of coding and my computer in general
  • Getting married late last year and spending more personal time with my wife
  • Planning a cross-country move later this year and preparing for that
  • Taking up a higher seniority position in my professional career (also as a software engineer) which has me committing more time to my career

You also pointed out a really good fact, LunaSea does not really have any income. As it is now, donations are about equal to the infrastructure cost for maintaining LunaSea. Between donations on all the different platforms and Ko-Fi, I average approximately $40-$50/month.

It’s increasingly difficult to want to invest a lot of time into something that isn’t really garnering any financial gains. I would probably estimate at least 3,000 hours have been spent working on LunaSea, and while I am a huge proponent of open-source and free applications, and I don’t regret making LunaSea FOSS, I do wish that I had more financial gains to show for how much time was invested working on the project over the years.

All that being said, I’ve slowly been chipping away at working on a successor to LunaSea. LunaSea is no longer being worked on but I will publish a fix for any major breaking bugs if they occur. As it is now, LunaSea does have minor non-breaking bugs but is in a state where all intended functionality works, so there is no need for any updates.

The successor will remain fully open-source, but will charge for the client application when installed from a monetization-supported platform (such as the App Store, Play Store, etc.). However, free copies of the binaries (IPAs, APKs, etc.) will always be available officially.

This will be a complete rewrite that shifts to a server-client approach where the user would install/run (via Docker) a server component and the client application connects only to that. It allows me to start fresh away from all of the technical debt while having a much improved experience across the board.

However, I’ll admit I’m not overly focused on this either. I work on it when I want to, and I’m not putting any pressure on myself to meet any timelines or release in any timeframe. I really love software engineering and want to avoid burning out again.

I made the mistake of giving general timelines before regarding this project and have missed them all, so at this point I can only say it will be ready when it’s ready. Progress is still being made (albeit admittedly slowly), and I will remain monitoring feedback and giving support for LunaSea when I can.

 

Is it possible to blog in the AI era?

I write short stories every now and then and I throw them online. I also have a tech blog, where I moan about the decisions software I use make and with my "infinite wisdom", I tell them what they should be doing instead.

I used to host both on Medium, but Medium got greedy. Then it was WordPress, but now even they're trying to be greedy bastards and use my shit for training AI.

Some would argue that WordPress paid hosting will exempt me from the AI training, but for less than 100 visitors a year, it's not really worth the expense.

So what is the solution? I ask the greater minds of this community for suggestions.

 

I'm trying to run Headphones via a Docker container on my Raspberry Pi 5, but things don't seem to be going well. It's like it brings the Pi down to its knees or something and all this despite the fact that it never appears to really start let alone finish the full scan. Anyone got any experience? Any tips? Anything I might've missed?

view more: ‹ prev next ›