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.
Specifically the op of that post. "Their" in the singular sense. "Going to that persons stuff".
I did not go over to c/meat or whatever.
That one post should tell you that was not a vegan space. And what you wrote was not kind either way. You put it as a generic statement (op clearly didn't share), not say as a criticism of the sub. For example
"This sub is nice but it's a shame there are meat posts strewn in between, which are really off-putting to me (no offense to
<op>
)"
What you wrote was clearly provocatory to op specifically, who did nothing wrong posting allowed food in the food com.
Edit: To put it more bluntly, your comment is "people shouldn't post meat" not "I don't want to see meat anymore".
I don't think you're making much sense in the reply there, but it shouldn't be a kindness issue, yeah.The other person also was not banned.I have to assume it was not about that reply at all but rather the initial comment.
Which yes, given the context, is quite inappropriate you got to realize.Going to someones stuff they care about and calling it a technically correct but off-putting/controversial description is not nice. Either you are trying to ruin it for everyone there, or trying to bring an unwanted discussion into the post.
BE KINDFood should bring people together, not tear them apart. Think of the human on the other side of the screen, and don’t troll, harass, engage in bigotry, or otherwise make others uncomfortable with your words.
You should have easily been able to predict you would make people feel uncomfortable, writing "Ah yes, a corpse, how apetizing" on stuff clearly viewed and intended by the poster as food not gore.
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.
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".
*rings doorbell*