view the rest of the comments
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.
-
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!
That's a pretty good idea, actually. I'll try that out. Thanks.
Yes, as @Darkassassin07@lemmy.ca says, just create a new user for each event you want to share photos about: 'BeachBBQ', 'WeekendStay-July' etc, then bind those user accounts to whatever folders you want to have the photos in and set the user restrictions to upload, share, but not delete for example.
I also use various FileBrowser instances, with a different subdomain pointing to them, also as a way to filter out usage as well.
collegefriends.mydomain.comcould take you to a FileBrowser instance that only has access to photos from a certain friend group. Not sure how useful that would be to you, but it's another way of controlling the data flow.I use Immich for that. You just create a shared link and then tick the setting to allow other users to upload.
Won't work for other filetypes though.