
I must remember not to buy Lucozade from Amazon.
16887 publicly visible posts • joined 13 Jun 2009
Sounds like the guy who still owes Nintendo $14m after getting sent to prison. Some judges really do go the extra mile for their corporate overlords.
In the proposed system they will be obliged to access the data on same basis as everyone else, log, request permission, alert the user.
And how would this cost be offset? We all know how Big Tech and PII works - either it gets sold to third parties or third parties pay them to target a campaign based on selection criteria.
The proposed services can be separate from Big Tech main business by law, with data localized per country.
No it can't, see the CLOUD Act.
The consortium itself is about common standards, not to reinvent the wheel.
The consortium itself doesn't exist and shouldn't exist.
That's a very brave proposal, AC. First it concentrates everyone's PII into the Big Tech oligopoly and gives them all the data they need for their advertising business that nobody else has. Second none of the corporations you propose are based in the EU and so they are beholden only by Safe Harbour, Privacy Shield, Privacy Figleaf or whatever it's called this year.
If someone wanted to try and render GDPR worthless and make everyone in the EU more dependent on US cloud, that would probably be the way they would go about it, so this proposal should be stored in the round filing cabinet.
So they should just keep a copy of all generated images and offer a TinEye-like image search to anyone who wants to check if an image they have was generated by OpenAI or close to what was generated. And the same goes for the other ML image generators. It'll be the cost of getting on to the ML image-generation bandwagon.
Despite the vocal minority of web users who lecture the rest of us about Firefox being a "better" browser, the market says otherwise.
It's not a fair market, the others:
1. Bundle their browser with their own OS with no browser choice screen.
2. Making their own OS complain mightily when the their own browser isn't used.
3. Making their own web properties complain mightily or artificially work worse when their own browser isn't used.
4. Paying to bundle their browser in with third party software.
Safari is an absolute albatross - it barely has any redeeming features apart from a bunch of privacy options which are also in Firefox. Nobody in their right mind would proactively choose Safari but it's included by default on Apple devices.
Edge as usual is almost mandatory at work as it plays best with Microsoft's login, some would almost say by design.
Chrome achieved critical mass on desktop by throwing money at antivirus vendors and Adobe and Google aims to keep it that way by making it the browser which works best with Google's websites and Android phones and Chromebooks.
The market is not a level playing field and people's choice of browser has very little to do with Firefox's feature set but how well entrenched corporations and force their browsers onto users.
Bluetooth is great for for data transfer between devices, where you don't need a network at all, and are happy to wait. But MacOS and I-Phones have traditionally been shit at that: I remember when you simply couldn't send files to I-Phones. In fact, I stopped using Bluetooth peripherals with my Macs years ago because the support was so poor: connected to a speaker a couple of metres away, music would invariably cut out after a couple of hours on the Mac, but happily run all day from the phone.
You're blaming the wrong device. Macs could (possibly still can, unless Apple have also hobbled that lately...) send files and Android phones and other PCs can receive them from Macs. It's just the Bluetooth stack on iPhones that had file transfer removed... and it was removed because iOS was forked from MacOS X.
Already done...
Pimiga 4 - The Amiga tribute for Intel or AMD pc, Intel Mac, or RPI4/400
Download link in the description.
The best form factor is the wedge-shaped Pi 400.
"To the best of our knowledge"
If a Starlink is working, someone's paying the subscription for it. It obviously won't be Russia because of sanctions but any other country could be paying the bill and the device itself could be used by Russian forces in occupied Ukraine.
Unless SpaceX is disabling every Starlink inside Ukraine which is not registered as being used by Ukrainian and allied forces, it could be argued he's not doing enough to comply with sanctions.
In a previous life I maintained a Windows 3.1 client and a UNIX document management server. One of the problems was the toolbar in the client looked like it had icons which were drawn by a drunk spider and the toolbar was not configurable, so I set about improving both of those deficiencies. After my changes the icons on the toolbar actually looked somewhat professional but you could go back if you wanted to drunk spider icons and it was configured by the standard (for the time) modal dialog with two lists and buttons for moving options to the other side and changing the order.
Then feedback came back that that users were confused by the new icons and and they didn't know how to get the button order back to the default, even thought there was a reset to default button.
So a few more changes - the old icon set appeared by default and it was locked to the default button order unless an option was changed in the config.ini... which of course for users confused by icons or button order didn't happen... so it was practically all for naught. It still took a few more years of IT experience to bludgeon my expectations down to the right level though.
Who knows, maybe even JetBrains' developers thought their users would love this.
There was nothing to indicate that that address range would be incompatible with the rest of the address space in some way. There was no instructions to block this address range off because it (and only it) might use an incompatible IPv4.1 in the future. "Actually you might want to" is not a good enough reason.
Many routers already treat it the same as the rest of the reserved address space (i.e. let it through and it'll time out if there's nothing at the other end) because their manufacturers can actually read the RFCs and when it does finally get a future use the chances are it'll use the same protocol as the rest of the address space - what possible practical use would there be in making ≈ 16% of the iPv4 address space incompatible? Letting it through means it's cheaper for manufacturers in terms of future updates and least likely to cause them support requests from customers as their equipment works in the way they expected.
If somehow it did turn out to be incompatible then an update would fix that, otherwise treating that address space as unallocated in the same way as other reserved blocks is the right thing to do otherwise you end up with precisely the idiotic situation we have before us today where lots of people need updates to fix something which should have just worked anyway - but they're not going to get them because their equipment is out of support.
I mean, Aadhaar leaks like a sieve and the Unified Payments Interface is used for money laundering...
I think they can be held responsible for mixing up real with fake goods in their own warehouses, for a start. Then after that they can be held responsible for supplying dangerous electrical goods or toys, crappy pwnable IoT shit, or TV sticks which try to hack everything on your LAN about 5 seconds after booting.
No reason why they can't meet the legal minimum that every other shop has to.
People really are leaving Xitter apart from sports fans who maybe are just using it like RSS?
It's not official though, it just mirrors The Register's account on Twitter, which is quite a feat these days considering Elmo setting fire to the API every week.
This Rust project and Carbon both aim to bridge with C/C++ code and not require you to throw everything out and rewrite. Even if Google did want to hedge their bets, the fact that nobody trusts them to not kill projects and they've just thrown money at Rust means that nobody's going to want to spend time learning Carbon, making it's death a self-fullfilling prophecy.