1. 43
  1.  

  2. 6

    Every attachment/media is cached (or proxied) by the server

    Everyone in the activitypub space seems to forget how hyperlinking media works. Wasting space with caching is not needed 95% of the time, why do all projects insist on doing it, I wonder?

    1. 6

      If a small instance gets boosted by a big instance and a lot of people see it, it can blow through the small instance’s bandwidth.

      That’s not a concern here since it’s a single-user instance, but that introduces a separate concern: if you run a single-user instance, and I send a DM to you with an image and then look at the server logs for when your client fetches the image, I can determine your IP and therefore your rough location.

      Also, space is cheap, and in most cases servers hosting a fedi instance aren’t doing anything else with it anyway.

      1. 4

        Also, space is cheap, and in most cases servers hosting a fedi instance aren’t doing anything else with it anyway.

        Space isn’t that cheap once you get past a few people on an instance. You either need a lot of local space, which not all hosts provide, or to move to S3 compatible storage. And most of the affordable S3 providers have pretty bad reliability.

        1. 2

          Yeah, that’s a fair point.

    2. 4

      Still in early development/I do not recommend to run an instance yet.

      What comparable server would people recommend for real-world use right now?

      1. 8

        I use honk which is written in Go and uses SQLite as its data store

        1. 5

          +1 also. If microblog.pub used SQLite, I might be inclined to give it a go but I have no desire for Mongo (in or out of Docker.)

          1. 3

            Agreed. The reason I looked at honk initially was the relatively easy and painless data store in a world where everyone was using Postgres and Mongo. The fact it’s opinionated as hell and written in Go are just additional benefits

          2. 1

            +1

          3. 2

            Any ActivityPub compatible S2S implementation (big ones are Mastodon and Pleroma; honk is a smaller one) should work with it.

          4. 3

            Looks very promising! I wonder how hard it would be to deploy in production instead of only docker…

            1. 1

              Impressive feature list.

              1. 1

                this looks awesome, good job!