apple.news/AvegtnPV2RvuCb0o16NiQkw
UK contact
apple.news/AvegtnPV2RvuCb0o16NiQkw
UK contact
A tweet was recently posted featuring an advert claiming Firefox is the better browser in terms of respect for privacy:
Shots firedfox pic.twitter.com/yaKS2hwOyS
— Kit (@meatcomputer) July 2, 2017
Sadly, this isn’t the case, as this Pale Moon update clearly describes:
https://forum.palemoon.org/viewtopic.php?t=16154&p=117375#p117375
So, if you use #Firefox, best to expect information leakage back to #Google anyway. If you value your privacy and want a functional browser, check out Pale Moon!
https://arstechnica.co.uk/information-technology/2017/02/google-brain-super-resolution-zoom-enhance/
Neat article on Google’s AI efforts to restore detail into pixelated or low-res images.
Nice video share, too 🙂
I’m just pondering a year without #Google; how challenging it would be to live without any G-services.
A warning about thinking twice before relying on megacorp cloud providers:
http://www.vox.com/2016/7/30/12303070/dennis-cooper-blog-deleted-google
Is it me… or is there an inordinate number of Google ads – I mean "posts", in the stream currently? Wow.
[ This is a retrospective publication ]
It takes heroes like Edward Snowden to reveal how malicious governments can become. The Snowden revelations during the summer of 2013 showed that not only does everyone have to be wary of internet-based “threats”, but that those threats could be in the form of legally-appointed agencies seeking to catch out anyone who accidentally clicks something they shouldn’t.
Worryingly, despite the big players’ assurances of high levels of security, a post on Ars Technica discusses (and links to) slides created by the NSA, and leaked by Snowden, showing how Google’s international internet traffic was intercepted, analysed and understood – for a variety of its services. Thankfully, more heroes have recently stepped forwards with updates of their own.
My heroes today are +Brandon Downey and +Mike Hearn, who have voiced their contempt for the authoritarian misuse of power with, as we like to call it, the two-fingered salute (this would be one finger in the US…).
Google, too, has a data-collection objective
Let us not forget who Google is and what it does. Yes, while its employees might be upset that their systems’ security has been brought into question, their employer’s mission “is to organize the world’s information and make it universally accessible and useful”. So Google, too, has a data-collection objective.
The good thing about the Snowden revelations, if indeed any of them can be “good”, is that it has revealed how much work still needs to be done and how much we assume our data won’t be intercepted and inspected. It’s no longer safe to think like that, and the use of encryption should be mandatory between two end-points.
But now that the larger players are catching up with better security implementations, who is there to help the smaller players? Running a hosting outfit myself, I know how much time is required to stay informed with regards to common exploits and vulnerabilities, as well as implementing working solutions when certain zero-day exploits are revealed. Every internet service provider, hosting company and other entity transacting business via the internet has a responsibility towards safeguarding confidential data. How many take it seriously enough?
It’s time the larger players stepped up and started working collectively in a security community designed to help the smaller players in the market, rather than try to pwn the market itself; if that were to happen, the purpose of the internet would be destroyed and the argument moot.
This post has a new edition.
Part #1 of the Data Liberation series
Although Google Chrome is a very fast browser, it lacks one key feature which seems designed to lock users in – any account migration facilities to support moving to other browsers. This post is intended to help you move your saved passwords from Chrome to Firefox.
Firstly, you’ll need to have a read of this page: http://blog.catoblepa.org/2012/08/linux-how-to-export-google-chrome_28.html – then come back here for more info!
While following the instructions in that post, take note of these steps below before you close your browser. If you have also set up a separate encryption password for your browser, don’t worry – this method still allows access.
In Chrome settings, as a precation, I disconnected my Google account before closing the browser. Therefore, any changes I could make to this temporary session wouldn’t ever be uploaded back to Google.
Password Exporter allows you to import passwords too, so you can avoid the need to install any third-party workarounds like LastPass (which again require you to upload all your browser data).Firstly, though, using Password Exporter in Firefox (Tools > Add ons … Extensions > Password Exporter > Preferences), we can export a sample CSV file to see how Password Exporter expects its import data. Simply click “Export Passwords” and save the file to your home directory.
NOTE: This requires that at least one password is saved in Firefox already.
hostname username password formSubmitURL httpRealm usernameField passwordField
This is the format that Password Exporter will expect its import data.
The data’s headings that you have just exported from Chrome are a little different:
origin_url action_url username_element username_value password_element password_value submit_element signon_realm ssl_valid preferred date_created blacklisted_by_user scheme password_type possible_usernames times_used
We need to match up the firefox CSV headings with the corresponding Chrome CSV headings. To do this quickly, use a spreadsheet tool I used LibreOffice Calc.
This is what I arrived at:
(FF = Firefox; GC = Google Chrome)
FF: hostname username password formSubmitURL httpRealm usernameField passwordField
GC: origin_url username_value password_value action_url signon_realm username_element password_element
Once the fields are mapped, there’s a couple more important steps to undertake.
Firstly, when you come to exporting from your spreadsheet application, make sure you choose to edit the output filter. In the Export Text File dialog, make sure “Quote all text cells” does not have a check (tick) in the box.
For good measure, I also selected ASCII/US in encoding type, as that is the format used by Password Exporter when exporting. I think the importer should handle ISO-8859-1 and/or UTF-8, but your mileage may vary.
Now export it.
Remember seeing the additional header in the exported CSV file? It might have looked something like this:
# Generated by Password Exporter; Export format 1.1; Encrypted: false
In order to tell Password Exporter what format to expect its data in, this heading needs to be added back. However… the best way to do this is via a text editor, not in a spreadsheet program.
Open up GEdit, Emacs, Vi… whatever. Add that line to the top, but remove any trailing commas! It should now look like this:
# Generated by Password Exporter; Export format 1.0.4; Encrypted: false
"hostname","username","password","formSubmitURL","httpRealm","usernameField","passwordField"
One more step before you import!
A side-effect of exporting your CSV in LibreOffice is that empty cells are not quoted. In other words, the comma-separated values may appear like this:
"someusername","somepassword","someUrl",,"someusernameField"
Did you see those two commas with nothing between? The Password Exporter won’t like that when trying to import, so do a quick search-and-replace:
Search for ,, and replace with ,””,
Finally, save the file. Again, ENSURE the file type is US/ASCII.
Now open up the Password Exporter dialog from Firefox and click Import Passwords – you should see progress in the dialog shortly.
CAVEAT #1: BUG WHEN IMPORTING v1.2-EXPORTED DATA
There is an import bug when the version header is declared as 1.1. However, you can get around this by “fudging” the import header to an older version (I used 1.0.4). If you have trouble importing, adjust your header in the file to look like this:
"hostname","username","password","formSubmitURL","httpRealm","usernameField","passwordField"
After importing, you may see that not all passwords were imported. This is because duplicates are not imported. You can view the details in the link.
CAVEAT #2: SOME LOGINS, PASSWORDS, ETC ARE QUOTED
So far I’ve not had time to find a way around this. It’s to do with the import format.
The adventurous can investigate the source code, here: https://github.com/fligtar/password-exporter/blob/master/passwordexporter/chrome/content/pwdex-loginmanager.js
Hopefully you have now successfully liberated your passwords!
Problems? Comment below!
If you have a curious bent – and you bought a Chromebook thinking it would be the answer to all problems, then chances are you probably gave up on that notion fairly quickly and installed a variant of GNU/Linux on it.
If so, well done. Thankfully, Daniel Berrange – a Red Hat fellow and Fedora users, posted some instructions on how to get Fedora 18 (Spherical Cow) installed on a Samsung series 3 (XE303C12) Chromebook. This is the route I decided to take, having been a Fedora user for many years. But I digress.
If you have GNU/Linux installed on a Series 3 Chromebook, you may want to remap those Google-inspired function keys that run across the top. You know, those keys with the arrows, reload, window-size/position, brightness and volume icons… Yeah. Actually, they’re function keys: F1 to F10.
A good read for how to identify what each key is can be found here, on this askubuntu post which details the xev command. xev displays the numeric keycode of the keyboard key (!) you just pressed.
Keys F1-F10 use the following keycodes:
Key | Keycode | Equivalent |
---|---|---|
Back | 67 | F1 |
Forward | 68 | F2 |
Reload | 69 | F3 |
Resize | 70 | F4 |
Stacking | 71 | F5 |
Bright down | 72 | F6 |
Bright up | 73 | F7 |
Mute | 74 | F8 |
Sound down | 75 | F9 |
Sound up | 76 | F10 |
To remap these keys, we now need to identify what extended functionality the XF86 multimedia keyset provides.
A reference table is available is available on linux questions.
I’m an avid tasker and a fan of the GTD methodology, but when I use tools that have lots (and lots!) of features I tend to slip up easily and do silly things. An example is adding a repeating task to my task list. A repeating task? Why is this an issue?
![]() |
Google Tasks: Simple. Too simple, for some. |
I simplify this slightly, but in David Allen’s approach to task management, anything that is time-related should be put into a calendar. Therefore, if I am allowed to set up a repeating task, this means I need to do something with a certain regularity, which further implies I must actually do it at some point in order for it to warrant the repetition which I have ascribed to it.
In ToodleDo and other “expert” task managers, the ability to manage tasks has advanced to the point where you can essentially control your calendar through your task manager. This approach really suits some people but, to me, this essentially is the tasks-first, time-second approach. It is truly a GTD-esque system and I have had a love/dislike affair with it for several years. I have never “hated” ToodleDo – it’s a great system, but isn’t as integral with my working environment as I would like.
To me, tasks should be lean and mean. I don’t really want to spend my time managing them – I want to be doing them. And various factors always weigh in that can be managed outside of my task list. I become less efficient if I start duplicating events into tasks.Part of me loathes the traditional “Weekly Review” of the GTD system. I have a daily review and the most important things are always the ones that get done – it’s a self-managing approach which I’m happy with and doesn’t require over-thinking. Removing the opportunity to over-manage tasks is A Good ThingTM in my book. All I want to do is store my tasks somewhere and interact with them quickly. Using Tasks in Google will accomplish this.
![]() |
GTDers rejoice! Toodle- Do lets you live the dream! |
Well, actually, they didn’t really say that. I did. But it’s true – it couldn’t be done, easily, until now.
Here’s what you need:
* I have only used this on Android 4.1 and have set up both of my Google accounts as sync accounts on my phone. As always, your mileage may vary.