Links
🔗 Pika
Seeing this makes me want to try it. I think I have a problem: I want to try all of the blogging CMSes. But I have no need for it now, so I’ll just keep a link to it here for later.
🔗 The amazing helicopter on Mars, Ingenuity, will fly no more
Ingenuity has been an incrediable achievement. The engineers at NASA should be so proud of themselves. It’s sad to see this chopper grounded now, but seeing it fly for as long as it did has been a joy. Bravo!
🔗 Let’s make the indie web easier
Inspiring post. I will admit that while I was reading it I was thinking “what about this? What about that?” But I came away with the feeling (realisation?) that the appetite for these tools might be infinite and that one size doesn’t fit all. This might be a good thing.
All you have to do is dream up a good URL at your domain and redirect it to the feed’s URL provided by whatever service you use to host your stuff. And then that’s where you tell folks to subscribe.
It’s easy to forget (like I do) that there’s nothing magical about an RSS feed. It’s just one more thing served by HTTP at a URL. And thus, is useable with the real magic here which is HTTP redirects.
This is a brilliant idea. The only thing I’ll add is just to make those RSS feeds discoverable.
🔗 Apple Watch Series 9 and Ultra 2 Ban Takes Effect; Apple Appeals
The ITC’s ruling was subject to a potential veto by U.S. President Biden by December 25th, but today, the Office of the U.S. Trade Representative issued a statement that it has decided against vetoing the ITC ruling, meaning that the ruling is now final.
It seems odd to me that Apple was expecting a reprieve from the White House over this patient dispute with Masimo. Issuing a veto looks like choosing one US company over another. Doesn’t seem like good political optics to me. Maybe it seemed to Apple it was worth a shot. 🤷♂️
🔗 Hardcore Software: //build It and They Will Come (Hopefully) (paywall)
I remember this Build conference. I was using Windows 7 at the time and it was exciting to see Windows 8 previewed like this. It was a major departure from what I was used to, and I was eager awaiting the Ars Technica reviews of the OS, the apps, and how things like contracts will work for developers.
But… it was an excitement I had for others. I was less than excited about the idea of seeing the desktop take a backseat to this brand new world of Metro and touch based interactions. I guess I was not the only one.
It’s quite a shame really. The devs at Microsoft clearly put a lot of work into re-enginerring the entire OS.
It’s thoughtful posts like this that keeps me on Micro.blog.
Also, chalk me up as one who’d rather keep link previews out of the timeline. I posted a link in Discord and the preview was so obnoxious I wish I could hide it (really Discord? Why can’t I hide it?).
🔗 PlayStation is erasing 1,318 seasons of Discovery shows from customer libraries
The realization has forced people to more deeply scrutinize their digital media purchases and subscriptions and how they value digital content. It’s also leading to calls for investment in hard copies of media.
I still believe that it’s possible to have a (semi-)perminenant representation of media in the digital realm. You just need to make sure it’s in an open, non-DRMed, file that exists on your file system. I know, easier said than done. But it might be time for me to be better here than I have been.
🔗 Hardcore Software 065. SharePoint: Office Builds Our Own Server (link pay-walled)
Yes, believe it or not, I’m reading about how SharePoint was built. I never had a lot of experience with SharePoint myself: although I did work at places which used it, I tried to stay away from Office documents as much as I could, sticking to things like wikis. And yes, I can understand why others may find it pretty crummy (the post gives a few examples of how crummy). But I did find some ideas SharePoint had quite interesting, such as the “everything is a list” concept. I do appreciate this consistent through-line in the product design, much like Unix’s “everything is a file” philosophy. I also like the fact that this extends to user-defined lists, like a very simple database.
Anyway, this paragraph caught my eye:
The idea of Office extended by a website for each Office user and team was incredibly important simply because it made using Office better. It was also a vision we had from the time we acquired FrontPage—everyone should have their own place on the web where it is easy to keep their work and share it with others. We were clearly too early. As we will see it was not just that the world was not ready, the world was anti-ready. SPS fit with the products of the era that remained top-down, complex, and under the full control of IT.
I yearn for the day when organisations make it easy for any employee to whip up an internal webpage for their team. Documents and wikis are nice, but they’re just so limiting in how they show information. The freedom to use real web technologies to present something as best you think you can, while also keeping the data “in house” (password protected, stored on servers the company controls, etc) is just an area on office tech that’s missing.
Case in point: I would love to be able to build a website showing the the status of backlog items that I can share with my team. I don’t want to manage the raw data myself: that’s all being tracked in Jira anyway. But Jira sucks, and it’s really difficult to show an overview of work, especially when they span multiple epics. Having something like a simple dashboard which will pull Jira ticket status and display them as maybe progress bars would be great.
But where am I to host this? Probably not best to do so on the open web.
See also the idea of small databases.
🔗 DOS_deck
Experience classic games with modern convenience at DOS_deck. With full controller support and a carefully curated game collection, enjoy timeless classics and hidden gems, readily available for instant play in your web browser on devices you already own.
Filing this away to try later. Also interesting to see they’re using JS-Dos for this, the same thing being used by F5 To Run, which is cool.
Via Ars Technica.
Seeing everyone blog (yes, actually blog) about their default apps over the last two weeks has been absolutely wonderful. Robb has been doing a fantastic job maintaining an index of these posts, and has now added a network graph showing the links between them. Works great.
100% this!
It was only a year or so ago that I found out that RSS discovery was a thing (coincidentally-but-probably-not-really it was also a year or so ago when I first read Manton’s book which mentions this).
Before that, if there was a site I wanted to subscribe to, and there was no RSS link on the page itself, I wouldn’t bother. Apart from thinking that I needed the link to the RSS feed to subscribe, I also got burned so often by sites that didn’t even have RSS that I just defaulted to assuming there was no way to read their site in my feed reader.
Browsers are getting better at surfacing this though. Vivaldi now shows an RSS indicator in the address bar when it detects that the site has one. But it’s small, and I’m usually not looking at the address bar after entering the URL, so it’s easy to miss. Really, nothing beats putting a link on the site itself.
Now, if you escuse me for a second, I just need to check that I’ve got a link to an RSS feed on my site…
🔗 Google is moving Shopping List and other notes into one app to worry about, Keep
This is somewhat good news, as Keep is a decent note-keeping app. But it’s also concerning because there’s now one major place to keep your data that Google might one day abandon.
It’s striking seeing this line in the first paragraph. I use Keep for my shopping list. It works well, and it’ll be a shame if Google were to shut it down. But there’s also a risk of them being too focused on the app, where they cram some useless AI feature into it. Notion does this, and I wish there was a way to turn it off.
🔗 Canada’s 84-year radio time check has stopped because of accuracy concerns
Interesting article about how Canada broadcasted timing information via radio. Reminds me of the 6 pips played just before the news on ABC radio when I was a kid. I’m guessing they served a similar role.
One way to think about age – we become old when we think and talk more about the past than the future.
Oooh. I feel a little seen. 🫣
🔗 Using Web Components on My Icon Galleries Websites
Lot of neat stuff referenced in this post, like htmx and web components. I’d like to try them in some capacity, like some small web project. Unfortunately, the only things I can think of building right now are things for my job.
Greg Morris wrote an excellent post about personal blogging that resonated with me. I know this is something that I struggle with. There are many posts on my blog that are formal and impersonal. And I hate re-reading them: they’re super boring. On the flip side, seeing posts about my day (sans post about work), of photos and videos I’ve taken, are a joy to relive. I know these are posts I tend to prefer reading on personal blogs of others. I’ll try to write more of those.
Related: Nobody cares about your blog, via. Skoobs.
🔗 XML is the future - Bite code!
I wanted to write something about fads in the software development industry when the post about Amazon Prime Video moving away from micro-services back to monoliths was making the rounds. A lot of the motivation towards micro-services can be traced back to Amazon’s preaching about them being the best way to architect scalable software. Having a team from Amazon saying “micro-services didn’t work; we went back to a monolith and it was more scalable and cheaper to run” is, frankly, a bit like the Pope renouncing his Catholic faith.
I didn’t say anything at the time as doing so seemed like jumping on the fad wagon along with everyone else, but I have to agree with this article that this following along with the crowd is quite pervasive in the circuits I travel in. I did witness the tail end of the XML fad when I first started working. My first job had all the good stuff: XML for data and configuration, XSLT to render HTML and to ingest HL71, XForms for customisable forms. We may have used XSD somewhere as well. Good thing we stopped short of SOAP.
The whole feeling that XML was the answer to any problem was quite pervasive, and with only a few evangelists, it was enough to drive the team in a particular direction. And I wish I could say that I was above it all, but that would be a lie. I drank the cool-aid like many others about the virtues of XML.
But here lies the seductive thing about these technology fads: they’re not without their merits. There were cases where XML was the answer, just like there are cases where micro-services are. The trap is assuming that just because it worked before, it would work again, 100% of the time in fact, even if the problem is different. After all, Amazon or whatever is using it, and they’re successful. And you do want to see this project succeed, right? Especially when we’re pouring all this money into it and your job is on the line, hmm?
Thus, teams are using micro-services, Kubernetes, 50 different middleware and sidecar containers, and pages and pages of configuration to build a service where the total amount of data can be loaded into an SQLite3 database2. And so it goes.
So we’ll see what would come of it all. I hope there is a move away from micro-services back to simpler forms of software designs; one where the architecture can fit entirely in one’s head. Of course, just as this article says, they’ll probably be an overcorrection, and a whole set of new problems arise when micro-services are ditched in favour of monoliths. I only hope that, should teams decide to do this, they do so with both eyes open and avoid the pitfalls these fads can lay for them.
A lawsuit, the last refuge of a scoundrel.
(With apologies to the Simpsons).
P.S. Like the new design of Birchtree.
🔗 Reddit mods fear spam overload as BotDefense leaves “antagonistic” Reddit
I wonder if anyone at Reddit’s C suite has ever been a moderator. That this API fisaco is affecting the tools that mods use to keep the community spam free and happy should give them pause. That they don’t care is an indication as to how detatched they are from those “on the ground”.