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 posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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
So, in thinking about this in more concrete terms (as opposed to vague dissatisfaction), I suspect what we really want is a blogging platform with robust authenticated reader interaction tools.
The issue with AP, and therefore most of these servers, is that (a) it's expected to be public by default (the privacy point you mention), but almost more fundamentally (b) they're aggregators. People either to a bunch of people and get a feed of a bunch of posts by different people (Mastodon/X); or they join a community and see a bunch of posts by different people (Lemmy/Reddit).
I think what we want is blogging software, with an endless stream of content posted by a single user, but with reactions and threaded conversations per post. I've been thinking how this could be achieved on various AP platforms, but while you can almost get there with groups/channels/communities, the sticking point is that they are all ultimately designed around any member being able to post top-level content. I haven't seen any system yet that (easily) allows restricting posting by individual accounts.
I need to look at pump.io clients, because I think pump.io started as more of a blogging protocol. And the more I think about it, the more I believe a private blogo is a better foundational model.
No. In fact, I suspect it may work against the privacy requirement. I expect that, even if one of the federated servers met all of the requirements, federation would have to be disabled to prevent leakage. Although, at least one server supports authenticated pull (one of the Misskey forks), I'm guessing it's not likely that federation will be needed.
For me, no. I want my SIL to be able to easily post pictures and videos of my toddler niece, and all the family members to be able to oooh and aaaah, and react with little heart and exploding brain emojis, and comment on how the fact that she climbed a jungle gym is a sign she's sure to be an Olympic athlete. The parents absolutely do not want those videos showing up in TikTok.
Ideally, it'd support ActivityPub. I'm not sure how; perhaps through the user creating channels and setting a federation flag, or marking it as public. I think the expectation that people will understand that inviting someone from another platform effectively makes all of that content public, might be bit much to assume. So I think having private and public channels, where public channels are federate-able would be fine. But I'd rather not have federation than have a system where people are prone to make privacy mistakes. Is there an option I'm missing?
Yeessss; I think that's a little different, because NextCloud was forked off of the completely open source OwnCloud, which was well-established and license protected long before NextCloud came along. If NextCloud tried any shenanigans, they'd be eviscerated. HumHub is a bespoke solution, right? So they can't be accused of stealing an OpenSource project's s code.
Yeah, this is a good example. I use it, too, although I admit I've considered, and regularly revisit, alternatives purely because of this quasi-free nature. So much of PhotoPrism is built on free libraries; the project uses something like 120 OSS libraries. How much of their income do you think they contribute to those projects who's work their taking advantage of?
I've been using it for two or three years myself; it's always been OSS & free software, AFAIK.
That's a service. I have no issue with charging for a service, because it's an ongoing cost to the hoster.
Actually, I don't have any issue with anyone charging for their software, either; it's just that I won't use it, and I don't trust quasi-free projects. That's just from experience. Most end badly, either by being bought out and going totally commercial, or just slow enshittification for the non-paying customers.
I write software for myself, and give it away free because it costs me nothing to do so. And I've written software libraries that I know, for a fact, are being used as backbone code for a not insignificant chunk of the internet. I've never been paid by any commercial company taking advantage of my work, and have little sympathy for people charging for software that's 90% other people's freely given code. Which is most software today. You write the entire stack from scratch, including the compiler, like Excel once was? Hell yeah, you deserve to charge for it. Otherwise, you're just profiting off other people's work.
Huh. Never heard of them before a week or so ago. I wouldn't completely discount them because of the semi-free model; I just am putting them down on the list.
I think largely we are aligned on what we are looking for in a platform. The private blog idea is interesting. I normally consider blogs as public, are there private blog platforms?
I don't see it like that. OSS is people releasing their work allowing it to be used commercially without limitation (other , it's what they wanted when they picked the licence, or they would have picked a different one.
On the other hand, projects die when the maintainers lose interest. I would like a platform that I know is going to stick around. That's a difficult ask though, if it's a company like HumHub, it's very possible if the company goes under it will just die. On the other hand, something like Zusam, if the maintainer loses interest it will likely also die. It would be nice to have some confidence in the longevity of the platform before diving full steam onto it. But I guess at this point, finding something that works is hard enough, without worrying about that!
I do have reservations about HumHub, but it's the first platform I've seen that even comes close to being a familiar feel for users. I'm considering the other idea of using Dokuwiki as well, which I guess comes in as being more similar to your blogging idea.
Sure. If nothing else, you could proxy it through an authenticated endpoint, requiring people to log on to view it. But I don't know the blogging software space very well - there are probably projects with built-in support for this. I've started looking around; I suspect the ideal platform isn't so much a blogging platform, but it's designed more around a blog design.
If you come across one, please let me know! I'll keep updating that CryptoPad document. I also started a spreadsheet, which is better suited to the data than a document table, but CryptoPad doesn't have the ability to embed assets from other documents (other than images), so I'm just doing the table manually.
Absolutely. Good projects attract multiple maintainers; there's a bit of Darwinism there. When one project I used was archived, I offered to take over maintainership; the author didn't want to hand it over to me, so I hard forked it and worked with distributions to replace the no-longer-maintained version with mine. It's the OSS lifecycle, right? And the best thing about OSS - if the maintained loses interest, someone else can simply take over. And if no-one does, maybe it isn't worth maintaining.
This is so important! Especially for this purpose. Getting several people to join a platform and then put content on it introduces a lot of technical inertia. That's why it's important for me to reduce the odds of the project changing their terms of use; increasing costs; moving popular, free features to the "paid" column; and other shenanigans.
See, I don't believe this. It's possible the project would die, but so often have popular projects lost their maintainers, and new people step in. They fork it, or have a peaceful transition of ownership, but the project carries on. Yes, some just disappear into obscurity, but the popular ones tend to keep going, sometimes under other names. X11 to XOrg; OpenOffice to LibreOffice; OwnCloud to NextCloud; so on and so forth. And increasingly, many projects add data migration paths from other projects, especially if they're popular. Many ActivityPub servers can import Mastodon account data, for instance.
It does look pretty close to ideal for what we've been discussing; I need to install it and try it out, because so far all other options have failed in some way. There's another forest of options in the blogging style, so I'm still optimistic, but I may try HumHub anyway.
Yeah, that was an interesting avenue; I suspect the user client experience will be where that fails for me. It can't require any technical expertise.
With Zusam, I don't think it's got that much of a following yet. I haven't heard of anyone on a self-hosted forum actually using it. Plus current development is slow (last release almost a year ago), so I do think it would die if the dev abandoned it.
I'm thinking that most of the non-technical people would be reading only, so it might be ok.
At this point I'm thinking of setting up a HumHub, a wiki (maybe Dokuwiki), and Zusam, and getting some of my most interested people in as a trial and see which one they prefer.
None of these options have emoji reactions or gifycat integration, though.
The emojis are something everybody in the family loves, and uses a lot. I don't know that it's a complete deal-breaker 🤷♂️
For the wiki option, perhaps the wiki is just where the posts are made then you share the link in a chat app or something. Then the reactions could be in the chat app?
Or for the HumHub or Zusam options, maybe you could add the reactions/gifycat integration. The platforms seem like they would work well with them if someone would just contribute that functionality.