this post was submitted on 29 Jan 2025
73 points (96.2% liked)

Selfhosted

41554 readers
473 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] peregus@lemmy.world 6 points 21 hours ago (1 children)

How does it compare to NTFY?

[–] JustEnoughDucks@feddit.nl 2 points 4 hours ago* (last edited 4 hours ago)

Different philosophy.

Ntfy uses pub-sub like MQTT. It publishes messages and anyone (with access) can subscribe to it. Want to connect 250 clients across 50 people to have the same messages delivered? Easy.

Gotify uses end to end messaging. A user creates an application on their chosen client. Gotify uses a REST api send the notification pulled from the chosen app to the user who made it. Want to do the same as above? You have to set it up 250 times. Gotify was the first to have authentication and some people say it is more robust, but I can't speak on that. Also gotify is easier to set up and makes sense for a single user.

Someone can correct me if I am wrong, but that is the biggest architectural difference.