clean_anion

@clean_anion@programming.dev

This is a remote user, information on this page may be incomplete. View at Source ↗

⁨Comment⁩ on ⁨Are hierarchies inherently bad in all aspects? or are there domains where heirarchies are good to have?⁩ ⁨⁨3⁩ ⁨days⁩ ago⁩:
Not all hierarchies are bad. For instance, in a judicial system, there need to be different tiers of courts as otherwise, if courts had universal authority and made conflicting decisions, it would complicate the law more so than it is already.

Similarly, in a large society that needs unity, if people make all decisions, the results would be catastrophic as most people don’t have the time or energy to focus on every mundane decision. In such a case, elected representatives becomes mandatory, creating a hierarchy.

Yet another example is cases where fast decision-making is required (e.g., to respond to an emergency). In such a case, there needs to be a central authority who holds others responsible and coordinates response.

Ultimately, if you consider a hierarchy where accountability is possible i.e. one party may have more power over the second than the second over first but the second still has some power over the first, then it makes accountability possible in hierarchies. Hierarchies are only wrong when the power gap increases, a small power gap is alright provided it doesn’t widen with time.

You could make the argument that a chain of accountability is better (X->Y->Z->X), but even such chains may include hierarchies (i.e. X itself is a hierarchy). Similarly, authority diffused among different people also suffers from potential shifting of blame. Truly neutral relations between different parties are impossible and ultimately, a power difference exists between any two parties, though it may be minute, and this power gap must be acknowledged.

In conclusion, there are a lot of disadvantages of hierarchies but there are some domains where hierarchies are good. There is no system of distribution of power that is without flaws.
⁨Comment⁩ on ⁨How do I install and use Orcaslicer on Tails OS?⁩ ⁨⁨3⁩ ⁨days⁩ ago⁩:
Enable Administrator password on the menu screen, create a persistent storage (if it doesn’t already exist), download the Flatpak file from the website, and run
```
torify flatpak install /path/to/file
flatpak run io.github.softfever.OrcaSlicer
```
Using an AppImage is not a good idea because they have a tendency to give errors if proper software and version are not installed on Tails (on my Tails USB, this was because of GCC) unless you compile your own AppImage. Using Flatpak is better as it allows you to run software on your system even if the versions of GCC etc. are not up to date.

Please keep in mind that I have not confirmed whether this method is secure and would advise that you consider whether this is secure or not depending on your threat model.
⁨Comment⁩ on ⁨France seeks to ban social media for children under 15⁩ ⁨⁨5⁩ ⁨days⁩ ago⁩:

The DKTB is a personal app. It is therefore assumed, that the User will not share it with other people, and that only the User can access and control their personal DKTB. Ultimately, this means that all attestations in a DKTB are expected to pertain to and only be presented by the same User. This is enforced by requiring the user to authenticate using biometry or PIN-code when using the app and only allowing the DKTB application to be installed on one device per user. (from the PDF)

This is a false assumption: PIN codes can be bypassed by sharing them with others. Devices can be faked unless using hardware attestation, which prohibits any modifications to the device which may be undertaken by those interested in rooting or installing a custom OS.

Users can initially acquire a DKTB on their smartphone or tablet via Google Play or the Apple App store. (from the PDF)

This method requires the use of a vanilla, unmodified device, effectively prohibiting modifications to devices that one might wish to alter.