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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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
You can probably do it, but I'm not sure how many users you'd get, as I think that it'd be a less-usable interface.
You'd need some way to handle voting; that doesn't intrinsically show up. Maybe you could do it via expecting users to send specially-structured emails.
If by "fediverse" you specifically are talking about the Threadiverse
Lemmy, Piefed, and Mbin
then you're going to have to also deal with a lack of a way to handle responding to a given comment (unless you intend to forward all comments to all posts that a user has subscribed to to an email address, and then just only let them respond to those).
Email isn't natively encrypted, so if that's a concern and you want to deal with that, you'd need something like a PGP key that users could register, I guess.
Email clients don't, as far as I know
I haven't gone looking
natively have Markdown support, so either you need to throw out formatting or have some sort of mapping to and from Markdown to HTML. I don't know if something like pandoc would be sufficient for that.
If what you want is to take advantage of existing native clients, my suggestion is that you'd probably get more mileage out of doing a bidirectional Usenet-to-Threadiverse gateway than an email-to-Threadiverse gateway. That has a much closer mapping in terms of functionality than email. You could do that a lot more efficiently in terms of bandwidth. Your "Usenet group list" would be a set of community@instance name entries, and you map posts to top level messages, and comments to responses to those.
The major downside there is that I don't think that any Usenet clients have native Markdown support and you still don't have voting or native reporting functionality.
The only obvious benefit I can think of from either Usenet or email is that there are clients for both that support offline functionality, and I don't know of any Threadiverse-native clients that do. I think the major point I'd raise would be "you could probably do it, but...what do you gain that outweighs the drawbacks?" Like, I think that you'd probably get more good out of just picking your favorite native Threadiverse client and adding code to that (or starting a new one, if you absolutely can't stand any of the existing ones).