dbtng

The bright red rubbery utensil meant for scraping cake mix and gravy out of bowls. What is that? This really is my kitchenware. I'll put it whatever side you say.

This bot's whole purpose is to import crap from Reddit to ... here? Why would anyone want that? Somebody did a bunch of work, made an instance and a bot, and they've currently got it spamming Lemmy ... just to enshitifiy lemmy.

Lemmit.Online bot@lemmit.online

I blocked the bot and the instance, but I have to login in order for that to be effective. If I don't login, this stuff is all over the main feed.

Am I the only one that thinks this is spam?

...
Edit ... Thanks, people. Learned some things.

I was a VMware admin. I drank the freakin koolaid. Got the certs. I was planning on a career as an architect. Did ok.

Then Broadcom. Fukers.

My boss said screw em, we go Proxmox. So now I live and breathe Proxmox.
PVE is a heap of janky hax, so you gotta get expert real fast.
PBS is cutting edge software that breaks twice a week, so ya gotta get expert real fast.
And now I'm an expert. Especially at PBS. DR. Site-to-site. I can do that shit.

Now that I have this new skillset, where can I use it?
Who's using Proxmox?

Lemming? Ya, I know. Prbly not. But he's kinda cute. I wiped off most of the bird shit.

GC jobs are hanging or not finishing after upgrade to 3.4 for some users.

Staff are currently mystified. Customers are rolling back to 3.3.

"there was the improvements to reduce the number of multiple atime updates on already seen chunks (as keep track by the cache) and the change in iteration logic to better correlate index files, as well as the bugfix for the possibly untouched chunks. Why this has negative effects with your particular setup remains to be clarified, until now the possible cause is only hypothesis."

This one's gonna drown. I call it the Submariner.

I'm thinking about spinning up my own Lemmy server. I want to tinker with the bits. There's some shit going on under the hood that's hush hush, and I want to poke at it.

I've got a domain. I've sure got the gear, but my home internet doesn't allow me to personally host. I work for an MSP. I was gonna run some stuff for free there, but I'm not so sure about that now. I'll make the old man an offer and see if I can get it cheap, but with a real contract. I'd consider other hosting, but I really hate the big clouds. Still figuring out where I'll run ...

The fediverse comms are all in a tizzy about lemm.ee shutting down. I don't see any help there. I've found this:

https://join-lemmy.org/docs/administration/install_docker.html
(And also the Ansible and From Scratch options.)

There's a lot of options for install. Anybody got any pointers or preferences?

Hey johntash. Check out this guy's project. Lemvotes.
https://blog.gregtech.eu/posts/lemvotes/

I'm not saying we should host it, but let's get it on the radar. Its a new project in rapid dev, even if we wanted to provide the service, we should wait for a stable rev.

But ... this thing bears watching. The guy is using instance-admin level perms to provide data that should be searchable by end users. I foresee some blowback. The dev may need support or a mirror in the future, and my own vote is firmly on their side.

Just check it out, man.

Today I learned that one can easily look up a user's voting history.

Go to https://lemvotes.org/
Select User, drop their handle there, and run the report.

After I looked up my stalker, ... (I love you and your attention, plz keep it up!) ... I looked up myself.
I'm very happy to find that I've almost entirely upvoted. And yes, I went on a couple sprees and downvoted some crap. That's kinda ugly to look at now.

It made me think about how I behave here. You know, in that its so damn easy to see.

And back to the question at hand. What's your upvote/downvote percentage?

Are you a Lemmy Shitbird?

...
EDIT ... The author of lemvotes posted about it here.
https://blog.gregtech.eu/posts/lemvotes/

Steam had the entire Witcher series on sale for a few dollars. I bought everything for the first 3 games.

There was some discussion of it at the time, and folks seem to agree that the first one in the series sucks hard.
As that seemed to be the worst plan, I went with it.

Yes. "It's rough." I guess the engine and content have gotten some backports and extensions. I'm not sure if you could ~~play other characters besides Geralt before, but now you can~~. (EDIT ... Sorry, this seems to be BS. My bad.) They updated the graphics a lot. Its not great, but I think they fixed most of the really bad problems.

I don't know about the story. Seems pretty awful. Awkward acting. Its been fun just trying to play the damn thing.

Um ... I sort of like it. Gonna play some more now ...

cross-posted from: https://eviltoast.org/post/13627562

I'm trying to unfuk myself from Google. It's an admirable goal, but damned difficult to do if you intend to continue using the Internet.

