this post was submitted on 18 Jun 2023
6 points (100.0% liked)

Selfhosting

201 readers
1 users here now

All things selfhosting and homelab related Resources: - https://github.com/awesome-selfhosted/awesome-selfhosted - https://github.com/awesome-foss/awesome-sysadmin

founded 2 years ago
 

I'd like to be the owner of my own data. I don't know if my data at kbin.social is available for download or something.

top 6 comments
sorted by: hot top controversial new old
[–] mwlczk 4 points 2 years ago

I second @vtez44, You would only host Your own private profile data - like password. Whenever You post to an other instance, then your post (data + username) is being shared to that instance - it does not matter if you connect via your own instance or not. There is only little advantage.

[–] [email protected] 4 points 2 years ago

Not unless you plan on blocking federation entirely. Once your data goes out to the Fediverse it's there forever.

[–] [email protected] 3 points 2 years ago (1 children)

The data instance really has is your browser info, IP and clicks. Posts are on all federated instances. That's for every site out there, and kbin doesn't have (I hope) business to sell this data to anyone.

[–] [email protected] 1 points 2 years ago* (last edited 2 years ago) (1 children)

hi, if If an admin closes my account, I lose my data? can I recover my account in other instance?

[–] [email protected] 1 points 2 years ago

The posts are public and on all instances, but profile is only on one instance. There is no way to log in back. Would be cool if you could sign with PGP or Metamask, so you can use any instance with one profile.

[–] [email protected] 1 points 2 years ago

If you already have a VPS, or are already hosting services locally in your home, you should spin up and instance for no other reason than to intuit the edge cases for the space. It's super informative.

It's just a little bit of a pain to get set up if you're not already familiar with the bits and bobs needed to do it.

load more comments
view more: next ›