Saturday 29 June 2019

Integromat as an alternative to IFTTT

For the last few years I have made a lot of use of IFTTT for automated web integration between my blogs and Facebook pages. IFTTT is quite good for this and I still use it to this day, with multiple IFTTT accounts as each account can only work with one Facebook page at a time, for example. One issue with IFTTT is that it doesn't have its own Facebook Groups action to post to a Group. Instead you have to use Buffer to do the actual posting. The key issue with Buffer is the free edition only allows you to post to one group. Even if you set up multiple Buffer accounts, only one Facebook connection is allowed between them, so in effect you can only use one Buffer account at a time unless you are prepared to pay the huge sum of $15 per month for multi account support.

I did some digging around and discovered Integromat, which is a complete alternative to IFTTT/Buffer combination. It is set up the same sort of way as IFTTT but incorporates its own Facebook Groups action. It looks it can do most of what IFTTT and Buffer together can do. One thing that is different is it doesn't allow in the free edition for you to schedule posting times - I have Buffer set up to post at two hour intervals so it can take a queue of posts and spread them out with one post every two hours. 

So that looks like a good alternative as the Buffer deliberate cripple to gouge you for $150 a year for their services has stopped me from being able to use Buffer with a second Wordpress blog that has a Facebook group receiving its posts and that means I actually have a backlog of posts that I need to catch up on for that group.

Wednesday 26 June 2019

Privacy concerns about Big Data well-founded

Since I wrote about escaping from Google's walled garden on my Android phone, I have made some effort to further implement this on my desktops as well. Geoffrey A Fowler is a columnist in the Washington Post and he has written a number of articles about these privacy concerns about Google's vast data mining efforts that they are making across a range of platforms. These columns have been carried on Stuff's website and the most recent one, just last week, took a hard look at the Chrome browser.

From my perspective, it's simple: I ditched the Chrome browser after I switched to Linux. It wasn't something I thought about immediately; Chrome is produced for the most common Linux platforms (Debian-based distros in particular) and I actually did use it for a time, but eventually I switched to Firefox, mostly at that time because of Mozilla's reputation for openness and privacy. The Mozilla platform has inspired a much larger community effort in the development of extensions, which offer much more customisation of the browser, and I've long been a fan of Firefox and Thunderbird in particular, although the latter is now developed by an independent community. Generally I have chosen to use Firefox Developer Edition and on each computer that I run it on, it is installed into my user profile (as is Thunderbird), which saves another step when reinstalling Linux.  It took a while before I felt that Firefox was good enough for me to replace Chrome completely but after a couple of false starts, I have stayed with Firefox and haven't looked back. It's only on the R-Pi that I have Chromium because they don't build Firefox for their platform. I hadn't actually thought much about privacy until quite recently, or that the Chrome browser itself could be spying on me, but it makes sense that this is probably what Google is using Chrome for.

Since then, more recently having become aware of Google's practices and having switched my phone off standard Android (especially since it's a Google phone), I have switched to a different search engine in my browser (not Google). DuckDuckGo is an example that I have tested which is nearly as good as Google. I don't know if their reputation is any good. There are others, so I am not sure which is the best choice at the moment, but the issue is that most of them are commercial operations that have to have some interest in what you are putting through their sites and possibly still collecting data in some shape or form. It's interesting that some people claim Apple iOS is a better more private phone / handheld platform. Whilst Apple does take privacy more seriously than Google, they are still a business and there is still plenty of data mining happening on Apple devices. The key issue is that people should be able to completely opt out of having their data mined on any platform, and whilst Apple does give people more options, it's still hard for anyone to really have a free choice and full knowledge to be able to stop this happening on iOS.

The next step after a better browser is to start limiting web site tracking that a lot of sites do. For example Facebook and Google and a lot of other companies have web site trackers that tell them when you access certain sites. Firefox now comes with tracking protection built in, and I recently have set it to the strongest settings, and have noticed almost no impact on what I can do in Firefox. Secondly you may want to look at an ad blocker; I chose to use Adblock Plus. The issue is not that ads are annoying or intrusive, but that they are another way to gather tracking data about the sites you are visiting. There are a small number of sites I've experienced that block you from accessing content because you are using an ad blocker; with a scripting extension that I haven't yet tested, it is possible to block sites from detecting the ad blocker, but the number of sites that work this way is actually quite small (IIRC the Washington Post is one of the few).

