A few weeks ago I needed a computer to be a Debian server for some at-home simple Web dev / learning stuff. I bought an HP Prodesk 400 G3 SFF PC with i5-6500, 8GB RAM and a 256GB off a popular auction site for £44. It'll do. I might upgrade to 16GB. An additional 8GB stick costs £19.
Good work. I bought an AMD Ryzen 3 3100 for €35 with shipping. A Radeon W5500 would set me back €150 at the moment. 16 GiB of RAM another €90. And that's on a relatively cheap site in my country.
I daresay you could find the odd example, as for any grid in a stressed situation, but it's not like we turn to each other every week in the dark and say "Oh, it must be half time at the Manchester United match".
I used to support DTP, and graphics for the systems house at which I worked. I travelled round the UK installing PageMaker and A4 paper-white CRT displays - boy were they heavy!
My endearing memory is calling the company in Edinburgh for technical support, to be greeted on the phone by a lady with a lovely, cheery Scottish accent announcing "Aldus UK".
Fun fact: I was first person in the UK to print in colour on an HP ink jet printer at the trade show where they were first demonstrated. The HP folks hadn't got the official colour driver ready for the show, so the HP guys were printing in mono, but I'd had an advanced model to try and hacked some other print driver to work with it.
The Motorola phones are generally good performers and value for money. My only gripe is that they cannot have their batteries replaced easily - even by phone repair shops.
I understand that this is because you have to disassemble / un-glue the phones through the front and remove the display. For this reason, the repair shops I have asked have said they don't 'do' Motorola phones because there's too much risk in breaking the display.
This effectively means that the life of the phone is determined by the ageing of the battery.
That's a disappointing change. I had a Moto G Play a few years ago (the one where you could swap different modules on the back, like a projector and things), and its battery was really easy to replace.
I learned how to do lacing during an electronics engineering apprenticeship in the 1980s.
After the fact, when I moved more in to systems and networking, I found that flat, nylon, waxed lacing cord, with a small nut tied to the end, was lightweight and perfect for throwing through ducting and ceiling spaces very long distances, so you could backhaul cables through the void. It was a real time saver.
LinkedIn - it takes you to the allow/deny page but doesn't automate things. It used to be that the LinkedIn login would get stuck in a cycle around this, but now it just dumps you on to the consent page.
I worked in IT support and engineering for a UK Olivetti dealer / distributor in the 1980s/90s. As such I had access to all sorts of Olivetti kit in various states of functionality. At one time, my home PC was an Olivetti M280 case with an M380 (386DX) motherboard and EGA display adapter. It had a colour monitor and the ANK 27-102 keyboard - it was a 'top end' hybrid for its time that I'd put together from several non-working machines..
I also had a 'faulty' Olivetti inkjet printer that was written off under warranty with a mysterious fault. I eventually managed to fix it by bending the metal paper detector arm so that it slotted properly into the optical sensor - it was a little out of whack and the sensor sometimes couldn't work out whether there was paper in the tray.
I tried this with Node-RED for a Meshtastic project (MeshBop), but experienced occasional timeouts even when only making a handful of calls per hour. In the end I moved to Met Norway's API for UK/EU weather.
reply