• 3 Posts
  • 28 Comments
Joined 2 years ago
cake
Cake day: July 4th, 2023

help-circle


  • Man, I feel you on the affiliate link fluff. I actually ended up unsubscribing from the Popular Mechanics and Popular Science feeds because the signal to noise ratio was so bad.

    The creator of Nunti provided a very good primer on the algorithm design here. Basically, you indicate to the app whether you like or dislike an article and then it does some keyword extraction in the background and tries to show you similar articles in the future. I suppose you might be able to dislike a bunch of the fluff and hope the filter picks up on it, but it isn’t really designed to support the kind of rules that would completely purge a certain type of content from your feed.


  • Most of the feeds I subscribe to came to me in one of two ways:

    1. I enjoyed reading an article posted somewhere else (Lemmy, etc.) so I sought out the feed of that publisher.
    2. Sometimes news outlets enter into agreements to republish each others articles. When they do this, the re-publisher will usually include a little blurb at the end giving credit to the original publisher. If a feed I’m already subscribed to has an article re-published from elsewhere then I click through and check out the original source to see if I want to follow them as well.

  • It can be as simple as just putting an app on your phone. I use feeder which is fine. Pretty bare bones, but in that way it’s easy to learn and use.

    I’ve also been meaning to try out an app called Nunti, which I heard about a while ago from this Lemmy post. It claims to be an RSS reader with the added benefit of an (open source and fully local) algorithm to provide some light curation of your feed. It looks interesting, but I haven’t actually tried it out yet because I’m still deciding whether I want any algorithm curating my feed, even one as transparent as Nunti’s. It’s also only available through F-Droid right now, which is a bit of a barrier to entry.


  • I’ve been trying to solve this problem for a while. I’ve not yet found a really good solution, but I can summarize what I’ve learned, partly for your information but mostly in the hope that Cunningham’s law will finally put me out of my misery. Here are suggestions I’ve seen, organized roughly along some axis of easiest/most popular to hardest/least popular:

    1. Get an NVIDIA Shield TV. This isn’t really what you asked for. It’s just a commercial smart TV box, but it’s generally considered the least annoying and highest quality of the lot. The unfortunate fact is that when dealing with DRM controlled media, having a big company like NVIDIA behind the product goes a long towards simplifying things.
    2. Install Kodi. Kodi (formerly XBMC) is the elder statesman of the FOSS smart TV world. You can run it on just about any hardware, including a SBC like a Raspberry Pi. You can even get it pre-bundled with a Linux OS like LibreELEC. It’s got a clean interface and good community support, BUT it’s primarily oriented towards viewing media from your own collection. If you’re a person who consumes content via streaming services then you’re gonna have a rough time. Apps (mostly unofficial / community made) do exist for many popular services, but installing them can be a pain, and you may have trouble streaming in high quality (DRM issues).
    3. KDE Plasma Bigscreen. Great concept, not maintained any more. See my comment here for all the gory details.
    4. Clean build of Android TV. I’m not aware of any major independent android distributions (Lineage, Graphene) providing official builds of the android TV operating system, but this site seems to provide relatively consistent lineage OS based releases. You can run them on a Raspberry Pi. I haven’t done this yet, but it will probably be the next thing I try.
    5. EarlGrey TV. This one is a deep cut. EarlGrey TV mad a very small splash in the FOSS news cycle a couple of months ago. The concept is simple: install your favorite Linux distro and configure it to boot directly into a browser displaying a static webpage with links to your favorite streaming services and/or local media folders. The implementation is extremely basic, but the upside is that it’s easy to tinker with if you’re so-inclined.

    As for remotes, there are some decent options on Amazon that connect via bluetooth or a USB dongle and basically act like a mouse and/or keyboard packaged in a remote control form factor. I bought this one a while ago and it’s been fine. Nothing special, but fine. The play/pause/volume buttons on the front read on the receiving end like the media buttons on a keyboard. The air-mouse functionality isn’t for everyone, but this model is one of the few with a little track pad on the back if you prefer using that. Honestly just get anything with a full keyboard. So much easier than using the arrow keys to click-click-click your way through an onscreen keyboard.






  • 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.





  • Out of curiosity, what software is normally being run on your clusters? Based on my reading, it seems like some companies run clusters for business purposes. E.g. an engineering company might use it for structural analysis of their designs, or a pharmaceutical company might simulate the interactions of new drugs. I assume in those cases they’ve bought a license for some kind of high-end software that’s been specifically written to run in a distributed environment. I also found references to some software libraries that are meant to support writing programs in this environment. I assume those are used more by academics who have a very specific question they want to answer (and may not have funding for commercial software) so they write their own code that’s hyper focused on their area of study.

    Is that basically how it works, or have I misunderstood?


  • This actually came up in my research. Folding@Home is considered a “grid computer” According to Wikipedia:

    Grid computing is distinguished from … cluster computing in that grid computers have each node set to perform a different task/application. Grid computers also tend to be more heterogeneous and geographically dispersed (thus not physically coupled) than cluster computers.

    The primary performance disadvantage is that the various processors and local storage areas do not have high-speed connections. This arrangement is thus well-suited to applications in which multiple parallel computations can take place independently, without the need to communicate intermediate results between processors.



  • I’m not sure what you’d want to run in a homelab that would use even 10 machines, but it could be fun to find out.

    Oh yeah, this is absolutely a solution in search of a problem. It all started with the discovery that these old (but not ancient, most of them are intel 7th gen) computers were being auctioned off for like $20 a piece. From there I started trying to work backwards towards something I could do with them.


  • I was looking at HP mini PCs. The ones that were for sale used 7th gen i5s with a 35W TDP. They’re sold with a 65W power brick so presumably the whole system would never draw more than that. I could run a 16 node cluster flat out on a little over a kW, which is within the rating of a single residential circuit breaker. I certainly wouldn’t want to keep it running all the time, but it’s not like I’d have to get my electric system upgraded if I wanted to set one up and run it for a couple of hours as an experiment.