Posts by Roland6 8260 posts • joined 23 Apr 2010
>Then there's the other risks. So there's a miscarriage (not just of justice) and the system might assume a termination.
So the slimeball looks again and finds the woman is a drug user or even a regular cigarette smoker and so initiates proceedings against her for manslaughter...
The question that should be asked of Clue, is why do they need to collect and retain a woman's health data outside of the woman's own device and in a form a third-party (ie. someone other than the woman) can access. I suspect Clue doesn't have a clue.
>If this is an *EU* directive, then why aren't all EU countries up in arms ?
The different members have different ideas about abiding by the law; just like the UK and US when it comes to intervention in other countries such as Iraq.
>Even pre Brexit, the UK seemed to be able to happily ignore EU regulations
The UK government, whilst it disliked many EU regulations, particularly those that impinged upon state surveillance, did implement and follow the agreed directives. Which was a cause of tension within the EU, as the UK obviously leaned on and called out those who's idea of compliance was more akin to lip service...
The EU project is a long-term project, we only need to look at the USA and the recent Dobbs vs Jackson case to see that even after 200+ years the US still have vast differences between states.
>Customer?
"The kitchen that we supplied to the builder of their 4 bed executive box on an estate somewhere."
Unless the customer (house purchaser) placed the order and thus was also instructing the builder, it would seem on what you say the customer (who brought the kitchen) was the builder. Not sure if delivery address, if that of a private individual, on a B2B transaction falls under GDPR.
>"One of the central functions of X is that it works over a network connection, something that Wayland by design does not do"
This is THE deal-breaker for me.
Given when Wayland was being designed, access over a network was pretty normal - web browsers had been around for a decade or so, the absence of a sensible network connection solution does bring into doubt just what were the designers of Wayland thinking.
>I use Zoom on Wayland (Debian 11) and it can record sessions just fine
I would expect Zoom to be able to record sessions just fine - its part of the app, so no privacy issues. The privacy issues arise when you want to do a Screencam recording of the entire desktop and thus all applications running.
So the privacy problems impact Teamviewer and other Remote Desktop style tools.
>I'm not sure about the need for de-duplicating similar chargers. If I have two devices that both need charging
So you don't have and never had two mobile devices, otherwise you would appreciate the problems with charging.
Yes the problem doesn't tend to apply to laptops as we've got used to keeping their cable and power brick in the laptop bag and they are difficult to mistake with a phone charger.
Every night I have at least four mobile devices to be charged: 2x phones (USB-C), 2x ipads (Lightning)
To facilitate correct cable usage for charging (ie. select correct cable for device first time), I've had to standardise both cable colour and length ie. phones use 30cm black cable, ipads 80cm white cable.
Naturally having four devices, it become much simpler to invest in a couple of 5~6 port charging bricks rather than having a 6 or 8 -way multiplug etc.
It was "forced" to put the service out to tender.
What I've not identified the exact circumstances that "forced" the service to be put out to tender in 2014. However, I suspect there was (Conservative) government interference, given the wording of the tender announcement:
"Provision of a service and system to enable the creation of high quality weather forecasts for UK (both national and regional) and global output."
[https://www.government-online.net/bbc-weather-services-weather-production-system/ ]
I suspect the Met Office would have to partner (with MeteoGroup?) to satisfy this requirement (doubt a Conservative government would permit a publicly funded agency to fully compete with (foreign) commercial entities as that just wouldn't be cricket.
Although this raises the question as to who was shortlisted, as suspect the tender was biased towards one company...
However, as MeteoGroup are a customer of the Met Office, the BBC are effectively still using Met Office data for their UK weather forecasts.
It would seem that whilst OVH had video surveillance, they hadn't partnered it with fire/smoke detection software - I wonder if the fire had been drawn to operators, attention earlier whether things might have turned out differently.
What is also not clear (not fully translated the report) is whether the standard procedure was to simply call the fire brigade and evacuate, rather than investigate.
The IP protocol number field is doing just fine - currently routers are really only required to implement IPv4 and IPv6; the protocol number field just permits traffic to be handed to the appropriate IP handler.
It makes sense for QUIC to be a TCP/UDP overlay, as this permits a client to easily use some of the stream orchestration features against systems that don't have native QUIC support. It also means the overlaying application only needs to hand stuff over to QUIC and not be concerned about streaming details. Ie. if QUIC were to be a full transport layer replacing TCP/UDP then the application strictly needs to be able to handle the use and non-use of QUIC.
>QUIC is smartly designed so that intermeditate routers/switches cannot read the packet and cannot make a decision based on a specific bit within the packet
A question has to be asked as to whether QUIC hinders content filtering such as adblockers.
Also whether it can be used by users to give a better response and user experience eg. force a download priority on content: text first, article images second, third-party stuff such as ad's last or never. given Google sees adblockers as a "revenue sinkhole", I suspect QUIC makes content filtering more difficult.
>It looks like transport and smells like transport.
TCP and UDP definitely look and smell like Transport layer protocols, QUIC has the distinct smell of a Session layer protocol, even though it implements features (such as the orchestration of multiple transport sessions/streams) I don't remember reading about in the OSI session layer specifications.
>and it's difficult to justify "Use the OS one on Windows and Linux, and write our own implementation on macOS" especially when there are going to be different bugs in each.
That is why a POSIX style defined API is required, it will also reduce and simply the interop.
It will also mean the QUIC layer will more likely be maintained by systems programmers rather than application programmers...
>It's an interesting subject for debate at what point any of these become sufficiently mature and ubiquitous that it deserves a stack of its own.
If I understand the benefits of QUIC and what is being suggested then we can expect the majority of client applications to have their own QUIC implementations, so looking at my current laptop and what I have running that will be multiple QUIC implementations concurrently in memory:
Chrome, Edge, Firefox, Outlook, Teams, Zoom, Onedrive, Windows native...
There is a lot to be said fo getting the transport layer out of the application and user space and back into the common/spared services OS space. It would help both with application bloat (remember Chrome already includes its own secure DNS service) and with fault finding.
However, for this to happen requires another POSIX style intervention and the definition of a QUIC API. This is not really within the scope of the IETF RFC process. Back in the 1980's X/Open stepped into the breech over Unix API standardisation; somehow I don't see The Open Group (which X/Open morphed into) doing similar now.
If the service is only for users possessing an Xbox Games Pass then it is reasonable to assume the user already has an Xbox and hence is able to directly connect via HDMI.
Although it is not clear whether the Xbox network streaming service adheres to standards or if it uses its own proprietary streaming scheme, hence why the TV needs to implement a bespoke streaming hub.
But wouldn't it be so much better for those 1000 sheets to be delivered as 80 sheets per month in a nice bendy cardboard package (will need to be to fit through the typical letterbox, otherwise left outside in the rain/damp) - just hope HP printers can handle pre-creased paper.
>I do tend to go through periods of heavy print use to non-existent use.
Just hope that your period of "heavy print use" doesn't go over your subscription limit: Your subscription is for 10 sheets a month, so that s what gets delivered every month, obviously you can print more, by going into your account and changing the subscription level, but expect to wait 5+ working days before increased supplied are delivered...
>Also HP's printhead cleaning routine utilises extra ink, that gets sprayed into a little reservoir/pad in the printer
The routine also doesn't actually clean the print head, just the nozzles if you are lucky. Many times it has been necessary - and is now my normal approach - to remove the printhead/cartridge and clean it and the contact pad with alcohol.
What I hate about inkjets is how manufacturers (not just HP) have buried the cleaning pad/reservoir so that it is inaccessible and not removable.
>The article says that community contributions have dropped to nothing.
Not really, its a mature development, which clearly does what it says on the tin.
Is there a stack of really useful essential feature updates/bug fixes that have been outstanding for 3+ years and the project maintainer posting a comment that they don't have time and if anyone wants to step forward...? That is a sign of abandonware.
Well given the basic editor functions haven't changed, the lack of "significant feature development" is to be expected.
However, having recently looked at the MS SwiftKey website, I see significant feature includes such things as the ability to add your own wallpaper...
This concept of "significant feature" goes a long way to explaining why MS have been doing what they have with Windows since they started developing Windows 8.
>Let us also see a universal visible marking scheme to help identify chargers, cables and devices and their capabilities/requirements.
That is something HDMI also needs.
It seems currently vendors only need to clearly mark the box a cable is sold in not the cable itself.
So once out of the box there is no indication on the cable as to which variant it is...
Seen and encountered enough bent connectors, broken ports and cables with the broken tongue in the micro-usb connector ver the years.
The USB port on phones particularly is easily broken due to the connector sticking straight out of the bottom of the phone; usual cause of breakage is using the phone whilst on charge.
>The next step is to make the charger ABSENT.
It always was optional; you just had to chuck it out of the window along with all the stupid packaging after you drove out of the parking lot
20+ years back it got me that my shiny new shop brought phone came in a 'huge' carton, but its couriered replacement (it got dropped) came in a box just big enough for the phone(*) - the network assumed you had a charger that fitted and worked...
(*) I think the replacement Nokia's also didn't come with battery packs...
> I may have to get some of those glasses with magnifiers and led lights so I can read the microscript on the chargers before use!
Well I've found reading the microscript on chargers, laptops(*) etc. is a good test of phone's camera
(*) Don't you love laptop manufacturers who have made the service tag et al practically invisible (eg. Lenovo gloss black microscript on matt black case).
> Unsurprisingly Linux is also dominant on servers since if you are firing up a VPS or dedicated server you tick the Debian/Ubuntu etc box on the datacentre webpage and it is all magically ready for use by the time you can login.
Linux became dominant because of Unix and the massive popularity of the Windows x86 server architecture. Even in the mid 1980's, putting to one side IBM and DEC, it was difficult to purchase workstations and servers that weren't running some variant of Unix.
The ease with which you can fire up a VPS with Linux is very much chicken and egg: Linux is dominant therefore providers will support it, because it is widely supported it is dominant...
>These people are whining because their [potential] customers want to use MS products.
That's what drove the growth in PC's !
Lots of vendors building PC's and dropping a copy of Windows on it, naturally MS supported and encouraged this approach.
What has changed is that MS really wants MS products running on MS cloud with all revenues accruing to MS, hence they aren't being so friendly towards third parties. This really is a continuation of the complaints that started when MS first launched 365 and changed the third-party terms to be a lot less remunerative to the third-party resellers compared to on-prem licencing.
But then this is what happens once businesses become established - their strategy changes from one of leveraging others to increase their market share to locking out third-parties and potential competitors...
Given the way Windows is being developed, I expect they are more likely to remove Swiftkey from W10/W11 due to lack of use and well it's more Apple-like(*)...
I like MS's website [ https://www.microsoft.com/en-us/swiftkey ] not a mention of Swiftkey for Windows...
(*) The continued absence of a swype-like keyboard bundled with iOS is still surprising given Apple's legendary focus with iOS on ease of use and user experience.
Looking back at history, when the wall finally came down, we learnt what Russian computer scientists had been up to, given the export restrictions on western technology.
One of the surprising things discovered was that because they didn't have massive computer power they focused on algorithms, so in many cases their algorithms were far superior to the solutions adopted by those who had simply thrown computing power at it.
So, yes perhaps the Russians will build massively distributed computing platforms (of which a neutral net is just one example...), whilst the platforms might not be very performant, expect their algorithms to manage the platform to be top-notch...
>It'll be longer than 4 years
Well given: Exchange 2013 goes EoL April 2023; and both 2016 & 2019 go EoL Oct 2025 - MS are in urgent need of a supported on-prem product if they wish to retain those customers...
Given the above, it does seem that MS will be offering (£)extended support for Exchange 2019 for 3 years beyond 2025 to permit enterprises to migrate onto the new Exchange on-prem platform (and encourage 2013/2016 users to go to 2019 or cloud - potentially simplifying migration to Exchange '2025'). Obviously, they will need to be making the announcement in the near future so that contracts can be signed etc.
Naturally, there is the additional question - will Exchange '2025' run on Windows Server 2022 given WS2022 goes into Extended support in Oct 2026...
> they want Exchange 2019 on Server 2019
Agree, however, back in March MS were only shipping Exchange 2019 and Server 2022 via their charity scheme and were very clear that Exchange 2019 on WS2022 was, at that time an unsupported combination and were giving no date for the availability of the next release of Exchange that would run on WS2022 etc...
Apologies to those who keep a closer eye on such matters.
However, for those who last looked a couple of months back, there is some good news buried in the release.
For me this gives a client an upgrade path from WS2012/Exch2013 and who still need on-prem Exchange.
Aside: Yes I know there are alternatives, however, I've been unable to locate a business local to the client who would do the install and maintenance...
>what advantage does it offer over the existing currency
Probably the main benefit is to permit innovation in practical everyday digital currency ie. not highly volatile currencies such as bitcoin or other blockchain-based forms of speculation.
Remember if the government/national bank were to officially adopt a digital currency, they would have to get it right, in all the detail, the first time.
The Register - Independent news and views for the tech community. Part of Situation Publishing
Biting the hand that feeds IT © 1998–2022
