The author of the fork declares 100 percent compatibility with the original project’s database. As you move, the database structure will be changed (new fields will be added) to be compatible with the fork, but it will still also be compatible with the original project (which simply will not use these new fields).

I used conduwuit for a long time and it seemed very stable. Now I don’t host my server anymore because my friend hosts his own server and lets me use it, so I have an account on his server.

The original developer is trying to do things slowly and stay with older versions of the dependencies, while the author of the fork is of the opinion that the dependencies should be updated to the latest versions and take advantage of their capabilities (such as performance improvements) which does not necessarily please the original author.

In addition, new features are implemented in the fork that are not present in the original project, because the author of the fork is pushing for rapid development (which doesn’t mean it’s a bad thing)

Check out conduwuit. It is a fork of conduit and you can see all the differences here

Please, just don’t. It’s pain in ass

Privacy and Apple are two opposites

That may be useful

Sign up for free access to this post Free members get access to posts like this one along with an email round-up of our week’s stories.

Joplin

Confirming: 973ec2ce022c5

Yes

So, the flash memory wasn’t built into the terminal, it was a 2.5-inch SSD drive that I yanked out of its plastic case to fit into the terminal’s SATA slot.

Once unplugged it, I dumped the disk image using the dd command onto my computer, and then I worked on that image to recover the data.

No, half of the file system sectors were corrupted, but I was able to recover all my files. I’m still wondering how my files survived exactly on uncorrupted sectors…

The device was already protected by a UPS, but it failed and shut down.

I will no longer use this device, rather I will throw it away, because I will have no more use for it.

Unfortunately, I didn’t have a backup, but I still managed to recover ALL the important files from this server, even with half of the file system sectors damaged. God, thank you. This is another lesson for the future to regularly make backups!

Unfortunately, I don’t have another power supply with the same specifications on hand, as this thin client is the only Dell device in my home 😕. Replacing the motherboard is not cost-effective for such old hardware. I’ll just buy a new thin client.

Alright, I’ll give it a try. Thanks for the suggestion!

This is a thin client. It does not have a removable TPM module, so I cannot physically “pull out” that TPM.

Yes, this is exactly the Dell Wyse 5060 with an AMD GX-424CC processor. This thin client is already old, which is why I decided to purchase a newer one with a better processor.

Anyway, thank you for your analysis! I learned a lot of new things. I will try to get it running with your advice and let you know how it goes.

However, this server will probably no longer be needed, since half of its cores are damaged. Previously, its computing power was fully utilized (the load was almost always 4.0), and it handled my tasks very well with four cores. Therefore, I cannot imagine using it with only half of its power available 😁

Good point - I’ve fixed it