Where do I send my bill?
As one of those constantly cold called, I want my compensation.
416 publicly visible posts • joined 17 May 2012
I agree. I see no benefit, other than to reduce banking charges for business. For consumers and the general retain public we already have digital currency. We use every time we tap to pay, either with a card or a phone. We use it when we send money via EFT. Why would we need, or even want, a blockchain backed currency with a separate wallet that we have to manage?
For business, which pays a much high transaction cost than consumers do via high street banks, then there MAY (and I stress the MAY) be some advantages if this reduces banking costs and improves transaction speed. But that is very marginal.
I am assuming that the lawyers have now amassed a large amount of paper, probably several ring binders full per tweep, what with personal statements contracts of employment, severance notices, legal filings.
Can I assume that these are now known as the X-Files? The truth will be out there somewhere.
I'll get me coat. Its the one with the Catatonia CD in the pocket.
That send you an email for something that can easily be done next week, or even next month
And then send you a whatsapp "did you get my email - its been 60 seconds and you haven't responded"
And then calls you to see if you got the WhatsApp?
No, Blair, I am just ignoring you because you are irritating
Exactly this. Years ago, Oracle tried stitching my company up with a £3.5M bill for using a small Oracle database, claiming that everyone who saw, or who could poentially have seen, a printed report from the database was in fact a user, and hence had to be licensed.
After a protacted set of increasingty fractioius arguements we did a corporate transition to DB2. Oracle were told to leave the building.
Sucks to be you, eh Oracle?
If you have your program divided into P and D memory spaces you can avoid all the issues with buffer overruns changing the execution code. P-Space is the only memory space that can be address by the program counter and thus execute instructions and its marked read only as soon as the space is loaded into a process; D-Space is data space. Its read/write (sometime read only) but can't be used to execute commands.
DEC had this right in the 1980's with the VAX/VMS systems. Its all this crappy X286 derivatives that we have to use these days that let us down.
The suggestion on another thread is that he firmware has been corrupted in a way that prevents it from being replaced. I imagine that this means the firmware has been corrupted to (a) Always allow new code to be installed silently, thus contiuing the intrusion, and (b) silently prevents any further update/downgrade/replacement of the firmware.
It has to be something pretty low level to force a full blown replacement of hardware units.
Instead of Halt and catch fire, this is more halt and be incinerated
I ask ChatGPT about Mu-RAM.
Spartacus: tell me about Mu-RAM
I'm sorry, but as of my knowledge cutoff in September 2021, there is no information available about a technology called "Mu-RAM." It's possible that Mu-RAM refers to a term or concept that emerged after my knowledge cutoff, or it may be a lesser-known or specialized topic that is not widely covered in the public domain.
If "Mu-RAM" refers to a specific technology or concept, please provide more context or details so that I can try to assist you further.
Can confirm that when halon goes off it does sound like a small tactical bomb. Especially if you are not expecting it.
Under floor halon globe blew the dress completely off one of our female tape operators and another drove the senior operators chair across the consoles and broke his arm. Unions had hell to pay for this.
No fun was had by anyone that day.
I love the 99.999 % uptime. Thats a downtime of 0.0001% or about 52 minutes a year.
Interestingly I did have one box, a Tandem non-stop server, that absolutely refused to go down. Even when the power went off because the computer room was flooding this box stayed on, serving credit card transactions, storing them up to pass to the customer services Sequent when that finally came back online hours later.
I remember, vaguely, a time when we got X.25 connections. Great for connecting dumb teletype style terminals to your new sparkly minicomputer. All was well, until someone decided to connect a whole network of IBM 3270 terminals remotely over X.25.
There is a a price for the connection and price per packet. Al wel and good if all you are doing is sending a line of data in, with a couple of lines of output back, when the operator is present.
IBM 3270's were not quite like that. The controller used to poll the terminals at very regular intervals: Terminal 1- Anything to send? No. Terminal 2 - Anything to send? No. Terminal 3 .... until it gets to the end of the terminals and repeats. Endlessly. 24 hours a day, 7 days a week, until the BT bill came in and the accountant lit up with an explosive "WTF".
Not my gig, not my problem, but I did laugh.
I worked in a large data centre that was protected by Halon. It was quite the thing at one time. This one had halon globes in the roof and floor voids, Each globe had a pyroelectric charge attached. There was a trickle current through the charge just to show it was connected - any break in the circuit would show up as a fault. To trigger the system in manned hours an alartm would sound and everyone rushed to the exit, to be counted out, and when everyone was confirmed out the system would be fired. Sound good.
Until the control unit failed in the middle of a day and sent a "Fire" voltage down the circuit. The globes expploded whilst people were in the room. One went off under the airvent by the main fram consoles. This knocked the senior operator off his chair, against a rather unforgiving desk and broke his arm. Another went off in teh take room, where by chance, a femail tape operator was changing a 2400' tape. This one simply shredded her dress and left her wearing bra and panties.
As you can expect, the union had a field day, demanded c ompensation, danger money, etc.
At the inquest as to what had happened the scary part was not that the system triggered, but that half the globes actually didn't explode.
Fire icon - well, you know.
I had that at an ofice I worked in. Two rooms in the office, each with its own thermostat, controlled by the HVAC plant in the basement. And it caused endless problems. One room would be boiling, the other like the arctic. The A/C engineer finally got them both balanced. All was fine until someone tweaked one of the thermostats because the temp was wrong. Nothing happened, so she tweaked it a bit more. Then the other team also noticed that their temp was wrong, so adjusted theirs. and the first team goit worse.
It seems that the initial installers had wired the thermostats wrong. Each one was controlling he a/c for the other room.
I worked for a now long-gone telco. One day the marketing and techie types had an away day to come up with new ideas for telephony products that were innovative, liable to earn lots of revenue and upset the major ex-government monopoly. For reference, alcohol was involved.
We came up with a great system: free phone calls. No line rental, no phone charges, just a totally free phone system. But customers would have to opt in to it by complting a fairly detailed life style questionnaire. Each member of a household (except under 16 year olds) would need to complete one, and every member of the household would be given a PIN number. When you want to make a call you have to enter your PIN, The system then plays you a targeted ad. When the ad completes you get your free call. One ad per call.
We were told by a well known advert company we brought in to validate the idea and to make the ads that it was "the most evil, intrusive idea they had ever come across". We all looked rather downcast, but they then said "We just wish we had thought of it".
So, I claim my part in prior art!
EU: "Hey that sofware you released has AI capabilities. It is scanning X, Y and Z and making unwarranted assumptions and deductions. It needs to be licensed un the EU AI Act"
Developer: "No, Its Free Open-source software"
EU: "OK, thats fine, as you were".
So the FOSS community thinks that because its not paid for software it should be outside of any laws? I know its going to be a burden, but then I find it a burden to fulfil the law as well. You know, all that not doing tax evasion, not employing child labour, not being racist or sexist and vodiing modern slavery. I would earn much more, even as a FOSS developer if I could just ignore the laws I don't like. But that is not how the world works. At least, not unless you are part of the wild west, it seems.
I did an audit of a place which processed very sensitive information. The ultra, company critical stuff which, if released to unauthorised parties could bring the company to its knees. And as this was a small country, bring down the government as well.
The computers were all in secure areas. The code was well protected. Password were secure and changed regularly, with decent password policy and no password reuse. The users were in a separate, locked room, with key card access. They even needed their key cards to access their terminals, so going to the loo meant that their screen automatically locked. It all looked great.
Until I went through the control points for a typical job run. The run was securely started. It was properly audited. The processingwas done and saved in secure file sets, and then the results were printed for examination.
Me: "And where do the printouts go"
Senior Operator: "Oh, we put an elastic band around the line printer output and put it in the pidgeon holes outside the print room."
Me: "You mean the open area, in the corridor, where people walk past all the time?"
Senior Operator: "Oh, yes, I can see there is a problem here!"
Next week they ordered a new printer for the secure room!
I wanred a major ship owner about this risk many years ago. I spoke at conferences about the need for rigourous cyber security. Needless to say I ws ignored. Comments like: Just trying to spend more of the companies money; its not necessary - no-one would hack us; No-one even knows about us. much less cares, so we are safe.
I even wrote a movie plot about it (it was a disaster movie, not a romcom!).
This has been an accident waiting to happen. I did hope that following the Maersk hacking incident in 2017 that the industry would sit up and take notice. But no. Easier to pretend it won't happen to you.
DUE DILIGENCE: I worked in shipping for 20 years as a business transformation manager, sitting between the business and the IT team.
I worked for a company that traded with South Africa when it was still very much an apatheid country. I was sitting in my office when one of the men I shared it with said "I think you should get out of the room, now, and get security, the police and the bomb squad" It seemed a strange and rather random thing to say, even for the early 80's. When I inquired as to why, he told me that he had started to open an envelope (this is pre email!) which had wires in it, and what he thought might be a battery.
So, I left, told security, who evacuated that area (note - work must go on, so not the whole building). Police came, and told him to throw it out of the window whilst diving under the desk. They then retreated to a safe distance. None of this covering up with a blast blanket, or a man in an armour suit deciding to cut the red or the yellow wire. Oh no. Just throw the package away and dive under the dek. Well, the desk was an old, heavy oak one that had definitely survived the war!
It did not go off. If it had done, several people walking along the Strand would have needed new underwear.
The lofty ideals behind TradeLens hold true. There is a mess of paperword, where errors cause disruption to supply chains and increase costs. The need to do something here is not dispiuted. But this was not a use case for a blockchain. The actual parts behind TradeLens are a smart contract, which is based on a blockchain, in this case HyperLedger. But it doesn'nt need to be.
The problems that TradeLens faced are multiple. But a couple are easy to point out. This was a closed community where a finite number of players trade with each other. They are all ananonymous, but have a fixed account code / wallet address. Despite thsi being a long string of numbers, it is noit beyond the wit of man, nor a simple computer to work out that if 1234 was TradeCo1 today it will be tomorrow. I know this because I traded with TradeCo1. Now I trade with TradeCo2, whose address is 9875. Oh look I can see that 9875 has a trade with 1234, so I can deduce the TradeCo1 is working with TradeCo2. And because its a shared ledger, everyone can see this. This is a major problem for trading companies who like to keep all their trades secret. So the first problem is that TradeLens ingtroduced too much transparency. It meant that Maersk were perceived as having too much visibility of all the trade chains, and thus gave them a market advantage. That is reason one why it was not widely adopted.
The second is the concept of the distributed ledger itself. To play on the blockchain you need to have a node where your part of the ledger resides. These are computers. Possibly several working together if you want some form of redundancy, and most traders do. These are not just simple applications that you run, backup and forget. You have a ledger that is growing with each trade, even if you don't participate in that trade. It needs management, backup, security, and all the other good things that data centre managers need. But because this is all encrypted, and you con't know all the keys, you can't get under the covers to manage the backups. As this was IBM, it is highly likely that DB/2 was that database. Thats not helpful when your whole company is an Oracle / MYSql / Postgres shop (other databases are also available). So now you have a bit of complex, mission critical computering power in your data centre which you know nothing about.
The solution to this is to outsource the management of your node to, well, TradeLens. They can run and manage your node on your behalf. They will throw up a virtual machine to run this one. What you now have is a network of distributed ledgers runing as a number of virtual machines on a single large computer. Why not save all the problems and just run a large application to do this without all teh blockchain complexity?
The final issue is growth. Adding new nodes to a closed blockchain network is not trivial. Depending on the implementation it often means taking the whole network down and distributing a new set of public keys to all parties. This is a nightmare of key management but with distributed ledgers. So growth was always going to be problematical.
TradeLens is needed. The concept is right. It just doesn't need a blockchain. But then I really don't understand what does need a blockchain unless you need to have that phrase in your buzzword soup.
Mine was about a software contract, for database applications, with a company that will remain nameless. To quote el reg, "Just understand that this firm is a big name in the business IT world. You don’t need to have the powers of a seer to figure this one out." They had quoted us an astronomical price for a new application. I had tried juggling the setup to reduce the end user count, but finally they told me that "this is the price, and no amount of arging will change it. We don't think you have the balls to change supplier".
I had to report this to the executive director of engineering. This guy was from the states and not amused whatsoever. Not one tiny bit. So he instructed me to quietly find an alternative supplier, which I did. Again, no names, but this one might turn you blue. I set up the deal: new hardware (a lot of new hardware) disks, database, consultancy, the whole works. It came in a lot cheaper that the first supplier.
Exec Director had the european VP of the first company in, explained his position, and said we could not afford the price that his team were quoting. VP reiterated the mantra that "You can't change, you have to pay us". So, in hius presence, he called me up and asked if I had the quotes on my desk. I did. He then, on speaker phone, told me to sign them and send them off immediately. All work, not just on this project but all other projects with supplier one was to immediately cease and all project manager instructed to immediately move to supplier two. His final comment to me was to call the press office and have a press release issued to announce that we were terminating all contracts and work with supplier one in favour of supplier two.
He then turned to the VP of sales of supplier one and uttered the words "I don't think we need you anymore, please leave the office immediately". Supplier one was excluded from all further work. The loss was measured in millions.
It was run by a large, internation, computer services team. I prefer not to expose them as my desire to end up on the wrong end of a defamation law suit is pretty low! This was decades ago, in the mid 1990's. And yes, if I recall, it was Customs and Excise. But it wasn't Southend we visited.
I am sure that they are a lot more professional now. This would all have been refreshed as part of Making Tax Digital. I mean, it must be so, mustn't it!
Some timeago I worked for a software development company that had a product to archive data from relational databases. It worked by running a search for candicate records to be archived and then found all the releated data. So, you could archive customers who had not ordered anything for five years, and it would also find all the invoices, payments, shipping, correspondence that related to the customer(s).
As the tech person I always insisted that the client test their scripts on a test sustem before running it on production.
One client proudly proclaimed that they didn't need a test system. Nor a development system. They just ran production. So I asked how they did development of the application and specifically new database tables (etc). The answer was "Oh, Malcolm here just gets on the main console and keys the changes directly in to the database. On production. And if it goes wrong, we are front page news next day. Ha!" We were out of there so fast as I explained to the samesman that no amount of profit was worth the risk that if anything did go wrong we were bound to be the fall guys.
Oh, yes. The system? HMRC's tax computers.
Indeed. I have just finished reading the original programming guides and internal documentation on the Apollo Guidance Computer. The low level hardware instruction set was what we would today call a RISC machine, with highler level operations handled by functions. It had a multi threaded operating system. To make life easier for the application programmers (ie, the ones who designed the guidance and navigation, and how to land on the Moon) they had a virtual machine.
We still have a hell of a lot to learn from these Luminary's (and lets see who gets THAT reference!)
I question why SWIFT are doing this. from the article it's not to move a crypto currency around. I mean, if you have the worlds largest money transfer system already, and it operates electronically, is safe and has all sorts of checks, balances and confirmations, then you have no need of a blockchain backed ponzi scheme.
So, its the smart contracts then. But they are not executing the smart contracts on the chain, they are checking what has been executed elsewhere. So this is just a new form of trade matching system. But as a number of trade matching services will happily explain, you most definitely don't need a block chain for that.
I am very sceptical about blockchain. There is some really neat technology involved, but the use of write once ledgers (had that in the early '90's, and then we could do it in hardware as well!).
But as for a distributed ledger, well, very few people seem to want to adopt this. They want it done on a cloud based service, and then a service provider has a number of end-user ledgers running on different VMs, in err, a central computer system. So, not distributed at all, just replicated.
So, why are Swift doing this? My guess is because there is a very pretty bandwagon and they want to jump on it.
I can imagine a rack of storage devices, not unlike the racks of SCSI drives we used to install in the 90's, with 8 racks, front and back, each with 8 disks in them, giving 128 spinning platters.
Replace these with computational storage devices, each with a high number of GB (if not TB) of storage and their own processor. Now imaging a parallel database that can send a query off to run in all of these simultaneously. Hadoop on steroids with go-faster stripes. Of DB2 (who remembers that) which parallelises easily.
Or more exotic stuff, such as facial recognition, or AI/NLP/Pattern Matching.
Am I alone in thinking that this could be the next game changer in the big iron arena?
25 years after we moved by old house still gets Christmas cards for me. Despite sending out messages to everyone who we knew that we were moving, and following up all cards with a note saying we have moved, including a card with our new address on it.
Eventually I called one lady who kept sending cards to the wrong address: "Oh, I thought you were joking". WHAT When I have been sending you change of address for 1/4 of a century? Thats a new form of stubborn.
I used a box containing a network of Transputers in something called a Computer Surface. We used it to model results from seismic modelling on a Cray. We eventually turned a system running on an IBM 3090 where we generated one image every 3 minutes, to one that generated 30 images per second. It was truly amazing.
It is a shame that no-one really understood it, it was way ahead of its time.
It was an employee training record system, called Training Information Tracking System. Can you see where this is going. I came in late to the project, to take it from a VB6 incarnation to a fully fledged mainstream app on SQL Server. But I was sitting with the team, getting their user stories, when one of the ladies on the desk found a record that wasn't it the database. She went to tell the boss (male) who promptly shouted out "Well get it on your TITS then".
Just as his boss walked by. Big boss WAS NOT AT ALL AMUSED, said so, and asked who was responsible, to which they all looked at me.
That caused me no end of grief with HR getting involved for "my gross profanity" until the IT director had the decency to say I had taken over the project, and it was the now ex-contractor who was responsible.