I don't believe I'd end up dossing the service as I would be querying the API in the same way their own website and mobile app do.
Considering also I expect my service to be used lightly, my traffic would probably be minimal compared to the their regular one.
But in any case I was thinking about caching/grouping the request to optimize that.
it's just a single site, not many, it's very specific.
what I have used for my purpose is the same REST API that their website (and possibly mobile app) use to pull the availability
this bitcoin theft happened in September 2012, before Ross Ulbricht got arrested (in 2013) so when Silk Road was active and not a Feds' honeypot like you describe.
It's true also for companies where CIOs are going to Gartner events and don't want to appear like the only ones not being "cloud-only" or "cloud-first"
Then you end up with BS like the ones described here
https://www.the-investing-desk.com/cloud-costs-are-in-a-bubb...
where to justify the fact that cloud is much more expensive managers start to throw random numbers vaguely justified just to show that cloud is actually better.
I saw similar things in Corporate world even when choosing a colo/service partner vs doing in-house... managers asking us detailed costs for infra needed (servers, network, licenses etc.) and when you were getting something like 30 in-house vs 100 hosted they just threw some random FTE count to support it to get to 110 vs 100.
I use SwiftKey (but without swipe) on both Android and iPhone.
Now that MS is retiring it I am not sure what I will do when I switch iPhone (fortunately I have just upgraded to 14 a couple of months ago so for few years I should be fine..)
I was working classic full time 40h/week, then took a parental leave for my first newborn that allowed to work 80% (so 32h/week).
Based on the law here, the employer could have denied the 80% but I could have asked 6m totally off and they couldn't have said no. Anyway, they accepted the 80%. This lasted for 20months. I then asked to have another one for my second kid, as no issue arose during the first one and I was productive, it was granted.
Finally, I negotiated to remain at 80% permanently.
wouldn't you be able to do the same even with FK in place?
what FK would prevent you from doing would be deleting a user before all his relationships are removed. That should prevent you to ending up with inconsistent data inside the tables.
That's fine for storing, the problem is that you need the key to sign any tx, so if you just have the paper wallet you need to import it to a computer or mobile device each time you need to do it while if you have an hw device the key never leaves it
There are also tools that allow to take your seed and split it in m subgroups so that you need at least n out of m to rebuild it. So instead of giving password to a single family member (or two relatives, half and half) you can give it to more people and you can still recreate it even if some lose it
Totally agree with you. Even if you have delayed copies, you still need proper backup in place.
They recently implemented long term retention for Azure SQL backups in Azure: https://azure.microsoft.com/en-us/blog/azure-sql-database-no... as it was only allowing 'til 35 days.
I would expect that something similar is provided also for this type of DBs
4-5 years ago I used pfsense as internet gateway and vpn for point to point in an office with probably 20-30users.
We had it clustered between a VM (on ESXi) and a physical appliance on alix (if I recall correctly, or another of the supported sff appliances). The VM was rock solid while the appliance from time to time was experiencing issues (stuck/memory exhausted I think) up to the point that DHCP lease were not released anymore and the office was de facto unable to work.
I think at the end we just kept the VM running alone.