If anyone actually manages to get Plasma Bigscreen working decently, please let me know how you did it. I was really excited when I first learned about it, but after considerable time tinkering, I gave up.

My first attempt was to install it on an old laptop. It boots up and looks good, but a large number of the built-in apps hang forever on their splash screen when you try to run them. I also couldn’t figure out how to customize what apps appear in the carousels on the homepage. I’m not sure if that’s because there truly is no way to do it or if the functionality is locked behind one of the apps that I can’t launch.

The Plasma Bigscreen website indicates that it was designed to run on a Raspberry Pi 4, so I gave in and bought one in hopes that using the preferred hardware would work better. I followed the provided links to the latest Manjaro build of Bigscreen (which is over a year old) and installed it on my pi. Unfortunately, that build apparently suffers from a bug that prevents you from even getting past the login screen on first boot up. I don’t remember the details, but I think it was some kind of “can’t log in without setting a password” / “can’t set a password until you log in” loop. Anyway, I found a forum post discussing the problem with no solutions found, so I gave up on the manjaro build.

My final attempt was to install an ordinary desktop Linux distribution on the pi and then use the package manager to install Plasma Bigscreen as an alternative desktop. This got me in, but there were still a bunch of broken apps. It was about this time that I also realized that the original Bigscreen concept seemed to lean heavily into voice control via Mycroft AI. Mycroft has gone through some major changes since the project launched, and I think these changes have resulted in basically all Mycroft related code in Plasma Bigscreen being broken. That may or may not be related to the other problems I had. I never got to experience a fully functional version of the software, so I have a hard time knowing what exactly is broken in what ways.

Anyway, that’s my experience with Plasma Bigscreen. I hope this doesn’t come across as hating on the project. It should be evident from the amount of effort put in that I really wanted it to work, but in the end I had to conclude that in its current state, it’s badly broken with no sign of improvement or repairs.

Helpful tip: there’s a setting in Firefox to block all notification requests. It’s under Settings > Privacy & Security, then scroll down to the Permissions heading. Click the “Settings…” button next to the the Notifications entry and tick the box for “Block new requests asking to allow notifications”.

I assume there’s an equivalent in Chrome, but I don’t know what it is off the top of my head.

Ninja edit: Removed my attempt to hyperlink directly to the relevant Firefox settings page because it wasn’t working.

I don’t disagree, but Windows’ built in screen casting is hard to find and clunky to use. Linux is even worse off. Until earlier this year there was no real support from any Linux desktop environment. There’s a GNOME project that’s supposed to be putting together support. It was announced to ship with GNOME 46, but I’m not a GNOME user so I just tried to install the flatpak on my Kubuntu machine. It detects my TV but fails to connect with it. Definitely still needs work.

Some of that focus involves adding features that have become table-stakes in other browsers.

Speaking of this, does anyone else feel like Firefox’s lack of ability to wirelessly screencast is a major problem when it comes to convincing others to switch away from chromium browsers? I know chromecast and airplay themselves are both proprietary, and therefore counter to firefox’s open source philosophy, but they could at least implement first party support for miracast (or DLNA?) A surprising number of smart TVs work well with those protocols. They just tend not to advertise it because most people don’t know what they are.

I admit that I haven’t looked much into this since some years ago when I first switched over to firefox as my main browser, but at the time I found that there weren’t even any decent addons for screen casting functionality. I’ve learned to live without it, but I know a lot of people who use that functionality on a daily basis and could (quite justifiably) never be convinced to switch without an equivalent.

I agree. The concept is simple, and it’s not perfect, but it isn’t dumb either. This is basically recreating how coal and oil got in the ground in the first place. Plants absorbed carbon from the air as they grew, then they got buried in a way that prevented them from decomposing and re-releasing it into the atmosphere. My main question here would be whether burying it only 10 feet under ground is really enough for long term storage. The other big elephant in the room with carbon capture is that it can be a convenient excuse for companies to avoid doing work towards actually decarbonizing their operations. If, as the article suggests, this is used primarily by industries like cement making that don’t currently have a way to become carbon neutral then it’s a good thing. If it’s just used as cynical green washing by companies who could be doing better, then it’s at best a wash, and arguably a net negative.

If you were actually hoping to buy one but the rounded corners are a dealbreaker, then you may be interested to know that the DIY edition lets you mix and match the older display with the newer motherboards. Looks like opting for the older display even saves you $130 on the purchase price.

I’m a big fan of upgradable hardware, but lately I’ve found that the bigger problem with Android phones is the lack of software support. I had my last phone for 5 years and finally upgraded not because there were any major hardware problems, but because the android version was so far out of date that I was starting to feel the pain of missing out on some major improvements, plus some apps actually were starting to break. I picked my current phone specifically because Samsung was promising to support four major version upgrades which is, unfortunately, industry leading among Android OEMs despite lagging hugely behind Apple’s software support for their older models.

Fairphone seems to have a mixed track record on this. According to their website the Fairphone 2 got 5 major updates (great!). But the Fairphone 3 got only one update (bad). And the fairphone 4 has received one update so far with a second one promised. After that they say that they’ll try to provide two more updates, but they’re not making any promises because the processor will be out of support with Qualcomm by then.

This is, unfortunately, a very understandable position to take. The fact that Android OEMs rely on third parties like Qualcomm to design and support their processors is definitely the major problem here. Big guys like Samsung and Google can throw their weight around and squeeze a year or two of extra support out. But for small players like fairphone it’s not surprising that they find themselves in this position.

The fact is that any sane company would prefer to make money selling new chips, rather than spending it to support old ones. This problem will persist until consumers start demanding longer software support on their devices and making it a major part of their buying decision.