Redjard

ooohhhhh, it’s cheese.

Literally unrecognizable to me, never seen anything like it. Probably couldn’t even be sold as “cheese” in the EU.

I was trying to make sense of why people recommend eating fiber with a bar of white chocolate, and what “normal way” you’d even eat it.

Edit: Why does it have cow spots? What cheeses is this assembled from??? Is the white stuff all the filler and the yellow stuff all the yellow colored filler?I am sitting here at 9pm searching cow spot "cheese" us block.

Recently I almost forgot my encryption keys. With windows I can now safely rest assured that I can always decrypt my drive with a simple file from github.
This shows the value of a great community, because while microsoft wrote the back-door, the tool to use it was developed by an independent programmer.

This would be a great application of btrfs. Copy over the boot-partition directly via cp /dev/nvme{0,1}n1p1 or similar.
Then, simply add the data partition(s) to btrfs. You can then tell btrfs to migrate all data out of the old partition, and finally remove it. All in a running system.

I have migrated the rootfs on running systems before using this method, it’s a super clean approach.

BTRFS also nicely handles the redundancy with its checksums. Usually you can’t fix bitrot between two drives, but btrfs can tell which version is correct. Makes scrubbing easier.

Modern version would be a silicon device not using any metal, that has a very low power mechanism (perhaps mechanical/chemical) that wakes it up much later where it then works as a bug. For example.

by a Nazi for Nazis.

I checked the actual code and there is no e2ee, at all.
It has some of the basic setup stuff, like giving you a recovery file, and messages are seemingly encrypted, but everyone can decrypt everything and the platform has none of the structure to deal with all the issues proper e2e brings.

As a very simple test: If you write a message in a server, close the tab. Make a new account and open that chat. You can read the message. Meaning anyone can.
The way actual e2ee does this is it signs messages for anyone in the chat at that moment. Anyone new can’t read old messages unless an old member sends them the contents.

Also this stuff is buggy in the actual functioning.

Also it’s full of trackers and weirdly loads youtube for no reason.

Also it’s full of nazis, the actual state is so much worse than the screenshots shown in the post. The top channels are “4chan” and “wagnersdom”.

Also claims to have federation with self-hostable nodes.
Def would like to see someone do some testing on it.

No, it just has artifacts that look very much like it. Like incorrectly morphing fur.

Ai slop‽

!anythingbutmetric@discuss.tchncs.de

No, 9GW of electricity, and they claim 16GW total. With a greater than 50% efficient gas plant.

What part do they make in that round thing?

The left bezzel is extremely thin due to perspective, the right one thicker than it should be. Makes no sense to put that on a sticker unless it’s purpose-designed to only work from one angle. Yours don’t have this.

I haven’t checked too deeply but I think fedora dropped the affected system between kernels 6.6 and 6.12 somewhere. 6.12+ appear to not have the modules.
Not too surprising given the system has been deprecated for a long time.

ur sentence should end with a period and there’s spacw for two commas around that »technically«

No security revisions over multiple months?

The reverse is that if you really know your stuff you can get away with fewer restarts, or even none. But you pretty much have to know every component and update you run while in that untested state.
This is similar to bugs that go away on a restart. If you don’t know why, then you haven’t really fixed it, just rolled the dice again hoping it won’t reoccur.

As for updates, on regular systems you can do update everything but the kernel. You do have to restart affected services afterwards (often done automatically).
Even on atomic systems you can switcheroo the subvolume underneath a running system.
Unfortunately the kernel is quite major, so that is a valid reason to see the need to update. Definitely not as pressing as say nginx, sshd, or sudo though. Kernel bugs bubbling up to an exposed attack surface is still quite unusual.

uptime should be handled by the kernel, so a kexec “soft-reboot” would still reset the uptime.

Might be an (almost) uniquely american meme for the circumcized?

Molly supports unified push