Cryptography nerd

Fediverse accounts;
@Natanael@slrpnk.net (main)
@Natanael@infosec.pub
@Natanael@lemmy.zip

@Natanael_L@mastodon.social

Bluesky: natanael.bsky.social

  • 8 Posts
  • 670 Comments
Joined 3 年前
cake
Cake day: 2023年8月16日

help-circle

  • If you don’t have strong consumer rights enforcement you have to do a lot of research in advance. Even then you can be hit by companies changing model later.

    In B2B, if you’re in charge you need to negotiate in terms to be able to break the contract if the other side don’t deliver what they promised. If you’re just an employee, you can’t do much about your bosses making stupid decisions. They might have thought they would save money, or gotten kickbacks, and you’re stuck with the consequences.

    And yes, dishonest people should be filtered out.







  • The ship of theseus says hello

    You have to decide what it is that defines the entity

    The title of “my gaming PC”? Whatever which holds the title is that PC at any given moment.

    Defined by some property? Desktop setup, game/file collection, hardware type (whichever has the hardware most suitable for the task, eg. the most capable PC being your gaming PC, etc)

    Defined by substance/components? OS image, motherboard / CPU, or even just the case, etc…

    You can even use all definitions at once with completely different choices in each, because your current gaming PC might become your next home server as you buy a new PC, then you move around some components like RAM, reinstall a device, make one a media center for your TV, etc…






  • Wikis benefit more from the ability to mirror them and to link between them than they benefit from full federation. You need much better antispam on a popular wiki than in most other user content systems, and that’s not solvable with just blocklists like in many other federated systems. You need almost all antispam working server side, the user side fixes doesn’t work effectively.

    It would be useful with atproto (bluesky) style portable identity where you could log into other wiki hosts from your own hosts user account to submit stuff (allowing you to maintain a single account in federation through OAuth logins, while still allowing each wiki to be centrally managed) with support for mirroring and native cross-linking between mutually trusting wiki hosts. You could replicate the Wikia/Stack Exchange user experience this way, without all the ads and without any central gatekeepers. (Very similar to stack exchange actually, as each individual Wiki would be read-only to you until you login to it separately (still using one a single account))

    Things like content addressing could allow proper static links that survive page name changes for the cross-linking, etc.


  • There’s things built for entirely different reasons that can be used as a federated Wiki if you wish, like Fossil (a federated version control system with a Wiki)

    https://www2.fossil-scm.org/home/doc/trunk/www/index.wiki

    Note that Wiki federation has a whole bunch of potential issues if you try to allow automatic updates from arbitrary users. Wiki servers rely heavily on antispam measures which often require a lot of analysis of the user’s connection, data which often isn’t available over federation, so submissions by others have to be validated manually. Fossil being a version control system means it is more of a mirroring friendly Wiki than truly federated, but you can set it up so that mutually trusting mirrors can replicate each other’s validated commits/updates.