BEL is alive and well in unicode: https://unicodeplus.com/U+0007
BEL is alive and well in unicode: https://unicodeplus.com/U+0007
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.
Oh I’m sure they can justify spending the time porting the game. I just can’t blame them for not doing so when Apple’s policy is to not give a shit.
Yes, but it’s highly unlikely they can reuse that effort. TF2 uses an older version of source, so you either end up having to update everything to a newer version or redo all the effort you’ve already put in to porting source, but for an older version. Now multiply that by the number of source games.
I can see how you might come to that conclusion, but porting to 64bit is way more involved than it may seem. x86-64 is different enough to x86 that you’re basically porting to a new architecture: all your assembly will break just like it would porting to arm. On top of that all your sizes have changed and caused all sorts of bugs, for instance: long
is 4 bytes under 32 bit on all platforms, but it’s 8 bytes on macOS & Linux and 4 bytes on Windows under 64 bit.
It’s mind boggling that Apple would drop 32bit support. Adding 64 bit support can be a lot of effort, especially on older code bases, and there’s a whole bunch of games that’ll never receive updates again. You could’ve had arm32 support, with the ability to run any x86 games.
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.
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.
Not sure what you’re expecting that fuse to do when the battery is on fire from crash damage?