Severn Trent Water

The complex accounting trick started in March 2017 when a shell company, with no money or assets, called Severn Trent Trimpley was set up as part of the group. Another Severn Trent company called Severn Trent Draycote - which owns the water company - agreed to buy Trimpley for £2.

Trimpley then issued additional shares and Draycote bought them for a staggering £3bn.

No money actually changed hands, however, as Draycote paid Trimpley with a £3bn loan note - effectively an IOU. But, on paper, Trimpley immediately appeared to be worth £3bn because it had the IOU.

Severn Trent Water then acquired 49% of Trimpley - and that investment was valued in the water company’s accounts at £1.47bn. A hugely valuable asset appears to have been created for Severn Trent Water out of thin air.

Panorama discovered the Trimpley investment through the work of retired auditor Stanley Root.

They might be wanting to build a proper desktop with RGB and all the jazz. While the Steam Deck does kick ass when plugged into a keyboard, mouse, and monitor, it’s not quite as impactful as a tower in terms of presence.

I use my Deck with the official dock all the time so I don’t disagree with Dindonmasker’s point that the value of a Deck is tremendous and a great alternative to building a tower.

deleted by creator

Honestly, it’s very likely just Salesforce since that cantankerous, janky beast is so easy to use poorly.

CRM is “customer relationship management” i.e. a system to manage interactions with customers such as tracking calls, marketing emails and collateral, meetings, quoting, support tickets, and more. It tracks the lifecycle/pipeline of a sale from prospecting, lead qualification and solution mapping, demos and meetings, proposals, negotiations and commitment, opportunity win/loss, license generation, onboarding, renewals, and a ridiculously huge number of other things.

It’s not just tracking the numbers but giving you a centralised system that all other business operations can hook into so you’ve a single source of truth about customer state so that various other operations can be triggered.

When you’ve hundreds of sales people, numerous systems, marketing people, support teams, and more all reading and writing to the same CRM system, if that “system” was a spreadsheet, you’d be constantly deadlocking and race conditioning the hell out of it, not to mention how absurdly huge that file would become with all that historical data (since a big part of CRM is also projections and other analyses across all the data you have).

And Ubuntu, no? Wasn’t that the big selling point of Ubuntu back in the day?

In the United Kingdom, people just add a contact to their phone book called “ICE”. You can learn more here.

Good bot

Nice! And MIT too. Perfect; I’ve given it a star now.

I agree. I don’t have the time but someone should point this out to the dev via an issue on GitHub.

So basically don’t use this in anything commercial because the phrase “feel free” is different to legally libre and gratis. I personally wouldn’t touch this until it’s released under a reputable license.

Shame they didn’t use a proper license when publishing.

Reference for the admission?

And it’s made by a Bitwarden developer.

They highlighted it was a bug and said it would be fixed very soon after it was flagged. It was addressed in a matter of days. You can build the server with the /p:DefineConstants=“OSS” flag still and you can build the clients with the bitwarden_license folder deleted again (now they’ve fixed it).

I don’t understand why you’re throwing FUD about this. Building without the Bitwarden Licensed code has been possible for years and those components under that license have been enterprise focused (such as SSO). The client is still GPL and the server is still AGPL.

This has been the way for years.

Cool. They got that sorted nice and quickly.

Edit:

I don’t get why people think they’re suddenly doing stuff under a different license to subvert the open nature of the project. They’ve been totally transparent on what isn’t part of the GPL/AGPL licensed code for years.

SSO, the password health service, organisation auth requests, member access report blah blah have been enterprise features under the Bitwarden License for ages and they architected the projects in a clear and transparent way to build without those features since they added them.

Thank you for the smug response however I did indeed read the article and going from 13 months to 10 days is not a trend but a complete rearchitecture of how certificates are managed.

You have no idea how many orgs have to do this manually as their systems won’t enable it to be automated. Following a KBA once a year is fine for most (yet they still forget and websites break for a few days; this literally happened to NVD of all things a few weeks ago).

This change is a 36x increase in effort with no consideration for those who can’t renew and apply certs programmatically / through automation.

Smells like Apple knows something but can’t say anything. What reason would they want lifespans cut so short other than they know of an attack vector that means more than 10 days isn’t safe?

AFAIK they’re not a CA that sells certs so this can’t be some money making scheme. And they’ll be very aware how unpopular 10 day lifespans would be to services that suck and require manual download and upload every time you renew.

Exactly. Source it from upstream at build time or something so it’s transparent.

You’ve been on vacation for 5+ months?

Also wouldn’t it be best to post this communication in the issue thread?

Given how long this has gone on now, it’d probably be best to inform your community that you’ll be removing BLOBs from the source and for them to be produced during build otherwise this shadow is going to remain.

This was the first time I’ve ever heard of your software and has kind of made me want to steer clear of it.