kavin/Yotter
Archived
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
PLUJA 2020-10-07 09:33:21 +02:00 committed by GitHub
parent 409ee410e8
commit d75450cfd5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -65,7 +65,7 @@ If you don't mind exposing your IP making requests to Google then you can set it
#### Your data #### Your data
The only things the database stores are: The only things the database stores are:
* Hash of the password * Salted hash of the password
* Username * Username
* List of followed users * List of followed users
* List of saved posts * List of saved posts
@ -74,7 +74,7 @@ The only things the database stores are:
This data will never be used for any other purpose than offering the service to the user. It's not sent anywhere, never. This data will never be used for any other purpose than offering the service to the user. It's not sent anywhere, never.
#### Security #### Security
Only the hash of your password is stored in the database, so no admin can see your plain-text password ever. Also, no personal information of any kind is required nor kept, if a hacker gets access to the database the only thing they could do would be to follow/unfollow some accounts. So there's no motivation in 'hacking' Yotter. Only the salted hash of your password is stored in the database, so no admin can see or guess your plain-text password ever. Also, no personal information of any kind is required nor kept, if a hacker gets access to the database the only thing they could do would be to follow/unfollow some accounts. So there's no motivation in 'hacking' Yotter.
I always recommend self-hosting, as you will be the only person with access to your data. I always recommend self-hosting, as you will be the only person with access to your data.