Except ... well ... you actually can do this. You can run a search proxy locally that will completely obfuscate you to the search engines and also strip out all of the tracking and ads they spit back at you.

I think there are more apps, but there are two primary search proxy platforms that are well developed and support running in a Docker container, so you could run it on any Windows or Linux box.

....

Whoogle https://github.com/benbusby/whoogle-search

Try this app first. Low system requirements. Super, super easy to setup. "Whoogle is intended to only ever be deployed to private instances by individuals of any background, with as little effort as possible." Let Whoogle be your gateway to running a search proxy.

I've run Whoogle for almost 6 months now. Google has tried to break it twice. Had to adjust some docker params and upgrade the LXC to fix. I'm extremely satisfied with Whoogle.

....

SearXNG - https://github.com/searxng/searxng

This app is the all around better tool, but its much more complicated to manage. It's had a fractious background, forked from an older project called SearX. The author of Whoogle says, "I'm a huge fan of Searx though and encourage anyone to use that instead if they want access to other search engines/a different UI/more configuration."

I've just deployed SearXNG today based on benbusby's recommendation. Ya know, I was a Whoogle fan, but this is just a step above. 140+ search engines, it looks awesome, and its got a large contributor list with lots of recent commits.

....

I run Proxmox VE, and both of these apps have been given the tteck treatment for easy setup.

Whoogle - https://community-scripts.github.io/ProxmoxVE/scripts?id=whoogle

SearXNG - https://community-scripts.github.io/ProxmoxVE/scripts?id=searxng

cross-posted from: https://eviltoast.org/post/14192399

I have love/hate relationship with Proxmox Backup Server (PBS). It's a groundbreaking product, cutting edge technology, entirely free, and a complete pain in the ass. Because of all of the above, I've spent a good deal of time haunting the user forum, irritating the staff, and spreading unpleasant truths about PBS.

So, what's amazing about Proxmox Backup Server? It's the realized dream of complete dedupe. There are a couple similar products out there, but largely whatever you think you know about backups probably only barely applies to PBS.

PBS should be deployed on SSD, because its really a huge database of file chunks. (Literally, they are called .chunks.) PBS scans its .chunks to see if it already has a .chunk, and if it does, it is not copied. Absolute dedupe, every time. A backup job consists of a whole lot of reading and calculating, but as little writing as possible. The actual backup itself, such as it exists, is a set of metadata that says which .chunks will be needed to build the VM files. When a backup is deleted, the metadata is deleted. If the .chunks that the metadata pointed at are not used by any other backup and continue to go untouched for a couple days, they are purged by garbage collection.

Think about how this will work out. When you delete a backup you are just deleting your ability to assemble those .chunks into a disk file, essentially nothing happens to the data on the back end for 2 days. If you immediately ran another backup, it's_going_to_run_like_an_incremental. Because all the data is there still. So the only thing it will write is a new metadata set (aka "backup") and any delta that's occurred on the vm since last backup. This is completely different from any sort of backup data management you've done before.

When a backup runs in Proxmox and the backup target is a PBS server, the VM is NOT stunned for a snapshot. The 'stun and snapshot' tactic is present in almost every virtual backup system out there in order to get the VM running on a delta disk, leaving the main disk available to be scanned for backup. PBS simply does not do this.

What PBS does do instead of a snapshot is hard to describe, but in pursuing their goal of not having a VM stun, they introduced a far worse flaw. The VM can hang on write if the sector to be written is also being backed up at that moment, lockstep with the storage write until that chunk of data is done backing up. Because of this issue, they introduced another feature that is essentially write caching, but they call it fleecing. (I'm told the name fleecing is part of the qemu standard.) Fleecing brought its own game-killer bugs to the table, only partially fixed in the latest version.

PBS does some really cool site to site sync tricks. You can establish a Remote relationship, and then a Sync Job. It's a nerdy interface, and not at all user friendly, but you can tell it exactly what to sync. They recently added Push style jobs, which will feel more similar to common backup systems than the original Pull jobs. When you start doing site to site sync and your VM backup populations get mixed, you immediately discover the need for Namespaces to segregate them, and that can be an intricate rabbit hole.

I just noticed their site blurb says PBS does physical hosts, which isn't exactly a lie, but pretty close. PBS is for backing up Proxmox guests.

If you run virtual machines professionally, you should know about Proxmox and have at least tried it. If you use Proxmox with any regularity, you should check out PBS. Here's a shot of my homelab PBS. Note the dedupe factor.

___