Venia Silente

Not really federated. You can’t, for example, raise issues or set PR requests from another instance.

Never have been. </astronaut-meme>

inb4 “it depends” but, well, really, it depends, on the what.

Having something to lose because you care for them means they are a liability and a weak point that can be exploited. They are also a natural distraction. In that sense, their presence and status as “things to care for” make you weaker; however, the fact that you care grants you motivation, as well as spite, that can be pretty hard to find elsewhere. You won’t find people who truly care so much as to give their lives for their employer, even top level bootlickers shy away once things get dicey. And spite is quite the damn effective motivator! So, the fact that you can have something to lose promotes you to keep up a higher “action baseline”: waking up in the mornings, keeping yourself healthy and open enough to actually go and protect, etc…; those make you stronger.

As someone who has had 8 cats before and has also provided support for 7 other ones, I can easily tell that their cute little purrs are energizing and I’m more active and aware of the world around me simply because I have to find good quality cat food for cheaper. So if anything I’m a “stronger” agent in the commerce.

Boot it once, don’t let it ever fully power down (suspend is fine).

If your V1 is on firmware 3.1 or 4.1 but does not work with the RCM jig and you have run your serial ID through the test site and it comes up as “possibly ipatched”, you might be able to use “online boot” via Pegascape, which you can also host locally (eg.: in a raspberry pi) and there is at least one alternative frontend. It’s pretty much the only way to boot an ipatched > 3.x into hekate without a hardmod, and even then it’s only limited to firmware 4.x that I know.

(On such a setup, you’d then install an eMMC partition for CFW with the firmware you want, eg.: 16.x).