Welcome
When I first set up this domain the plan was to expose the way that the cooperative nature of 'the cloud' was being destroyed by the increasing isolation of the separate 'cloud computing' islands run by competing commercial organisations. There is a lot of discussion on passing information 'to the Chinese' but that misses the point that we do not know just where all this information is stored. I've been working with the CDDB data to sort out my music collection, and have used this new AI Chat technology to produce Summary of CDDB history which while better than I would have written myself, is not a 'good' summary. It's factually correct, but until I asked about some of the open source options they had not been mentioned initially. In essence it shows the commercial bias that even dumb search engines display.
When asked the question "Where are the computers you run on based?" I got a vanilla "I don't have personal experiences, a physical location, or a specific set of computers that I run on. I am a text-based AI model that operates within a cloud-based infrastructure provided by my developers. This infrastructure is designed to handle user interactions efficiently and securely. The servers and data centres that support my operations are distributed globally to ensure reliability, scalability, and low-latency responses." Which is actually quite accurate, but also misses the point? Today as I got up I did my daily medical checks, blood pressure, pulse, weight and so on, and these measurements were pushed to my mobile phone. Both Google and Samsung keep complaining that I have not 'backed up this data', but their applications do NOT provide a private means of downloading that data, it has to be uploaded to their 'clouds'. That the information needs archiving is correct, but that should be direct to my Doctor's surgery and remain on hardware housed in the UK! I have some information in the NHS app, but it's quite obvious that different parts of the NHS are working with different 'clouds' which do not talk to one another? Some pieces of information have now been updated, but as I understand this has to be done manually between systems. Just as I have to manually copy key measurements into other apps on the phone. Today nothing just works!
So I will sit on my own little island and try and keep the drawgate up on others scraping my personal data. Not that I am doing very well here since the stats report lists some 20 crawlers reading what is posted here. That some of these are intent on hacking the site and are trying to find things like wordpress and other files that may be compromised is just what we have to live with today. It is about time IP-v6 was the default and every address used actually identified to an individual. Anonimity has a place, but not when they are indulging in activity that should be blocked by the 'cloud' as part of it's basic security systems. Just who has created emails should be readily identified by automatically tagging those messages with the origin IP address, and if this is missing then an email can't be forwarded at all. The volume of traffic hitting my own email server which are pure crap is irritating and addressed to non-existent email addresses on my domains. I just throw that traffic away, but I should be able to just bounce it back to the real originating server!
What is next on the TODO list ... Filling in the gaps around just what I do have remaining.
Where is my data today
Desktop configuration is where I am today with the workspace machine and I have the main server documented here.
In addition there is a windows machine and some other networked devices which Equipment Inventory - Up until May 2020 at Smallbrook Road)) - Up until May 2020 at Smallbrook Road|need updating here)).
The history of this page can be found as Old Welcome Page and more recent Welcome Part 2 pages ... The nice thing that bitweaver provides is a complete history of edits to a wiki page ( and I need to add that to blog pages as well now ), but I have had to disable the history view because it confuses crawlers.