Time for another tech post: fresh from the saga of Photobucket's disastrous changes of last year, I once again find myself discussing an unpopular change to an online photo hosting service but this time it does affect me personally. Back in the mists of time I had an account at Fotopic.net but since that company went out of business, Flickr has been my (and many other photographers') site of choice.
After a tough recent past that has seen a lot of ups and downs as part of the Yahoo empire, Flickr has now found itself in the ownership of fellow photography site SmugMug, which it was hoped would create a new era of focus and stability. However, in recent weeks a controversial and potentially damaging change to Flickr policies was announced, sparking a vocal backlash in the wake of Photobucket's similar actions. Read on to see the message in full and why I think this change isn't all bad news...
Showing posts with label computing. Show all posts
Showing posts with label computing. Show all posts
2018-11-20
2018-01-24
Very un-appy with eBay
My first proper post of this year is unfortunately another rant about the bizarre actions of a tech giant, this time eBay for their inexplicable decision to remove their mobile app's compatibility with older Android versions and woefully inadequate response to the resulting backlash. It all started when I did a factory reset on my phone. It's a Samsung Galaxy S2, which may be old but I've looked after it so it still works fine and perfectly suits my needs of reading emails, Facebook browsing, a few calls and texts, and the occasional photo. I deplore the wastefulness of modern society and can't stand to see perfectly functional products thrown away simply because they're old, so I can't justify replacing the old S2 to myself while it still works.
The reset installed Android Jelly Bean 4.1.2, the newest version of the operating system officially supported by this device. Everything was going well and all the apps I installed worked fine - until I tried to install the eBay app, only for the app store to refuse to download it as it is "not compatible with my device". Huh? The version I had before worked fine, going from version 4.0 to 4.1 isn't even a major upgrade and Android 4.1.2 was released only about five years ago so it's hardly an ancient obsolete operating system that no one uses anymore. Being unsupported but still usable is one thing but incompatible and totally unusable is quite another, so how come the eBay app is no longer compatible with my OS and why aren't eBay doing anything about it?
The reset installed Android Jelly Bean 4.1.2, the newest version of the operating system officially supported by this device. Everything was going well and all the apps I installed worked fine - until I tried to install the eBay app, only for the app store to refuse to download it as it is "not compatible with my device". Huh? The version I had before worked fine, going from version 4.0 to 4.1 isn't even a major upgrade and Android 4.1.2 was released only about five years ago so it's hardly an ancient obsolete operating system that no one uses anymore. Being unsupported but still usable is one thing but incompatible and totally unusable is quite another, so how come the eBay app is no longer compatible with my OS and why aren't eBay doing anything about it?
2017-11-17
Retro Review: Ford Simulator
Although I work in the IT industry I've never really been one for games. I'd describe myself as a very casual gamer who maybe spends a couple of hours a month gaming, and I'm an impatient sort who wants to make quick progress so I tend to stick to simple fast-paced games. As a car enthusiast, naturally it is driving games that appeal most to me and nowadays there is no shortage of ultra-realistic games and simulators to suit all tastes. I grew up in the simpler time of the late eighties and early nineties though, and here I look back at a very odd, obscure and crude program (I hesitate to even call it a game) from 30 years ago that played a part in shaping my childhood.
![]() |
| What kind of super-realistic simulation awaits when I press the space bar? |
2017-07-13
Photobucket's commercial suicide
A return to the subject of tech after a few months of vehicle-related posts. You will no doubt have noticed a recent major change to the Photobucket photo hosting website as the consequences are far-reaching and have single-handedly destroyed a large part of the internet through what I fear is a commercially-suicidal decision. For years Photobucket have offered free third-party hosting and thousands of people have taken advantage of this to host photos for use on forums, auctions and blogs, but they have now got greedy and decided to start charging an annual subscription of $399.99 for the privilege of displaying Photobucket-hosted images on other sites. Needless to say, there has been a huge backlash and the company is losing custom at a rapid rate, so the popular nickname of 'Photofuckit' is fully justified as angry customers give up and move elsewhere.
![]() |
| The most hated image on the internet right now. It's everywhere and has replaced countless photos. |
Labels:
computing,
IT,
Photobucket,
photography,
tech,
web
2016-04-21
A compendium of bad error messages
The subject of computer error messages is something that is guaranteed to get me riled. Errors are a sad fact of life in computing and something no one really wants to happen, but so many IT companies really don't help themselves with their unhelpful and often flippant attitudes towards them. It shouldn't be difficult to write a clear, concise description in language the average user can understand of what went wrong, what caused it and how to solve it, yet even in the short time I have worked in IT I have seen so many error messages that are quite frankly terrible and unfit for purpose and become utterly exasperated by them.
They range from the indecipherably technical to the overly 'friendly' and vague, via total gibberish, patronising nonsense, inappropriate frivolity and instructions that are quite simply impossible to follow, but all have one thing in common: they have singularly failed in their sole duty of helping the unfortunate user to understand and recover from the error. Here, in no particular order, is my own personal compendium of the worst error messages I've ever had the misfortune to encounter. You may find some of them hard to believe, such is the scale of their sheer awfulness, but I can assure you every one is genuine and has been seen on a real live computer system in the 21st century.
They range from the indecipherably technical to the overly 'friendly' and vague, via total gibberish, patronising nonsense, inappropriate frivolity and instructions that are quite simply impossible to follow, but all have one thing in common: they have singularly failed in their sole duty of helping the unfortunate user to understand and recover from the error. Here, in no particular order, is my own personal compendium of the worst error messages I've ever had the misfortune to encounter. You may find some of them hard to believe, such is the scale of their sheer awfulness, but I can assure you every one is genuine and has been seen on a real live computer system in the 21st century.
2015-09-02
Further Facebook friend frustration
Following up on a previous post written a few months ago, I have started to notice a new form of irritating behaviour becoming increasingly common on Facebook recently. Many friend requests are never being accepted or rejected by the recipient and are simply being left pending indefinitely, and in some cases this appears to be deliberate and intentional. It only takes a second to click the 'Accept' or 'Not now' buttons so at first I thought this was simply laziness, and to some extent it probably is but I've started to realise Facebook themselves may also be partly responsible.
To support my argument I have been regularly monitoring someone I sent a request to and have confirmed that she has accepted friend requests from other people since receiving mine that is still pending, and thus has definitely been online and seen my request. I find that extremely annoying: when accepting those requests there is no good reason why she couldn't have dealt with mine at the same time, so I just don't understand why it has been ignored and others accepted. Please people, if you don't want to be friends with someone, at least make the effort to let them know by rejecting their request and don't just leave them in suspense forever.
To support my argument I have been regularly monitoring someone I sent a request to and have confirmed that she has accepted friend requests from other people since receiving mine that is still pending, and thus has definitely been online and seen my request. I find that extremely annoying: when accepting those requests there is no good reason why she couldn't have dealt with mine at the same time, so I just don't understand why it has been ignored and others accepted. Please people, if you don't want to be friends with someone, at least make the effort to let them know by rejecting their request and don't just leave them in suspense forever.
Labels:
computing,
facebook,
facebook friends,
IT,
social media,
tech,
web
2015-07-27
Beware of Ctrl-Z!
This is not the post I was intending to publish today as that one fell victim to an infuriating feature of Blogger behaviour so I was moved to write about this instead as a warning to others. I have a first-class honours degree in computer science and am currently studying for an MSc in the same subject so I am by no means the average novice user and I feel I am suitably qualified to comment on how stupid and dangerous this feature is, particularly as Blogger is intended to be a simple tool that can be used by people without high levels of computer literacy.
I'm sure everyone knows what Ctrl-Z does: it is a pretty much universal shortcut to undo your most recent change. That's all fine and very useful but Blogger's implementation of Ctrl-Z has another nasty little trick up its sleeve: if you press it again when there are no previous edits in the history, it deletes the entire content of the post to leave you with a blank page. This isn't documented anywhere and the one relevant post I could find dates back to 2011 so it's not a new problem. That's not what an undo function is for so why they have decided to implement this feature and what benefit it has is unclear, but combine it with the automatic saving that is turned on by default and you have a recipe for disaster. For novice users this can doubtless cause blind panic and extreme anger as they think "Oh my God, where did all my work go?!", and possibly drive them to stop blogging as a result.
I'm sure everyone knows what Ctrl-Z does: it is a pretty much universal shortcut to undo your most recent change. That's all fine and very useful but Blogger's implementation of Ctrl-Z has another nasty little trick up its sleeve: if you press it again when there are no previous edits in the history, it deletes the entire content of the post to leave you with a blank page. This isn't documented anywhere and the one relevant post I could find dates back to 2011 so it's not a new problem. That's not what an undo function is for so why they have decided to implement this feature and what benefit it has is unclear, but combine it with the automatic saving that is turned on by default and you have a recipe for disaster. For novice users this can doubtless cause blind panic and extreme anger as they think "Oh my God, where did all my work go?!", and possibly drive them to stop blogging as a result.
2015-05-21
N for 'no point'
The sad and pointless life of the Windows N versions
Browsing the operating systems available through the university’s Dreamspark account, I came across something I had never heard of before: a load of Windows versions with an N suffix in their name. I was intrigued but Dreamspark failed to explain how these differ from the normal versions, so off to Google I went, to discover a story of yet another cack-handed response to a legal challenge that eclipses even the infamous 'browser choice' app for sheer stupidity.
2015-05-14
The trouble with Facebook groups
Facebook groups are great. They bring together people with common interests, no matter how obscure, and are a fantastic way to share things with like-minded individuals, and if there isn't a group for your interest you can easily set one up. That's the theory anyway, but unfortunately there are a few problems with the way Facebook have decided to implement the group system that make it a rather less pleasant experience than it should be.
2015-05-09
Databases and Digital Democracy
Modernising the voting system
Thursday's General Election highlighted to me just how antiquated and inefficient the voting system is in this country, requiring huge amounts of manpower and paperwork to administer with so much potential for mistakes. It's the 21st century so why are our election results still being determined by people counting marks on pieces of paper? As a computer scientist with a particular interest in databases, this seems an ideal use of such a system to me and having given it some thought, from a technical viewpoint this is actually a very simple problem that can easily be solved with current technology.
2015-04-25
Time, gentlemen, please
...stop trying to sort my news by 'interestingness'
A new trend seems to be spreading through the world of computing and I have to say it is one I deplore as it is technology for the sake of it and actually makes the user experience worse in my view. Not so long ago, your news feeds would be organised in a simple chronological order with the newest stories at the top, so you could scroll down until you saw a post you had seen before and instantly know you had seen all the new content and everything below was older. All nice and simple and everyone understands the concept of time, but that isn't good enough for many technology giants as sorting by time is basic stuff that doesn't show off their talents. Nowadays, there is an increasing trend to implement algorithms that deliver content organised by relevance or 'interestingness', which while technically clever do nothing to enhance usability and are a solution to a problem that doesn't appear to exist.
2015-03-05
Facebook friend frustration
I hope I'm not alone in my feelings towards Facebook friends - the sense of satisfaction when a friend request is accepted but also, more pertinently to this post, that feeling of disappointment and self-doubt when you realise a request you were confident would be accepted has been either rejected or worse still simply ignored and left hanging as a pending request. These feelings are even worse when you see these same people becoming friends with many of your friends and making you feel left out.
Labels:
computing,
facebook,
facebook friends,
IT,
social media,
tech
2015-02-26
Cloud computing is the future for universities
This article began life in late 2013 as an answer to a question in an assignment for the Cloud Computing module of my undergraduate degree programme, in which each student was given a cloud technology and asked to explain how it could benefit the university, mine being Rackspace hosted services. My response was well received by the lecturer and I feel it has genuine real-world merit as a solution to the challenges of academic IT provision so it is deserving of a wider audience, hence my decision to share it here. It is reproduced largely as submitted but with minor edits to remove references to the specific institution that would be inappropriate to reveal in public, and the mention of Rackspace by name is not showing favouritism but simply because that is the specific technology I was given by the lecturer; other similar cloud services are available and equally valid in this scenario. Although this text is now over a year old, the situation has not changed greatly and most of the problems discussed remain contentious issues, so it is still just as valid as when it was written.
Labels:
academic,
cloud computing,
computing,
internet,
IT,
rackspace,
tech,
university,
web
2015-02-25
Facebook groups and the curse of the unavailable attachment
Something that has been annoying me for ages and shows no sign of being fixed gives me cause to have another dig at Facebook I'm afraid. I'm sure you've all experienced this - someone shares something to a group but all you see is this message:
Utterly pointless really - why bother telling you someone has made a post you're not allowed to see, especially as the comments then just fill up with people saying they can't see it. I know why it happens - the person whose post has been shared has set its privacy settings to something other than 'public' so those group members who are not their friends don't have permission to view it. As the person who shared it is likely to be friends with the person who originally posted it, they probably won't even know some people can't see it.
Utterly pointless really - why bother telling you someone has made a post you're not allowed to see, especially as the comments then just fill up with people saying they can't see it. I know why it happens - the person whose post has been shared has set its privacy settings to something other than 'public' so those group members who are not their friends don't have permission to view it. As the person who shared it is likely to be friends with the person who originally posted it, they probably won't even know some people can't see it.
Labels:
computing,
facebook,
IT,
social media,
tech
2015-02-06
Why are links from Facebook crashing my browser?
Another tech post detailing a problem that's really starting to annoy me but I haven't managed to find a solution to. Whenever I try to follow a link to an external website from the Facebook app for Android, it crashes the browser with that patronising and unhelpful 'Unfortunately, Internet has stopped' message. Having read that Android's built-in 'Internet' browser is not the best, I downloaded Chrome from the app store, only for the exact same thing to happen. The browser starts to load, but before the URL even appears in the address bar, it shuts down and generates the error message so I can't even see the URL it's trying to load.
This behaviour is consistent with any external link from Facebook, regardless of the external site's address, and is getting so frustrating as it seems something very simple has been overlooked somewhere. I don't know if the cause is the Facebook app formatting URLs in a way that common browsers can't understand, or something missing from the browsers' URL handling, but I suspect the former as the problem occurs in multiple browsers. If anyone has any further information, or even better a solution, please leave a comment as this problem is starting to drive me mad.
This behaviour is consistent with any external link from Facebook, regardless of the external site's address, and is getting so frustrating as it seems something very simple has been overlooked somewhere. I don't know if the cause is the Facebook app formatting URLs in a way that common browsers can't understand, or something missing from the browsers' URL handling, but I suspect the former as the problem occurs in multiple browsers. If anyone has any further information, or even better a solution, please leave a comment as this problem is starting to drive me mad.
Labels:
android,
app crash,
chrome,
computing,
error message,
facebook,
IT,
mobile,
smartphones,
social media,
tech,
web browsers
2015-01-31
Are Facebook missing a trick?
A tech-related post this time - there's no vehicular content here. What started out as an idle 'I wish they would do that' thought developed into a realisation that Facebook may be missing out on a vast untapped stream of data, which given their insatiable appetite for knowing everything about everyone surprises me.
What happens when a friend request is rejected or declined? In short, nothing - the requester is not notified and the request is even removed from their activity log leaving no evidence that it ever happened, which inevitably causes confusion as they think maybe they didn't send the request after all and send it again so the other person gets annoyed by having to reject it again. Anyway, that's not really my point. I don't know about others but I only send friend requests to people I have actually met and I think have a high likelihood of accepting. The majority do but on the odd occasions when someone decides not to I would quite like to receive some feedback on why they did so - is it because they don't like the content of my profile, they just don't feel they know me well enough, or something else? If I don't know what's wrong, there's nothing I can do that might make them more likely to accept, but it feels quite rude messaging someone who has just rejected my friend request asking why they did it.
Having thought about this from a purely personal point of view, I then realised that collecting this information would surely give Facebook themselves a massively valuable insight into the psychology of their users and the type of people they might want to be friends with. As a simple example, let's say person X tends to reject requests from users with certain characteristics because he doesn't like the content of their timelines, but accepts requests from users with other characteristics. Knowing this would allow Facebook to provide much better focusing in person X's 'people you may know' list with a consequently greater chance that he will become friends with them and Facebook can do their 'your friends like this so you might too' marketing wizardry. Maybe they could even use this information to help build up statistical data on the probability of any given friend request being rejected and the likely reason why!
Correct me if I'm wrong, but didn't something like this exist a few years ago? After declining a friend request I'm sure you had to select an option, which I think may have been along the lines of 'do you know this person?' and selecting 'no' may have had certain consequences for the requester. Like so many Facebook features, this quietly disappeared just as suddenly as it appeared with no explanation, but expanding it into a list of reasons for declining would have provided useful feedback, both for the requester and more importantly for Facebook themselves.
Any thoughts, or is it just me who wants to know why my friend requests get rejected?
What happens when a friend request is rejected or declined? In short, nothing - the requester is not notified and the request is even removed from their activity log leaving no evidence that it ever happened, which inevitably causes confusion as they think maybe they didn't send the request after all and send it again so the other person gets annoyed by having to reject it again. Anyway, that's not really my point. I don't know about others but I only send friend requests to people I have actually met and I think have a high likelihood of accepting. The majority do but on the odd occasions when someone decides not to I would quite like to receive some feedback on why they did so - is it because they don't like the content of my profile, they just don't feel they know me well enough, or something else? If I don't know what's wrong, there's nothing I can do that might make them more likely to accept, but it feels quite rude messaging someone who has just rejected my friend request asking why they did it.
Having thought about this from a purely personal point of view, I then realised that collecting this information would surely give Facebook themselves a massively valuable insight into the psychology of their users and the type of people they might want to be friends with. As a simple example, let's say person X tends to reject requests from users with certain characteristics because he doesn't like the content of their timelines, but accepts requests from users with other characteristics. Knowing this would allow Facebook to provide much better focusing in person X's 'people you may know' list with a consequently greater chance that he will become friends with them and Facebook can do their 'your friends like this so you might too' marketing wizardry. Maybe they could even use this information to help build up statistical data on the probability of any given friend request being rejected and the likely reason why!
Correct me if I'm wrong, but didn't something like this exist a few years ago? After declining a friend request I'm sure you had to select an option, which I think may have been along the lines of 'do you know this person?' and selecting 'no' may have had certain consequences for the requester. Like so many Facebook features, this quietly disappeared just as suddenly as it appeared with no explanation, but expanding it into a list of reasons for declining would have provided useful feedback, both for the requester and more importantly for Facebook themselves.
Any thoughts, or is it just me who wants to know why my friend requests get rejected?
Labels:
computing,
facebook,
facebook friends,
IT,
social media,
tech
Subscribe to:
Posts (Atom)

