it occurs to me that what in IT we call "security" in most other engineering disciplines would be called "basic safety engineering", or even, "material science"

in some cases your, common sense,

"Why are you building this 4 lane bridge out of straw??"

@hirojin this is reasonable, but as a slight counterpoint, most bridge designers don't have to cope with routine assault by brigades of malicious assholes armed with explosives and bulldozers.

@brennen i will accept your counterpoint, as soon as we figure out our material science

or, as soon as we figure out what our material is, and what our tools are, which bits are the plumbing, and which bits are the porcelain…

@brennen but, anyway, that part would actually fall under security

if such things kept occurring, a government could post an army at each end of the bridge, and at each pier.

or take for instance London: after its subway system became target of frequent terrorist attacks, all trash bins were replaced with see-through bin-bags.

i believe San Francisco, which was never target to any such attacks, reacted by closing access to all public restrooms. 🤷‍♀️

Security it getting people to lie to auditors and the more you do it the more security you have

Infosec around here works by having people that dont understand technology tell us what to do and if we cant do it those people just tell auditors we do it

@hirojin mostly true. The problem though is the edge cases are different. I agree that most software authors don't take security and privacy seriously enough, but some do, and then you get into the difference that there aren't hundreds of people at each building at any time, trying to figure out how to blow it up.

@hirojin in fact, houses are unbelievably insecure in the details and edge cases (windows? Actually secure locks?), but it usually doesn't matter.

That doesn't mean that I don't agree that much of the software industry keeps forgetting to add doors.

Sign in to participate in the conversation


BE WARNED this instance will absolutely be unstable at times. It will 10000% be used for experimenting with settings and tweaks to Mastodon. So the place may experience outages, not federate reliably with the rest of the world, have posts go missing, or other technical faults. As such it's meant to be a chill, maybe kinda playful place. FOR BREAKING THE SOFTWARE. Time to see what we can do with this thing! Time to ˥∀IƆOS HƆ⊥I˥⅁

the code is here

This instance also has domain level blocks on numerous others, using the block list found here .

followbots from other instances will be blocked. please report them

Some rules

  • Do not engage in harassment of any kind.
  • Racist, sexist and other oppressive slurs will get you suspended, even in non-public conversations.
  • You can post porn and nudity, but you must use the nsfw flag and do not post on the public timeline or you will be silenced (ask around how to make unlisted posts)
  • try to be kind
  • no non-sentient bots until further notice
  • no shit that's illegal in Canada
  • animated gifs should always be marked sensitive/NSFW and identified as animated gifs (for now let's say just putting 'gif' in the text of the toot is sufficient), because they can cause serious problems for people

some guidelines

  • stuff here is impermanent but i still want this to be as safe a space as we can reasonably make it. let's keep common triggers and angry/ranty/grumpy toots behind CWs
  • free speech maximalists can kindly fuck off. there are instances where that is a priority. this is not one of them.
  • all languages are welcome!

the privacy stuff in the 'terms' isn't what it should be, but no time to change it yet. this instance's data will not be sold or traded or whatever.