• 2 Posts
  • 32 Comments
Joined 1 year ago
cake
Cake day: August 6th, 2023

help-circle
  • Hi, I am a building a platform with the goal of supporting apps like this, and I would be interested to develop a plugin for your use-case as an experiment (no fee).

    I am working alone on this and this is not my first priority, so I cannot make any guarantees about the timeline, or the scope of the plugin. But, if you are interested we can have a chat on matrix.

    The project is not open source yet, but I am planning on doing so once (a) I figure out how to properly apply licensing, and (b) remove any potentially critical information (credentials) from the repository.




  • Dopamine received, initiating hyperfocus protocol!

    As a rule of thumb, we’ve observed that a team of 5 trained moderators appears to provide ample coverage and redundancy for servers of about 1,000 active users

    That’s a fascinating bit of information. I would expect 5 moderators to provide coverage for more users. I am wondering how they came up with that statistic (will update the comment if I find an answer).

    Remember that offliine/IRL community management experience can be just as important as online experience

    Interesting idea, wondering what’s the IRL presence of the fediverse…

    If you’re building toward participatory or democratic governance, consider establishing a proposal and voting system (some teams we spoke with use Loomio, but multiple options exist) for major policy decisions.

    That’s soooo important, I love when communities create polls to decide on policy changes.

    Avoid promoting brand-new members unless you already have a pre-existing relationship with them

    I have followed some discussion on multi-level hierarchies on the fediverse, wondering if there are any instance implementing that…

    Consider charging for accounts or offering paid memberships.

    Hell no!

    We hope there will be more resources available in the future, particularly tooling around legal compliance. This is one of the big infrastructural gaps we point out in our main report

    That’s a big issue, I would be interested in hosting an instance available to other people, but I don’t want to end up in jail and I lack the resources to make sure that won’t happen…

    That was an interesting read, it seems there is an in-depth analysis of the report here.









  • Me neither buddy, me neither…

    Falsehoods About Time: … Time always moves forwards.

    I had to learn this the hard way… I was working at a platform that pulled measurements from sensors. The sensors did not declare the timezone for the timestamps of the measurement and the platform broke down twice after daylight saving. The first time there were duplicated records which caused conflicts and the second one we weren’t handling impossible timestamps.





  • twelve factor app

    Great resource!

    Write database migrations in both directions so people can downgrade on failures.

    Good point. Personally, I take backups before upgrades and restore if anything goes wrong. But, I understand how downgrading sometimes is just easier.

    I have trouble coming up with a migration procedure that makes sense to me. I have the following in mind:

    1. Provide init scripts that produce a schema that matches beginning state of the current major.
    2. Provide major to major migration scripts.
    3. For every major, provide minor to minor migration scripts.
    4. Schema changes require at least a minor release.

    Make it possible to configure your system via ENV variables, ENV files and config files.

    I am bit worried about this one, environment variables can be a security concern. Specifically, I am not sure if I should allow providing secrets (like db connection strings) through environment variables. I am inclined to let people do what they want to, but issue a warning.

    Make it possible to disable authentication to add Authelia or LDAP through the webserver. Make clear that this is only to be used for external authentication.

    I am considering adding support for oauth through keycloak. My assumption is that if you are going to host your own LDAP, you can probably configure keycloak too. Do you think that makes sense?

    Make it possible to run multiple parallel instances of your software without affecting the database consistency, e.g. for high availability or horizontal scaling.

    Ideally, an instance shouldn’t be big enough to need it. I know, famous last words, but in my case I think it’s a bad problem to have. I am going out of scope, but I am wondering where is the line between discouraging large scale deployments and designing something pre-destined to obscurity.

    Telemetry

    Not even on my radar, thanks for bringing it into my attention 🙏