Microsoft is killing Skype in May 2025. I haven't used it for a few years, but I'm going to shed a tear or two.
It's hard to overestimate how important Skype was a little over 20 years ago. I had recently moved to San Francisco and made a lot of phone calls to friends and family back in the UK. There was this thing called a landline, and as well as local service you had to choose a long distance provider with all sorts of complicated tariffs and fees. Cell phones were their own nightmare and even for SMS you paid per text message. Incomprehensibly, ring tones were on their way to being a multi-billion dollar business. My current phone has been on vibrate for its entire life and I travel the world with free high speed Internet included in my plan. Skype marked the beginning of this transition using P2P to open VoIP and video calls to the masses. I even had a cordless phone that made local calls over the phone line but seamlessly switched to Skype for long distance.
Skype's P2P stack could be used for more than phone calls. I built a business to backup your computer over Skype. It's one of the best things I've ever worked on. The Internet was slow for most people. and so you could do a local backup on LAN and then send incrementals P2P via Skype whenever your computer was idle. We also did superior local backups with full history, encryption and locked file support when most competitors choked on PST files. Skype were kind enough to include us as a premium extra in the client. We did some paid search and PR, but the lion's share of our customer acquisition came from this placement.
My current job involves many Teams calls, but before that we operated on hundreds of Skype channels. Before that work was driven by email and conference calls. I'm ambivalent about this shift. Email has some advantages, and hours of video conferences are way more draining than the voice bridge alternative. Teams brilliantly combines channels and chats that look very similar but work completely differently adding an entirely new mental load to the workday. Skype used to display a special cat emoji if you held down three keys at once. I know which philosophy I prefer.
(Published to the Fediverse as:
Bye Skype #etc#skype#microsoft Memories of Skype, including building a backup business on it, that mysterious cat emoji, and a landline with Skype built in. We'll miss you!)
By Robert Ellison. Updated on Wednesday, March 12, 2025.
I want to do two things with my digital photos. First, keep them safe, especially all those precious memories of random parking meters and unfathomable HVAC mechanisms. Second, enjoy looking at the small subset that are precious family moments. I'm not a special snowflake, these basic requirements should represent a large and competitive market. Unfortunately I'm not holding my breath for much in the way of consumer friendly regulation for the next four years in the US.
Google is making some changes to their Photos API next month, which amount to "Get the fuck out of our Photos API". They're a polite organization so they phrase it a little differently: "We're excited to see the creative solutions developers will build using the new Picker API and the updated Library API.". The developer documentation is a little more pointed: "If your app relies on accessing the user's entire library, you may need to re-evaluate your app or consider alternative approaches."
I have an Aura Carver Mat, a nice digital photo frame that I synced to a shared Google Photos album. Easy for me to add photos, way too easy for the kids to add photos - a fantastic device. As of next month it's ewaste though. I'm not going to upload photos slowly through some picker API like an animal. I'm going to end up building something complicated out of a Raspberry Pi (adds to actuarially unrealistic to do list).
This change doesn't impact backup, because that was already broken. For a while Google Photos nicely integrated with Google Drive and I ended up with a local copy of everything that I could then backup through other means. I'm never going to trust any one company to look after important files and so my philosophy is to backup twice online and once to an external hard drive that lives in a fire safe. (At one point I even built a backup company based on this model).
Google killed the Drive integration and so I MacGyvered together an apps script based solution that used the Google Photos API. This revealed to me that the Photos API would not return location information. Even worse it was impossible to get the full resolution version of a video to download. So it's not like I was in love with the API before this most recent change.
My current approach is a mix of sad and awesome. The sad part is that I use Google Takeout once a month to get an archive of all my online photos. Thankfully this still works. The awesome - I wrote this photo sorter tool that takes the messy download and organizes it by year and month. And I also wrote a volume shadow copy tool that lets you backup a drive without getting hung up on locked files. Those pieces get my photos safely to an external drive, and I upload to Amazon Photos too (the third leg of my backup stool).
(Published to the Fediverse as:
Google Photos killed my Aura Frame #etc#google#photos#aura#backup Google is changing their Photos API so my Aura frame is ewaste. Thoughts on using and backing up digital photos.)
I spent a few days near Shasta Lake over Thanksgiving. Here's a three night time lapse of the milky way. Also a couple of great hikes in the area: Clikapudi Loop (long) and Waters Gulch Loop (short). Some other travel time lapses include Bangalore and Lviv.
There was an election. I probably single-handedly evicted Biden and then endorsed Harris. Unfortunately my lifetime winning national election voting record stands at 1. And I got to vote in the US and the UK this year. Trump would probably have lost if Biden gave this speech I wrote for him. I do better in local elections and this year used OpenAI to semi-automate my California and San Francisco proposition guides.
I got my first electric vehicle - so should re-write this post to be far more righteous - and the hardest part was figuring out PG&E's shell game of rate plans. I ended up writing a python script to simulate my bill and it should work for anyone else trying to figure out this conundrum.
I know what this review is trying to say but nonetheless I have been chuckling for two days about all the women ruining the view on this 18 mile long beach, especially with the accompanying photos.
By Robert Ellison. Updated on Sunday, December 29, 2024.
I've been Fediverse curious for a while, but even with its decentralized nature I'm not interested in creating content for someone else's platform. This blog has been federated for a little over a year thanks to Bridgy Fed, a nice free service that handles most of the gory implementation for you. I was delighted to learn this week that the project is now part of a non-profit, A New Social. Maybe the decentralized Internet stands a chance of coming back again? I'm cautiously optimistic and will be integrating a bit harder next year.
(Published to the Fediverse as:
Bridgy Fed and A New Social #etc#ithcwy#bridgyfed#fediverse A New Social is a non profit that is taking on Bridgy Fed and hopefully opening up the Fediverse.)
Google tried this with Duplex, but for the solved use case of making a restaurant booking. The restaurants didn't like it and we didn't need it.
What I want is - transcribe my voicemail and send me an email. During that step drop any obvious spam. If I choose to reply to the email phone the person back, repeatedly, until you get them on the line and convey the reply and take down any response.
This looks like Twilio for the telephony, Whisper for the transcription and OpenAI realtime for the conversation. Do I want it badly enough to build it? Maybe. I should do this first though.
(Published to the Fediverse as:
AI Wishlist: Use email to reply to voicemail #etc#lazyweb#openai#voicemail#email Use LLMs, OpenAI realtime, Whisper and Twilio to prevent the scourge of real time communication.)
I haveoccasionallybeencriticalofAndroid, so I'm delighted to have something positive to report. For even fairly long articles I can now read the whole thing!
Over the last few updates my phone has become almost useless for reading. I'm probably an edge case in the TikTok era, but reading is important to me. Android has got progressively more psychotic about preserving battery life with Adaptive Battery and the war on background services and numerous other 'enhancements'. If I take my attention away from what I'm reading for a split second Android kills the process, plows salt into the memory it once occupied, and emails the developer to request an environmental impact statement.
In theory none of this should be a problem because Android has an activity lifecycle that tells the app it's going to be hung, drawn and quartered. The app can then save the current state and restore it when the user comes back to the app. Of course many developers can't be bothered with implementing this properly and Google seems to set a very bad example here. Chrome - back to the top of the article for you! Google news - full reload of a fresh slate of stories so the one you were reading isn't even in the list any more.
Android 15 blissfully fixes this and has done more than exercise, diet or beta blockers for my blood pressure.
(Published to the Fediverse as:
I can finish a web page in Android 15! #etc#google#android Android 15 finally fixes background process killing, making it easier to finish reading long articles without frustration.)
Google has been sending me increasingly threatening emails about upgrading my Android apps and so August has been all about that. Helpfully Microsoft has also deprecated Xamarin (a tool I used to write software for Android) and so I also had to do a crash course in MAUI. Thank goodness for ChatGPT and GitHub Copilot. I also took this opportunity to figure out adaptive icons and generally update the look and feel of the apps.
Catfood Earth for Android has a new volcanoes layer and support for showing where you are on the satellite image.
I have wanted a decentralized social network for alongtime. Maybe this Fediverse thing is starting to get legs. Bluesky and Mastodon can now talk to each other via Bridgy Fed. Threads can post to Mastodon. ITHCWY has been on ActivityPub for a year now and it's become a significant source of traffic and comments. If you are on Mastodon or a federated service you can follow me at @[email protected]. I plan to get even more federated over the next year.
I waded foolishly into the debate around turning the Great Highway in San Francisco into a park, and found that the data doesn't support the fear of carnage in the Sunset when this road is closed. I also made a custom GPT to discuss the San Francisco budget with, and had to spend some time writing the missing manual to even know what to ask. Too late now, but here's a guide to the March ballot measures (watch this space for November) On a national level I got to update my NPVIC page now that Maine has joined.
