HackerTrans
TopNewTrendsCommentsPastAskShowJobs

slock83

no profile record

comments

slock83
·4 yıl önce·discuss
Same or better uptime might not be granted, but I've been hosting my instance for quite a bit of time now, and the only downtime I've had were due to my ISP. I'm using vaultwarden too (bitwarden_rs when I first deployed it), and have absolutely no complains whatsoever.

Also, after your device synced with the server at least once, you can still access and export all your passwords, even if the server is down. This is the main selling point for me : even in a disaster scenario, your passwords are "naturally" replicated.

Mine is exposed behind a reverse proxy, with a subdomain != Bitwarden, and a wildcard certificate. Never seen anything weird in the logs since (before, I had a named certificate including subdomain, and I was seeing regular pokes from unknown IPs, so better be on the safe side)

Again, the main bitwarden instance is a huge target. Mine is just a small instance with less than 10 users, which will probably never encounter a targeted attack.
slock83
·4 yıl önce·discuss
I know people who were in that case. Not a fine, the taxes are just updated, and from now on they have to pay for the pool.

As for the dataset, while I don't know for certain in this particular case, we have a rather accurate database of constructions in France, that could have been used (it's publicly accessible, actually that's what OpenStreetMaps used for the building footprints here), and include pools. We also have "BDOrtho", a public database of aerial photography.

These data can be seen at https://www.geoportail.gouv.fr/carte