Hazelnoot [she/her]

Transfem demigirl with an interest in coding, gaming, and retrocomputing.

My links:

  • 0 Posts
  • 72 Comments
Joined 3 years ago
cake
Cake day: June 2nd, 2023

help-circle

  • Ethics and rights aside, this isn’t even possible to comply with. The law applies to additive and subtractive manufacturing hardware, and expects it to automatically detect and refuse any attempts to manufacture a firearm. But that depends on an underlying assumption that a machine can answer the question “will this command (set) result in the construction of a gun?” And that assumption is false.

    Even if you somehow designed an algorithm that could read a G-code program and determine whether it produces something shaped like a gun, it still wouldn’t be enough - because the CNC machine is just one step of a manufacturing process. The human operator controls what materials and commands go into the machine, so they also have full control over all inputs that the “oversight” program is allowed to see.

    Some simple ways to bypass this (hypothetical and perfect implementation):

    • Print the gun in two pieces, then combine them manually.
    • Print something that contains a gun, then cut out all the non-gun material.
    • Use multiple separate machines for different parts of the gun.
    • Design something that looks nothing like any existing gun, but is still capable of firing a bullet.
    • Print most of a gun, the build the rest by hand.
    • Build part of a gun, then print the rest onto the hand-made parts.
    • Print part of a gun, then run a separate program to print the rest onto the previous result.
    • A thousand variants of the above.

    So even if this was something we wanted to enforce, it’s just not possible. For the same reason why Minecraft abandoned their plans for an SMP “penis detector”, this law could never be complied with because it’s impossible to build a machine that actually meets the requirements.













  • Disclaimer: I administrate multiple Sharkey instances and am one of the project maintainers, so I’m likely quite biased. Please take my opinions with a grain of salt!

    1. I’ve used Mastodon, Akkoma, and various Misskey forks (Calckey, FireFish, and now Sharkey). The former felt very much like a corporate platform, complete with the “polished feel” you’d expect. Someone unfamiliar could easily mistake it for Twitter. Akkoma is quite the opposite - it feels like an indie software hosting forgotten subcultures in a quiet corner of the internet. Misskey-based software is somewhere in the middle, and feels more like an MMO than a social network sometimes.
    2. Mastodon moderation is clearly geared towards structured and (semi-)professional moderation teams. The mod tooling supports coordination between multiple moderators and records detailed audit logs for quick catch-up on a particular user’s history of staff interactions. Akkoma, again, feels like moderating a classic PHP forum backend. The tooling options are either high-level and barebones, or low-level but extremely powerful. Misskey forks vary, a lot. Vanilla Misskey has relatively poor moderation support, and is clearly meant for communities with a fairly “hands-off” approach. Calckey/FireFish improve this somewhat, and Sharkey has put moderation as a key focus with support for granular restrictions beyond just “silence or suspend”. Community wise, I feel that Mastodon users tend to over-report, and Mastodon admins under-moderate. Akkoma users rarely report anything, but admins set up intricate MRF rules to enforce detailed restrictions and limits. Misskey users report about as much as Mastodon users, while admins often over-moderate and jump directly to instance-level restrictions in response to minor user-level issues.
    3. I do, at least in general. The quality of moderation on fedi is a mixed bag. A few instances do very well, some do well enough, and many more just moderate the bare minimum or not at all. I regularly see users complain of harassment from sources that have been known for years. No qualified moderation team should allow federation with poa.st, for example, and yet many do. But Beehaw’s staff have shown a commitment to their roles, and the community has consistently backed them up with reliable reporting and a solid effort to maintain the community health. I think our people could do very well in the larger fediverse space.