Apologies to my readers, this is not the usual technical post, but something happened that made me not happy, and I just need to explain to my friend why I have disappeared from Facebook.
It all started 15 days ago, when I received a message on Discord from my good friend Hogne Bo Pettersen, asking me if it was something he said that made me unfriend him.
I was flabbergasted, to say the least, because I did not unfriend him, so I went to log on to FB to check what happened.
I could not log in and I saw this
Well, is pretty obvious that this one is NOT my Instagram account. To me looks like a bot attack. Anyway, it seems that the only way to ask to remove the suspension is log on to IG and file a report.
I did that, using my real IG account, but obviously the savy monkeys that manage Meta security and “compliance to the rules” expect me to log on using that su9…. account, because so far they gave me no answer.
I was already considering since some time to leave Facebook, it has its advantages, I love to be able to see what my friends are doing, their pictures, the little or big things that happen in their life and they want to share; on the other hand it was getting worse everyday, about half of the posts were “advertising” or “sponsored” or “we thing you may find this interesting”, which made it difficult to go to the post that really were interesting for ME and not the Meta advertisers
Now they gave me the reason to do it, they threw me out and I do not have the slightest intention of creating another profile and use that crap again.
What did my supposed IG account do to not follow their rules ? Give a bit of explanation? No, huh ? Imagine you get a fine with the motivation “you broke the law”….
I always thought that the people behind Meta “compliance” were a bunch of brainless invertebrates or even less intelligent beings and this is just a confirmation. What can you expect from a company that censor a post with a statue of Milo’s Venus because” it shows a nipple” and then accept to advertise this ?
So, as I already did with Twitter, my last message to Meta is “fuck off”, learn to better manage your users.
My friends that really want to reach me can find me on Discord, though is a completely different way of interaction, or they have my phone number.
I have been asked to give more details about the .taz file that I mentioned in my previous post.
I hope you have read the excellent posts from Martjin and Daniel, where they explain the structure of the tarball.
In my case it is very simple: create on your machine a domino-bin directory e.g. /home/domino-bin, and put there the ontimegc file.
Then go in the /home directory and issue the command : tar cvzf OnTime15.taz domino-bin/
The content of the file is this: # tar -tvf OnTime15.taz drwxr-xr-x root/root 0 2024-10-10 09:02 domino-bin/ -rwxr-xr-x root/root 57352 2024-10-10 09:02 domino-bin/ontimegc
Place the file in the default directory, usually /local/software, and follow the instructions in my previous post.
First of all, a big THANK YOU! to my friend and fellow HCL Ambassador Martijn de Jong . If you don’t know him, he’s one of the gurus for Domino containers, together with Daniel Nashed. Without his invaluable help, my work would not have been possible.
Running Domino in a container is becoming more and more popular in these days. I assume the reader is familiar with the topic, I am not going to explain how to create and run a Domino container. If you want to know more about Domino containers watch the replay of the webinar that Martijn did for OpenNTF and read his presentation
OnTime is included in Domino, starting with Release 14, is a great tool and I encourage my readers to use it, the version included in Domino is free and very powerful. The issue is that Intravision, creates new releases of OnTime faster that HCL creates new releases of Domino, which is obviously understandable. For example the OnTime version included in Domino is 11.1, but the most recent is 11.5. Hence if you want to keep updated your environment, you need to upgrade OnTime.
The upgrade of OnTime is so easy that I am tempted to use the word trivial. Unzip the file you downloaded from their site, and expand it on your local PC where you have Notes installed. Open the installer.nsf database and follow the instructions, i.e. select the language and select if is a first install or an upgrade. That’s it.
On Linux there are a couple of extra steps you have to do 1. Copy the OnTime task for Linux, ‘ontimegc’ from the installation files /ExtraFiles/Tasks to the Domino server program directory. 2. Run as owner or root ‘chmod 755 ontimegc’ (-rwxr-xr-x)
That is OK if you run Domino on Linux native, but what if you run Domino in a container ?
Copying the files in the program directory into the container is easy (again, I assume you are familiar with Docker) and it works, but….. if you stop the container and restart it you will lose the update. Because the updated ontimegc file is not in the base image where you created the container from, so restarting the container will bring you back to 11.1.
There are two ways to solve this, thanks Martijn for pointing me in the right direction, and make the updated file always available in the program directory of Domino:
1) Install the latest version of OnTime as a custom addon when building the image
2) A quick and dirty trick using volumes
Install the latest version of OnTime as a custom addon when building the image
Once you have the taz file you just run this command: ./build.sh -custom-addon=OnTime15.taz#e13658bd364b55cb31196242100db36501724e728eac00fc43aa2d50e4cc7f61 menu In this example OnTime15.taz is the name of the file I created and everything after the # is the SHA256 of the file.
As a result your image will now have the latest version of OnTime and when you run the container it will use it. This way even if you stop and restart the container, it will always use that version.
A quick and dirty trick using volumes
Copy the ontimegc file from the zip file to a location on you machine, e.g. /local/ontime/
I assume that you have used Daniel Nashed startscript to run and configure your server. If this is not the case, then run, clone that repo and use the scripts. One of the scripts is dominoctl, which is used to start and stop Domino and to get to the console. If you run
dominoctl cfg
It will open the config file in edit mode
You should fine something like this inside it : CONTAINER_VOLUMES=”-v /local:/local:z” (it may not have the trailing z:, but that’s only for SELINX so is not a problem is is missing) Change the line to CONTAINER_VOLUMES=”-v /local:/local:z -v /local/ontime/ontimegc:/opt/hcl/notes/lates/linux/ontimegc:z” This means that Domino will use the ontimegc you copied, i.e. the latest version, rather than the one in the original one, the older version.
Save the file and restart the container.
This second method is quicker and has an advantage. When the next release of OnTime becomes available, you just copy the new ontimegc file in the /local/ontime/ directory then restart the container (obviously you will have to use install.nsf to upgrade the databases, but that is not specific to containers)
