The GPL allows you to copy & modify code for your own desires very generously.
The limitations you fear apply if you distribute the code (in source or other forms) or modifications yourself.
794 karma · joined April 11, 2014
The GPL allows you to copy & modify code for your own desires very generously.
The limitations you fear apply if you distribute the code (in source or other forms) or modifications yourself.
In short, give rclone your keys, (small ~/.rclone config file) tell restic to use an rclone backend and add an extra argument when running restic. (See the blog link above, all explained)
There's an open issue for this which doesn't seem to have moved: https://github.com/restic/restic/issues/2134 - it does have a couple of PRs linked on there which implement proper soft-delete.
> ... a certain song (CDPR didn’t say which one) during the game’s “Braindance” sequences might trigger a Digital Millennium Copyright Act strike. That’s even if you’re using the specific in-game setting designed to toggle off copyrighted music for this exact reason.
Really though, how does it work for a business like this? How do you not serve a specific country on the internet? I'm not aware of any technical solution to this - geoip databases simply aren't accurate.
For businesses where most customers pay, perhaps you can gate the site and verify payment details but that plainly doesn't work for the business model we're discussing as most people surely don't pay anything by design? This isn't Netflix?
Edit: The comment I replied to has been edited and originally explained the owner was Canadian but serves US customers and so should abide by US law.
I don't want to claim to agree or disagree, I'm just not sure how to work out what's right.
I guess the simple answer to the GP is "Availability is likely sacrificed", and the clue's in the submission title being all about consistency. I haven't looked too deep into it and am sure there are also still Consistency sacrifices too.
I'm still a little niggled though... "almost certainly not fully partition tolerant at the node level and requires some sort of quorum" - what does this actually mean? I'm confused why you raise the tolerance of a single node to partitions, when the partitions by definition require >1 node?
Whoa hang on! You can't just say you're not tolerant of partitions...
I'm struggling to find the best post on aphyr.com about this but https://aphyr.com/posts/325-comments-on-you-do-it-to is a good one, specifically the line:
"CP and AP are upper bounds: systems can provide C or A during a partition, but might provide neither."
In short, Partitions happen, no matter what. No really, when you have multiple nodes they happen, you must tolerate them. You can't have CA.
Many people refer to it as "relay theft" since historically it's often just a matter of relaying/repeating a signal - there may be no real authentication involved.
Around physical security, I'm often reminded that "locks are for honest thieves".
I found myself rewatching "Hated in the Nation" recently which gave me shivers. Obviously we're not there yet but I feel there's an argument to be made that "targets" lose livelihoods these days, not lives? Somehow I doubt the "twist" will ever come close to reality.
It doesn't work in exactly the same way - you don't by default get a different window per-profile. Instead, tabs get a different colour for each.
There was also a theory that this had already happened.
Recent versions of Android have also improved the permissions model... you can specify what apps (e.g. F-Droid) are allowed to install other apps. You don't need to add a blanket allow forever.
Why? I'm not sure it has ever been a standard and it's certainly not a default implementation for most providers?
HSBC in the UK have a system they call "Voice ID" which claims to authenticate you by your voice: https://www.hsbc.co.uk/ways-to-bank/phone-banking/
I've not enrolled...
My big recommendation is to backup the binary at the same time as your sql backup.
They've got a github sponsors link too FWIW.
At the time, people were (at least) less aware of the password options for zoom calls, so it was easy to hijack meetings knowing only that id if the host wasn't careful.
I don't think you can be faulted for expecting this to have happened again.
Imagine manufacturers having the incentive to issue monthly security updates, else their users get very angry they can't watch Netflix/log into their bank app/use google pay...
For reference, I have an ops background.
It does make a bit of sense. Users can't be trusted not to lose their single token. But rarely is the option to enrol a second u2f key as backup permitted.
I use Homebank[1] which has pretty useful auto-assignment rules. I then have vague categories - think groceries, lunch & dining (e.g. buying lunch is more luxurious than buying lunch and dining is even more extravagant)
Every couple of weeks I import my statements and have a quick look at anything that wasn't auto-assigned - there's usually a couple of things and I add these, based on the merchant name or description, never to worry about again.
I figure this gives me the best of both worlds.
The only reason this small amount of work works for me is that I don't have to pay cash for much. When I do, it's unique enough I remember and categorise it, no biggy. I understand this wouldn't work for most though.
I wouldn't want to lose track of the small things, as they do add up! Keeping the categories loose (and not caring about the difference between coffee and a sandwich) makes it work.
"Look after the pennies and the pounds will look after themselves." as my grandma always says.