Not sure what you’re expecting that fuse to do when the battery is on fire from crash damage?
Not sure what you’re expecting that fuse to do when the battery is on fire from crash damage?
BEL is alive and well in unicode: https://unicodeplus.com/U+0007
Kinda. IANAL, but here’s my understanding: If you’re explicitly dual-licensing and publish the proprietary license then contributions can be assumed to also follow the same dual licensing. You’d need to be extremely careful with writing the proprietary license though, since your business is now using non-employee proprietary code.
If you write “the copyright holder may choose to allow an entity to use this work”, then you do actually need permission from every contributor. If you write “this work may be copied, modified and redistributed freely by Blah enterprises” now the business cannot be sold without losing access (or possibly have it’s name changed). If you write “Neshura may freely copy, modify and redistribute this” then you can’t be fired or move jobs without the company losing access.
You can also never ever change this license, since every contributor needs to agree. So if a mistake is made when writing it you’re just fucked.
On the other hand with a CLA that transfers copyright ownership you don’t need to dual-license at all since everything already belongs to the business. Much less risky.
Only until you have any other contributor, as you’re then no longer the sole copyright holder. If you still want to work like that you’ll need a CLA.
Distributed ledger data is typically spread across multiple nodes (computational devices) on a P2P network, where each replicates and saves an identical copy of the ledger data and updates itself independently of other nodes. The primary advantage of this distributed processing pattern is the lack of a central authority, which would constitute a single point of failure. When a ledger update transaction is broadcast to the P2P network, each distributed node processes a new update transaction independently, and then collectively all working nodes use a consensus algorithm to determine the correct copy of the updated ledger. Once a consensus has been determined, all the other nodes update themselves with the latest, correct copy of the updated ledger.
From your first link. This does not describe how git functions. Did you actually read the page?
The consensus problem requires agreement among a number of processes (or agents) for a single data value. Some of the processes (agents) may fail or be unreliable in other ways, so consensus protocols must be fault tolerant or resilient. The processes must somehow put forth their candidate values, communicate with one another, and agree on a single consensus value.
From your second this. Again this description does not match with git.
You’re right in that automation is not technically required; you can build a blockchain using git by having people perform the distribution and consensus algorithms themselves. Obviously that doesn’t make git itself a blockchain in the same way it doesn’t make IP a blockchain.
Key word distributed ledger. Git repositories don’t talk to each other except when told to do so by users.
I shouldn’t need to explain why an access key is not a consensus algorithm. Seriously?
Well, I’m saying Circulor is most likely lying about their “blockchain” actually being a blockchain, or that they’ve pointlessly set up extra nodes to perform redundant work in order to avoid technically lying.
Blockchain is completely pointless without 3rd parties being part of the network. It’s like me saying I run a personal social network for just myself.
Git is not a blockchain. There is no distributed ledger; no consensus algorithm.
Polestar uses contracts and audits to ethically source materials, not blockchain. It uses blockchain as a shitty append-only SQL database to (apparently) tell you where the materials came from. Let me quote from Circulor’s website:
data can be fed seamlessly to the blockchain via system integration using RESTful Web Service APIs with security and authentication protocols
So the chain is private and accessible only through a centralized, authenticated REST API. This is a traditional web application. A centralized append-only ledger is not even a blockchain.
There’s a decent chance that’s still the salt lamp.
TLDs are valid in emails, as are IP V6 addresses, so checking for a .
is technically not correct. For example a@b
and a@[IPv6:2001:db8::1]
are both valid email addresses.
Deer had “produced documentary evidence that Wakefield applied for a patent on a single-jab measles vaccine before his campaign against the MMR vaccine, raising questions about his motives”.
He both wanted to sell test kits and have his own vaccine.
My experience with Apple issue reporting is that you’re speaking into a void.
In recent memory I’ve had both a microphone driver bug in Linux and one in macOS with specific hardware. Only one of them was fixed with an update.
For a phone who’s ethos is sustainability buying a 2nd device just for music is antithetical. When my FP3 eventually goes out of support I’ll have to look elsewhere.
AMDGPU is open source: https://github.com/radeonopencompute/rock-kernel-driver/, it’s also upstreamed into Linux. The firmware is a binary blob though.
My issue with automatics is that there’s a lack of control. It’s trying to be smart about changing gears and yet never ends up doing what I want. It’s like the throttle is going over a bad internet connection.
Because there are no gears to switch I don’t have that issue in electric cars, it even feels better than a manual: Smooth torque curve and instant throttle response.
At least it’s transparent and often doesn’t require root, unlike say a debian package.
This is plainly false. Hash collisions aren’t more likely for longer passwords and there’s no guarantee there aren’t collisions for inputs smaller than the hash size. The way secure hashing algorithms avoid collisions is by making them astronomically unlikely and that doesn’t change for longer inputs.
🤔