Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 30 days old, your post is exempt from this rule as long as you continue to engage in comments.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
This has gotten a ton of votes, and I'm in agreement that new accounts that have only posted about their paid app should be considered spam, and I would say a timed ban (maybe a week?) would be a good start.
Now what about open source vs paid? Devs who made something may just think "oh I should share it on selfhosted!" On their freshly made fediverse account. Does open source get the same treatment? I'd lean toward no, but some of these projects have a paid component as well - paid hosting, or a license upgrade, or whatever.
I think its fine that they want to make some money, and I'm personally more positive toward a hosted option than a paywall, but its a finer point to navigate than just "paid vs open".
That said, I do see a problem with comments on some posts as well - a reply with "spam" and no report is not helpful. The comment itself isnt helpful. A downvote and report is.
So I think a clear and concise set of rules would be helpful, and maybe with a separate list for fully open source and no paid component, open with a paid component, and a fully closed (paid or not, because we all know where the profit comes from in this scenario).
I'd personally lean toward something like an account xx days old to be able to self-promote, and tags for each type of post.
N of one, but:
Edit: @Shadow@lemmy.ca had a comment about Tailscale, it's a prime example of the last bullet.
There is a sticky up with the currently proposed rule.
Paid closed source or f/loss with a paywall requires active (non-advertising) participation.
f/loss that can be hosted and used fully without a paywall (even if they offer their own cloud option, or a donation subscription, whatever) is exempt.
Oh that sounds spot on. Thanks.
Personally I'm fine with paid apps here, lots of people use tailscale for example. I think the larger issue is the drive-by spamming without contributing outside of their own promotion thread.
I like the comment elsewhere in this thread referencing a subreddit that requires X comments over Y days in the community first.