this post was submitted on 22 Sep 2023
173 points (94.4% liked)

Selfhosted

39927 readers
400 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 66 points 1 year ago (21 children)

There hasn’t been a new Git repo launch in almost a decade

Am I the only person annoyed they seem to mistake repositories for forges? It's already annoying when casual users say "git" for "GitHub", but those guys actually want to build a forge, explaining they're going to do better than anyone else. Maybe start by properly using the terms?

[–] FooBarrington 10 points 1 year ago (4 children)

Also plain wrong - Codeberg launched in 2019. Now the question is: did the author just not know better, or is he paid not to know?

[–] [email protected] 12 points 1 year ago (1 children)

Codeberg isn't an entirely new forge. It's just a well-known gitea/forgejo instance. Sourcehut would probably be a better example.

[–] FooBarrington 9 points 1 year ago

Thank you for the correction! Then it's also wrong due to Gitea which launched in 2016.

load more comments (2 replies)
load more comments (18 replies)