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.
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.
The only one I’ve seen is the VW “e-up!”.
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.
So you push digital goods to a robust public platform like IPFS and tie decryption to a signed, non-revokable, rights token that you own on a block chain.
What you describe is fundamentally impossible. In order to decrypt something you need a decryption key. Put that on the blockchain and anyone can decrypt it.
Even if you can, pirates would only need to buy a single decryption key and suddenly your movie might as well be freely available to download. Pirates never pay hosting fees because it’s using the same infrastructure as customers and they can’t be taken down because they’re indistinguishable from customers.
Adding blockchain into the mix changes nothing. Whether your digital ownership is stored in their centralized database or a distributed database, they still have control over everything because they’re the ones streaming it to you. They can just as well block your access & block resale.
The only way to actually digitally own something is to have a full DRM-free copy of it (ianal though this still might not be enough to allow resale).
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.
Apple still uses intel chips in all their macs, just not for the CPU. The M1 Macbook for instances uses an Intel JHL8040R thunderbolt 4 chip.
It’s a little complicated. A USB-3 connection must provide higher current 900mA than a USB-2 connection 500mA. As such a USB-3 data connection can charge faster than a USB-2 connection - some people may call this “fast charging”.
However USB-PD (Power Delivery, aka fast charging) was released as part of the USB 3.1 specification, but it does not require a USB-3 data connection and neither does a USB-3 data connection require USB-PD. You can see all the different USB-C modes on Wikipedia as well, where USB-2 and Power Delivery are listed separately: https://en.wikipedia.org/wiki/USB-C#USB-C_receptacle_pin_usage_in_different_modes
If it was free to use then AMD would support it too
They do. There’s thunderbolt motherboards and it’s coming with USB-4 on the new 7000-series mobile chips.
You’d need to collect the condensate, but that would actually work quite well.
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.
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.
🤔