Kalcifer

What I like about the Gadsden flag, as opposed to this one -- according to how I interpret it, anyways -- is that it advocates for the use of one's voice before violence. The main symbol on the Gadsden flag is a timber rattlesnake. If you think about such a rattlesnake in nature, when you get too close to them, or provide them with a reason to feel wary, or uncomfortable they won't immediately attack you, but will instead provide you with an auditory, nonviolent warning. It's only when one ignores their warnings, and continues to harass the snake, or give them a reason to think that they are under immediate threat of harm that they will fight back, and will not hesitate to do so. In all other circumstances, the rattlesnake will mind it's own business, and let you do the very same. I find this behaviour admirable of a creature, and it is, in my opinion, the true ethos of libertarianism. The Canada goose, on the other hand, won't hesitate to harass you. they will routinely attack people just relaxing in a park. They provide little warning to someone that they find threatening, and will often choose to immediately strike out. This is not behaviour that should be emulated, or admired, in my opinion.

dd?

I subconsciously tried wiping my screen.

I've found that the only way to dual boot reliably is to have windows installed on a separate, dedicated drive, and to keep all drives used by Linux air-gapped from the windows drive. Fast start and hibernate must also be disabled within windows to prevent it from putting hardware in an undefined state.

That being said, I haven't actually found any regular use for the windows install in years. mostly just keep it around as a sort of backup failsafe, or just in case there is a game that refuses to work in Linux. 99 times out of 100 it simply just collects dust.

They're viewable on Lemmy too!

Yeah, I'm starting to agree. I've found that it gets to a point where you essentially just cant keep up with the griefers if you are drawing over virgin pixels. I second the idea of making it the same cooldown for placing pixels for everybody. I don't think theres a way to structure it to always favor defenders. There will always be an edge case where the attackers will have the upperhand.

I'm also starting to think that being able to have multiple pixels queued can also put a defender at a disadvantage. When your actively placing pixels, you are always at 1 pixel with a cooldown, but someone could come along with 6 stored pixels, and just dump them consequtively in a spot giving them a permanent space advantage that you will never be able to recoup if the attackers keep at it.

A couple more ideas popped into my head:

1. When placing a pixel on your own pixel, the time delay should be the same as placing over a virgin background. I don't see the point in punishing a user for drawing over their own art.
2. Defenders should have a more favorable time delay than attackers. For example, when placing a pixel over someone else's pixel that replaced your previous pixel (defending), the time delay should be short (e.g. the same as when placing over a virgin background), whereas when you place a pixel over someone else's pixel that wasn't preivously the location of one of your own (attacking), you should get the longer time delay (e.g. 1 minute).

• Lemmy: Thunder
• Maps: Organic Maps
• Weather: Breezy
• Tuner: Noteworthy Tuner
• Matrix: Element Android (it's got a lot of issues, but, as far as I can tell, it's the best that there currently is)

Of course. My inquiry was out of theoretical curiosity, and not so much anything practicaly useful for security, or privacy.

This works great for 3d-printing but wont work as well if you intend to export to CAM systems that can use a drill to make the holes.

Why's that?

Would it be possible to at least show the total subscribers from all federated instances?