Another useful idea is deleting cookies from a site when you close the site. Some news sites use cookies to limit the number of free articles you can view before they start blocking you. The technically astute can always configure the browser (perhaps with an extension) to delete the cookies when you close the site, and stop this particular level of tracking.

Firefox also has Facebook Containers and Multi Account Containers, which are extensions that you can use to manage the ability of different tabs in a browser session to access data from other tabs. Essentially these extensions group together either all Facebook tabs, or other tabs that you choose, into containers that don't have access to the data in other containers. Mostly I have found it useful to be able to log into multiple different Google sessions in the same browser. However for most of the time it is more useful to use separate Firefox user profiles and have a desktop menu shortcut that starts Firefox with each particular user profile in order to access the multiple accounts each in its own browser window. The main point of Facebook containers is to limit Facebook's ability to access the data outside the container (i.e. all the other websites you use) which is another privacy management technique.

It's also very important that you don't use your Facebook or Google (or Wordpress or any other site) credentials to log in to another site, because that gives that site access to your Facebook or Google profile and some of the data in it. Likewise, some apps that you install in Facebook can create this problem. In both types of situations, sites or apps can gather data from Facebook/Google and can even post spam on your Facebook or Google profile.

To finish off here's a few articles from the Stuff site addressing some of these issues.



Tuesday 11 June 2019

Buster moves to RC1

I have put a 240 GB SSD into the computer that I edit the map mosaics on (in Gimp) which gives me 200 GB of swap file space so that large projects can be handled more readily. I have no actual intention of going beyond 100 layers as in the present projects; it will be more of use when I have to open two of these large projects in Gimp at the same time to transfer layers between them.

The SSD came from one of the other computers that I have, which for now has a regular HDD in its place. Eventually this computer will get a new SSD, but at the moment it is not a high priority to spend money on. The old Intel 120 GB SSD from the graphics editing computer went into a laptop that will be specifically streamlined just for a limited subset of the maps, including aerial photos of Canterbury, that will come in handy going to PT advocacy meetings.

I went to the Debian site and downloaded the latest version of Buster and found that the Debian project have moved buster up from alpha5 to rc1, bringing the eventual production release of buster a step closer. In fact, buster's official release should be occurring almost any day, although there is no official announcement from the community as yet. Feature freeze occurred three months ago and probably they are working on getting the bugs down to a specified target level before they will announce the release.

Running the installer showed it is practically the same as previous versions of Debian. At the task selection stage you get a choice of DDE, Gnome, Xfce, KDE Plasma, Cinnamon, MATE, LXDE, LXQt as desktop environments along with the unrelated choices of web server, print server, SSH server and standard system utilities. I always untick DDE and only choose one environment to install but several can be chosen if wanted. As always, the netinst went smoothly, although it is not as streamlined as the Lubuntu installation which has only five configuration steps, principally because it installs LXQt by default and does not allow a root password to be specified, or mirror locations. This caused an issue for me on my last Lubuntu install when a default mirror timed out when attempting to install Qgis and I had to change to a local mirror. DDE (Debian Desktop Environment) is difficult to find out info about and I always untick it. I remember letting it install once and it just seems to be a strange lightweight throwback to something very old like Gnome 2.

After finishing the install, the new installation of Debian Buster / KDE booted smoothly and I then had just some straightforward post install tasks to finish setting up the system which went well also. There was a somewhat odd glitch when the Bios didn't know which disk to boot from the first time rebooting independently post install and I had to change the settings to ensure it would boot from the new SSD. I guess with the change in SSDs it didn't automatically default to the same SATA port, yet the first reboot was able to magically bypass this setting. Since then software reinstallation has proceeded as usual for the system and it will soon be fully functioning again.