Selfhosted

62755 readers

526 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Local Mastodon Instance (thelemmy.club)

submitted 1 day ago by voster99@thelemmy.club to c/selfhosted@lemmy.world

14 comments fedilink hide all child comments

Hi everyone! I’m looking to run a Mastodon instance on a home server, entirely within LAN, without owning a domain. It does not need to interact with other Mastodon instances, but users on the local server should still be able to follow accounts on other Mastodon servers. Local users should also be able to create posts and see each other’s posts on the local instance. I’d appreciate advice from anyone running Mastodon this way at home. Thanks!

you are viewing a single comment's thread
view the rest of the comments

[–] tal@lemmy.today 3 points 1 day ago (1 children)

I don't use Mastodon, but I don't know if it's possible to do this particular combination:

without owning a domain

users on the local server should still be able to follow accounts on other Mastodon servers

Like, a client that supports having accounts on multiple Mastodon servers would work. Then they have a local account, and they have an unrelated account elsewhere on another Mastodon server and follow people using that, so that the "following" has nothing to do with your local server.

But if you want federated behavior, where a user connects to your server and has their account there tell the local Mastodon server to pull down posts from another users somewhere out on another Mastodon server, you might need to have a certificate on your server that other servers recognize as valid, which in practice would mean one signed by a public CA.

I don't know for certain whether this is actually necessary, but I could believe that it is.

[–] ViatorOmnium@piefed.social 4 points 1 day ago

If you go really out of the beaten path, a client that only reads from other instances could use the RSS feed to go around the signed requests.