how should we handle the liability for data integrity and data leaks?
See the discussion in https://freespeech.firedragonstudios.com/web/statuses/106812422161729554
how should we handle the liability for data integrity and data leaks?
By declaring there is no warranty, not even implied when using the service, while we attempt to follow sane logic and store encrypted backups at multiple places etc.
dunno about data leaks, we should have a look at codeberg's or sourcehut's tos perhaps...
By declaring there is no warranty, not even implied when using the service, while we attempt to follow sane logic and store encrypted backups at multiple places etc.
dunno about data leaks, we should have a look at codeberg's or sourcehut's tos perhaps...
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
See the discussion in https://freespeech.firedragonstudios.com/web/statuses/106812422161729554
how should we handle the liability for data integrity and data leaks?
By declaring there is no warranty, not even implied when using the service, while we attempt to follow sane logic and store encrypted backups at multiple places etc.
dunno about data leaks, we should have a look at codeberg's or sourcehut's tos perhaps...