this post was submitted on 05 Nov 2023
134 points (92.4% liked)
Asklemmy
44151 readers
2350 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You have a product that needs to be sold just as much as google needed to sell gmail. This is where the technical rubber meets the social road. It is a given that not everyone will want to host their services, so to get the network effect people need to use your instance.
With that in mind, first and foremost you should treat your services you host almost like a product: you do need to sell it, it needs to be maintained it, and if other people get onboard you can’t just get bored of it and put it down. Your product is niche and competes with the largest corporate entities out there, but you have the advantage that you can genuinely personally know your customers and your customers can personally and genuinely know you.
I spend considerable thought on this, unless you are talking about household members or other people who trust you borderline absolutely, there is just no way to get a stranger or acquaintance to meaningfully use your hosted services.
For the stuff i host that i can share from my hosted services i make it apparent to the users that the data is subject to my whims. think this helps a little as it puts the otherwise unstated in the open, it would be awkward for a friend to have to ask me how safe their data is, i can acknowledge their data is as safe as their relationship with me is, and honestly that’s the best that can be done without structuring.
Now structuring: if you genuinely want members of your communities to be able to buy in, become consistent and stable with your services operations, a d make a legal entity. Use the entity to provide what you have as a service to have the legal structures in place to protect you and your users. If you think this is bullshit, i don’t recommend because i think the structures will protect anything, i recommend because the structures indicate trustworthiness to the type of people who don’t make themselves concerned with matters they are instructed to not bother with. You would be able to make an appeal to a more personal business relationship.
Now that highlights the effort, as the privacy advocate i functionally have to operate a business to maintain my digital infrastructure; if i want others to join my network i should commit and run a privacy-centric business. There is opportunity here for standard operational models to be documented so that power users can quickly bootstrap and present an adoptable platform to their communities; however, i am not there yet myself.