Category: tech
You are viewing all posts from this category, beginning with the most recent.
I’m not at all sure about this new “Gutenberg” editor they’re adding to WordPress. I’ve installed the plugin version to try it out. Gutenberg is a change to the web-based editor in the WordPress dashboard, not a separate app. I typed up my previous post in MarsEdit, as is my wont, and uploaded it. The Gutenberg plugin imported it nicely and displayed everything as you’d expect. But it turned all my Markdown into HTML.
That’s not what I want, and it’s not how most Markdown-processing plugins — notably WordPress’s own Jetpack — handle Markdown. Instead they keep the source document as Markdown and only convert it to HTML when the page is requested. That’s what using a dynamic CMS means, after all.
It appears that you can get Gutenberg to keep the Markdown as it is, if you type it into what they call a Code Block. So I’ll have to hope that [@danielpunkass](https://micro.blog/danielpunkass) updates MarsEdit to send posts to that kind of block once Gutenberg is the default. Assuming the WordPress API lets you do that, of course.
Radically Interoperable and Universal
In
Dan Cohen writes of how email got things right, long before some of our other ways of interacting online came along and got so many things wrong.I’ve long thought that email was the killer app of the internet, despite the problems that many people have with it. Those tend to be not inherent in email, but caused by the way we use it.
Here’s one point he makes, in regard to the algorithmic timelines that are ruining Facebook, Twitter, and Instagram:
Although some email systems algorithmically sort email by priority or importance, that is not part of the email system itself. Again, this can be added, or not, by the user, and the default is strictly chronological.
Although my main problem, as I’ve said before, is with some clients that insisting that “chronological” means “newest first.”
Beware of Email Apps Storing Passwords
Email apps, especially ones that offer advanced services like “send later,” may be storing our usernames and passwords on their servers.
To be clear what that means: if you use Gmail, for example, you put your Google username and password into the app when you set it up. You expect the app to store them securely on your device. But some apps may also be storing that username and password — your keys to all the Google services in this example — on computers owned by the company that makes the app. Computers over which neither you nor Google has any control.
I’m not suggesting that the company I talk about below, or any other, is doing anything nefarious. They need to be able to log in to your mail server in order to send your mail later. But I hadn’t realised until now what that means, and I’m guessing neither will a lot of people. And to my mind they don’t make what they’re doing clear enough.
Worst of all, having passwords stored on unknown servers — at the very least, that’s worrying.
Background
On episode194 of the Connected podcast, Myke Hurley and Federico Viticci were reviewing the latest version of the iOS (and Mac) app Spark. It’s a fine email app, which I was using on my iPhone and iPad. So I was alarmed when they mentioned in passing that mail handled by the app is routed through Readdle’s servers. That didn’t seem likely at first. Spark is an email client. You tell it what servers handle your mail, and it connects to them to receive and send. The servers belonging to the company that makes the app have no business getting involved in that.
I did some digging. Whether or not Myke was right™ about mail going through their servers, the reality turned out to be much worse.
Digging
I tweeted at the Spark account. Here’s what happened:
@SparkMailApp Hi, I was listening to a podcast today on which it was suggested that if I use Spark, then my email is routed through your servers. Is that true?
— Martin McCallion (@devilgate) May 25, 2018
Which podcast said that?
— Terry Blanchard (@terryblanchard) May 25, 2018
The latest episode of Connected, with Myke Hurley and Federico Viticci.
— Martin McCallion (@devilgate) May 25, 2018
The only time Spark servers access your email is to create a push notification (to create sender, subject, and message snippet) The content is cached until the notification is sent, but removed after that.
— Terry Blanchard (@terryblanchard) May 25, 2018
OK, seems fair. Thanks. Probably all a misunderstanding, either by them or me. Just out of interest, is the “send later” feature done on the client?
— Martin McCallion (@devilgate) May 25, 2018
Ah, forgot about that one! We will store it on our server until the send later time, then we send it through your email server and it is removed from our server.
— Terry Blanchard (@terryblanchard) May 25, 2018
OK. Isn’t that a problem, in that you must be storing your users’ mail server credentials on your servers? I’m pretty sure it doesn’t say that in your Ts&Cs.
— Martin McCallion (@devilgate) May 25, 2018
It’s the second item that we mention in our privacy policy. https://t.co/WpQSIDGPgx
— Terry Blanchard (@terryblanchard) May 25, 2018
I had already found their privacy policy:
OAuth login or mail server credentials: Spark requires your credentials to log into your mail system in order to receive, search, compose and send email messages and other communication. Without such access, our Product won’t be able to provide you with the necessary communication experience. In order for you to take full advantage of additional App and Service features, such as “send later”, “sync between devices” and where allowed by Apple – “push notifications” we use Spark Services. Without using these services, none of the features mentioned above will function.
The wording “Spark requires your credentials to log into your mail system in order to receive, search, compose and send email messages” suggests that Spark the app needs to log into your server, which it does. But nothing about that says that your credentials will be stored on their servers.
Further down, in point 4, “How Long Personal Data is Stored For,” in a table that includes “Type of information,” we see (emphasis mine) :
Email address, email content for Spark Services, mail server credentials
So there it is. They do store your username and password on their servers, and they do tell you; though only if you read well into the kind of document that notoriously goes unread.
Final Thoughts
For features like “send later” they need to store the fact that you want to send an email at a specific time, and log in to your server in order to send it. And to be fair, I’m sure they can’t be alone in keeping that kind of data. Lots of clients offer “send later” and similar services, and all of them will have to log in to your mail server to work. So they have to store your credentials on their servers to do it.
And consider, if you use Gmail, that means your username and password not just for Gmail, but for all Google’s services, are now stored on somebody else’s servers. Their security might be great, but how do we know?
The more I think about this, the more concerned I become. Passwords should only be stored in one place: a secure, trusted password manager. But above all, these services need to be much clearer about the fact that they’re storing our passwords.
Faces and Feeds
I think I might have to develop an app for reading Facebook the way I think it should work.
There was an article doing the rounds the other week about how “our minds can be hijacked,” which was all about how terrible social networking is for us. I skimmed part of it, but got annoyed when it seemed to be about rich Silicon Valley entrepreneurs deciding to go “off-grid.” That’s all very well for them, but most of us have to make a living.
More pertinently, since the main target for the attack was Facebook, it annoyed me because I use Facebook to keep in touch with people that I might otherwise not. For that, it can be very good.
And yet… it struck a chord with, me to some degree. I realised that Facebook has increasingly become more of a time sink than a pleasure. Not that I spend vast amounts of time on it each day, but when I do open it up, I often end up spending longer than I’d have wanted to. And not reading updates from friends and family, but following links to articles and quizzes and nonsense, most of which I wish I hadn’t bothered with.
By comparison, a similar length of time spent in my feed reader lets me read blog pieces by people I actively want to hear from, and which I’m generally glad I’ve read.
But they mostly aren’t friends and family.
And then there’s the fact that the Facebook algorithm is tuned to show me what it thinks I should see, not what I want to see. What I want to see is all the updates from my friends, in reverse-chronological order. And that’s all. But there’s no guarantee that it will show me everything everyone posts, and the order is close to random at times.
One way to work round this is to visit people’s individual Facebook pages. You could see all your the posts by all your friends by going to each of their profiles in turn. But that would mean you’d have to keep track of all that: remember who you visited and when, and somehow manage the list of people.
Keeping track of things is what computers are good at. The software should be doing that for us.
So I’m thinking that what I want is an app that will do that for me: that will keep a list of my Facebook friends, and show me all their posts (which of course is what Facebook used to do).
As far as I know, no such app exists. This seems strange and unlikely, but I don’t think Facebook make a public API available for third-party clients, so such an app would have to work by scraping the web pages, which is neither good practice nor much fun.
Of course, what this means is effectively turning Facebook back into a set of RSS feeds — or now, especially as I have some experience with them, a set of JSON Feed feeds. Which would then be usable in all sorts of other places.
Web scraping may be bad and painful; still, I think I want to write this thing. Watch this space.
The Kickstarter Corporate Communication Conundrum
Today I chanced to see an email in which a manager was asking his staff to work for extra hours. Well, ‘asking’ is putting it generously, to be honest. There didn’t seem to be much that was optional about it.
The Kickstarter connection, though: you’ll be familiar with the idea of ‘stretch goals.’ If not, the idea is that the basic target is to make X amount of money, but if we make X + 10%, or whatever, we’ll be able to do these other things. Develop additional features, make the item in more colours, or whatever. My guess is that the term originally comes from sports.
So this email included in the subject the phrase ‘stretch targets.’ Meaning we want you to do more this week/month/whatever, than we originally planned. It was clearly written by someone who thinks that the way to develop software faster is to work your staff to the bone. When in fact that’s much more likely to result in people taking shortcuts and making mistakes.
In this team they’re already working weekends, and now they’re being ‘stretched’ even more. It bodes ill. But perhaps co-opting the language of positive things for something so negative is worse.
Site Moved
This site is now running on a Linux virtual private server (VPS) at Linode. There may be some teething problems from the move, so please let me know if you see anything strange.
Great New Phone; All the Wrong Reasons
My iPhone 6 was getting slow, and its battery was poor. I have been thinking of replacing it. But September is approaching, and Apple will announcing new iPhones (three new ones, according to rumours). So I had more or less set my mind on waiting till then.
That would also be consistent with my iPhone buying history: 3G, 4S, 6… the next in the sequence is 7S.
Friday changed my plans. I was standing at a bus stop on Old Street, just replying to a WhatsApp message. Something touched my hand, and for half a second I thought someone was bumping into me. Then there was a firm grip on my phone and it was gone. Pulled right out of my hand and off down the road on a moped — which must have come across the pavement from behind me.
I should have been more aware. I knew this kind of theft was a thing. We’ve been hearing about them for a few months. But you don’t always think about it, and you never think it’s going to happen to you. And, yes, OK, drink had been taken. But not that much.
The bus arrived a few seconds later, so there was nothing I could do but get on and head home. There was another guy at the stop who witnessed it, and he very kindly set up a hotspot on his phone and let me use it from my iPad. The Find My iPhone app didn’t find it, so the thief had probably turned it off right away. But I was able to request a remote wipe in case it’s ever turned back on, and I got an email from Apple saying all the card details had been removed from Apple Pay.
All of which meant I had to make a trip to the Apple Store on Saturday. And to the Three store, where it was alarmingly easy to get a replacement SIM. I just had to tell them my phone number and give them a payment card. No questions asked. Not even my name and address.
So I now have jet black 256 GB iPhone 7. Which is lovely. I’m late to all the new features, obviously, but here’s a quick rundown:
- TouchID: it’s now insanely fast to unlock my phone. Seems like it’s almost before I touch the home button sometimes.
- 3D Touch: people on podcasts seem to be saying they’ve stopped using this, but I’m loving it. Especially the edge-press for activating the app switcher (a feature which seems to be going away in iOS 11, I hear, so I probably shouldn’t get too used to it).
- The haptic feedback generally. Little clicks that tell you when you’ve activated something. Just makes the whole experience much nicer.
- The “taptic” home button. When I’ve tried this in the shop before now I wasn’t too sure about it. But a couple of days using it for real and I think maybe I prefer it to the feel of the old real button.
Plus, it’s black. Really, really black.
Even the box was black.
The cables are still white, of course. Which reminds me, I’ve always disliked Apple’s ear buds, and passed all my past ones on to my kids. But I thought I’d give these a try, not least because I wouldn’t mind trying the AirPods if they’re ever in stock anywhere,1 and they have the same form factor.
And I don’t hate them. I thought I always had trouble getting them to stay in, but that doesn’t seem to be the case now. The main problem is they don’t give enough sound isolation, so you can hear the traffic and people talking even with music or a podcast playing. I’ve always preferred the kind with rubbery tips, which form a seal. But aside from that, these are better than I expected. Which bodes well for AirPods.
Downside: the battery life doesn’t seem dramatically better than my old one, weirdly. For the first couple of days it was busy downloading updates and restoring things (and getting hot), but that should be over now. I’m assuming that I just have to give it a few full cycles till it beds in and the measurement gets more accurate.
And all the things you have to set up again. That’s not the fault of the phone, though, so much as the way it came to me. If had planned this I would have done an encrypted iTunes backup, which would have meant more things were restored to the new phone.
Anyway, that was a lot of words and no links about not very much.
-
I asked in the shop if they had them in, and of course they didn’t. ↩︎
The Sound of Audio Formats
Amusing that in the same week that I post a criticism of software patents, the final patents on the MP3 format expired. Some people are characterising this as the “death” of MP3, which is just nuts.
In fact, far from being dead, it can finally come to life, as Marco Arment makes clear.
Software patents: they’re what needs to die.
In other software-and-the-law news, here’s a story about a case of alleged GPL violation coming to court. The judge so far seems to have made a good decision, by stating that the existence of the GPL and the defendant company’s use of the software does mean there was a contract in place.
Rational? Twitter, Micro.blog and Social Engagement
I had vaguely seen references to “ratios,” and was aware it was something to do with engagement on Twitter and elsewhere. But I hadn’t understood what exactly people meant by it. Then last night I saw a tweet in which someone said, “I accept I’ve been ratiod.” (Should the verb form rather be “ratioed”? Hard to say. Neither looks quite right.)
A search for understanding led me to this article on Know Your Meme. It tells us:
and goes into some detail about the origin of the term.
It makes me sad to read that. Imagine an interaction system where, if people reply to something you say, that’s bad. Well, it seems we don’t have to imagine it: we can see it right here on the “social” web.
I like to get replies on Twitter or elsewhere. A reply means, to me, that someone has read what I’ve written, thought about it, and found it worth responding to. I’m aware that I speak from a position of some privilege, in that I’m not in a group that is likely to experience the mass abuse that many do. But something has broken down in our systems of interaction if getting replies mean what you said “is bad.”
I’m far from the first to have made that observation, of course.
But consider Micro.blog, the still-young social network based on blogs that I’ve written abut before. Micro.blog has replies, but it doesn’t even have the concept of likes or retweets/reblogs. If you read a post and want to say something about it — even just that you like it — you have to reply. With words, in human language.
It’s a much friendlier place than Twitter.
This conversation from the last day or two gives a good flavour of the kind of thing you can expect.
If you clicked through that link you’ll have seen that it appears to be — and is — on the blog of the user who made the original post. The responses appear as blog comments. But while every Micro.blog user has a blog, you don’t have to interact with it as a blog if you don’t want to. You can do it all through the Micro.blog app or one of the third-party clients, or just the Micro.blog website, where you can see the same conversation.
Similarly, you can see all my posts here, as well as at their natural home.
It’s well worth a try if you’re looking for a less toxic social-media environment.