Cryptography nerd
No, that’s also not how it works. Reverse engineering and making a profit from your clone is legal. Breaking DRM for compatibility reasons is in fact exempted and legal too. Nintendos argument is that they broke DRM for piracy, but the tools can still be legal and legal precedence supports that
Very few of those are legally problematic, pretty much just the imagery, possibly GPL issues (but Nintendo wouldn’t have standing for those), and due to copyright weirdness 3rd party online services for games which still have active online services (it shouldn’t be, but that’s how it’s been interpreted)
Not enough for Nintendo to be able to force the project to stop, but they didn’t want to fight it in court I assume
Not really.
Since handles are domain names (and your own DNS entry points to your account public key, DID) they have a referral deal with a registrar to let people easily get a custom domain and set it as a handle (otherwise your handle is a subdomain on the bluesky domain). But future plans are uncertain
As said many times before, Jack is now AWOL and left for nostr, he even deleted his bluesky account because the crowd didn’t like him there. He doesn’t have a majority on the board and don’t own any majority stake either.
The motivation for a new protocol is there’s architectural limits to activitypub. It’s essentially email over http, it really behaves like public mailing list archives, as servers push each interaction as a message. This is part of why there’s often a discrepancy between visible replies across servers because retries are limited. Account portability is also very limited as accounts and posts are tied to a server.
Bluesky switches to a content addressing model plus user ID based on a public key, allowing you to more easily move across servers as well as syncing data between servers such as thread replies, it’s very much like git (user data is held in personal repositories signed by your key) with a shared CDN/cache (relay servers, previously called BGS) and “worker agents” (mostly driven by the “appview” which is the api endpoint for your client + feed generator servers). You post to your repository via your appview, it sends a ping to other servers and they sync new relevant entries.
They already have federation with 3rd parties in a sandbox network and the official server just switched on “internal federation” (used to be a single shared server, now there’s 10 using the same protocol that open federation will later use)
The code is already open source, several servers in the sandbox is 3rd party reimplementations
FYI the bluesky protocol is open and there’s plans to standardize. It’s also federated (the sandbox network is open to 3rd parties)
There’s lots of new privacy techniques from cryptography, stuff like differential privacy and MPC could help a lot with making it easier and safer to use collaboration tools.
XKCD has the prototype
My Sonys can’t be used with Bluetooth when charging but you can use 3.5 mm audio input so they act like wired when charging. Probably because they’re using a fairly standard Bluetooth chipset which also controls charging
I know plenty of headphones that can’t be used while charging, but that’s often because it would be inconvenient to use simultaneously
If you want to support a lot of devices in a dense apartment building with wifi you pretty much want everybody to have MU-MIMO capable access points and IoT gear. Otherwise you’re hogging spectrum.
(It’s not like other protocols aren’t also affected, but at least they don’t compete with people’s internet traffic)
The link says no such thing, it only says nobody else is marketing another such algorithm, yet.
“AirPods Pro (2nd generation) with MagSafe Charging Case (USB‑C) will enable Lossless Audio with ultra-low latency to deliver the perfect true wireless solution with Apple Vision Pro.2 The H2 chip in the latest AirPods Pro and Apple Vision Pro, combined with a groundbreaking wireless audio protocol, unlocks powerful 20-bit, 48 kHz Lossless Audio with a massive reduction in audio latency.”
“Qualcomm Technologies International, Ltd. today continued to demonstrate its vision and leadership in the wireless audio space with the introduction of Qualcomm® aptX™ Lossless audio technology to its already extensive audio portfolio. aptX Lossless is a new capability of the proven aptX Adaptive technology and a new feature of Snapdragon Sound™ Technology that is designed to deliver CD quality 16-bit 44.1kHz lossless audio quality over Bluetooth® wireless technology.”
The descriptions do not match
Are you trolling you absolutely nutjob, OF COURSE if Apple uses a different thing which is not patented because the patent owner DID NOT invent that COMPLETELY DIFFERENT thing then Apple don’t have to pay for patent licensing fees for a thing THEY DON’T USE
And as I’ve explained so many times that you have to be illiterate to not have understood the point, Qualcomm is not the only company with a lossless algorithm and bluetooth itself doesn’t limit your algorithm choices
So what? Qualcomm owns the Qualcomm codec patent. Old news.
However, Bluetooth explicitly allows you to add support for custom codecs on both ends, so Apple can ignore the existence of the Qualcomm codec and use their own.
Sony is literally already doing that in both their smartphones and headphones with LDAC
Apple has AAC
Unless the contract they signed says otherwise, there’s nothing stopping you from swapping out bits and pieces even when you have a license for a collection of patents like for bluetooth components. Sony does it!
You can use custom codecs if you control both sender and receiver, and they have their own lossless codec as well.
The Steam Deck uses the same architectures by the way, with different core counts and a few more differences in capabilities
It definitely sounds like he has redundant routes (this literally shouldn’t be possible otherwise) so yeah, he needs to fix priority
Can this thing run complied WASM? Because compilers to WASM from other languages exists already
After a month from what I read, most distro hadn’t included it yet
Edit: it had been prepped for 2 years or so and the malicious code was introduced a while ago, but from release it took about a month to detection