sfunk1x

@sfunk1x@lemmy.world

• ⁨Comment⁩ on ⁨Selfhosted alternative to Spotify⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:

  I started working on a hobby project recently to meld the utility of Beets with a music and podcast streaming service, like Subsonic. I’m developing this with a contract-first approach, and so far I’ve gotten most of the podcast management code in place, but I’ve not started working on the frontend outside of integrating a skeleton project into build process. I’ll add a note to look into supporting webdav data sources directly.

  I plan on doing another big dev push around Christmas, so hopefully I’ll have an MVP app to show off around that time. The frontend is a basic vite/react base and the backend is Spring Boot with Kotlin. I’ll be looking for some contributors for the mobile app side within the next few months.

• ⁨Comment⁩ on ⁨After announcing increased prices, Spotify to Pay Songwriters About $150 Million Less Next Year⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  Metallica, Dr Dre, et al were not wrong in suing Napster. We’re seeing the fruits of the evolution of that format. I guess at least people aren’t downloading “Get Back ft Stevie Wonder - Oasis.wma” anymore, and somebody is making money off of it. Just (mostly) not the artists that make the music.

  Low cost, distributed digital distribution is absolutely a thing. Phones have enormous storage anymore, so much so most people could have their entire music collections available on their phones or tablets - not everyone - but most people.

  A distributed streaming platform would really be the way to do this and make it cost effective for everybody. An app that could stream from a list of sources (remember playlists? M3U files that could play from multiple Internet locations - yeah, that already exists and has since before 2000) would enable people to stream the music they haven’t found yet or are searching for.

  Seems like an interesting open source software project, to be honest. Funkwhale is probably a good basis for extension, and could be run by the artists (or provided to then via a simple click to setup platform) for low overhead.

• ⁨Comment⁩ on ⁨How do you handle family requests that you disagree with?⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  You rip them and provide them to a community that will then re-dub them into something fun. Hilarity ensues.

• ⁨Comment⁩ on ⁨Google Search is getting even worse for independent sites⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  Seems like a combination of building a proper webring and then setting YaCY loose on it is probably the path forward.

• ⁨Comment⁩ on ⁨Windows 10 reaches 70% market share as Windows 11 keeps declining⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  I’ve been a hardcore Linux gamer for 15+ years, but there’s some games that just don’t work on Linux, unfortunately. Sim reaching was something I wanted to get into so I could get familiarity with some tracks before I actually go drive them, so putting up with windows long enough to launch the games is something I can deal with.

  If M$ starts sending me ads mid game, then I might start looking for other solutions.

• ⁨Comment⁩ on ⁨Windows 10 reaches 70% market share as Windows 11 keeps declining⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  Thankfully I only have to use Windows to play video games. It would be terrible having to use it everyday for work.

• ⁨Comment⁩ on ⁨SBC Case Builder v3.0 can create thousands of cases for popular SBCs and standard motherboards⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  Seems like this could be killer for building a multi-Turing Pi rack mount case.

• ⁨Comment⁩ on ⁨Is it that difficult to run Mastodon over Docker?⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  I’m running the mastodon stack in docker via a compose file. It was straight forward. Follow the instructions to the letter and it will work.

  I will say that it is in your best interest to have an automated update process happen, either manually (via cron) multiple times a day or have some kind of orchestration layer that manages updating the component images once they are released. Mastodon has had some nasty 0 day bugs that involved account and server takeover that had to be fixed immediately, and you don’t want to lag very far behind in those cases.

• ⁨Comment⁩ on ⁨Building my Homelab!⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  That is probably true, however, I personally use it to share with others who are not part of my network, calendar integration, password database access across many devices, rsync backups across baby devices, document editing via collabora and probably other things I’m not thinking about at the moment. I don’t have the performance issues that others note, but I took all of the performance improvement steps noted in the documentation: have bare metal well-resourced db hosts (for multiple services), dedicated redis cache, properly configured php-fpm, etc.

• ⁨Comment⁩ on ⁨Building my Homelab!⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  Nextcloud is good at general cloud features. It’s not specialized in photo management. If you’re storing memes or cell phone pictures it’s fine, but if you use an actual camera that uses a RAW format, you’re much better off using Immich.