a cool (brr) dude
I would have preferred Jellyfin as well but chromecast was not working on my TV properly. So I tried Plex which worked fine.
There are only a few things I like to watch so I don’t need jackett etc.
Then I realised that I can just use a dlna server and cast using VLC for Android. This is working much better for me than Jellyfin or Plex which are overly complicated. I cannot even disable metadeta fetching in Plex. And have to log in their central server for some unknown reason.
I agree that NPM should not have ideally caved in to whatever Kik™ asked them too. Also agree that NPM had the right to restore the module as dictated by the terms of license the module was distributed under. I haven’t checked but I am 99% sure that is licensed under MIT which is the darling license of the node ecosystem. When you do that you are basically opening yourself to being abused by corporations. But I don’t want to blame the victim here because it is pretty common in webdev to be seduced by sweet whispers of the “open source” “community”.
Whether the function should be a part of the standard library I am not sure. If I had to do something like that I would most likely copy paste the code from a stack overflow answer. Having a whole module for one small function seems ridiculous to me.
There is still a market for these but they are marketed as HiFi devices with a significant markup. I have one called Shanling Q1 which is the cheapest such audio player I could find and I really like it. Would not have been required if phones did not ditch the 3.5mm AUX port but then they would not have been able to sell garbage like airpods and galaxy buds.
I am not really sure what is causing this. Sorry about this. It could be because of incompatible versions of lemmybb and lemmy being used. Maybe @firstname.lastname@example.org can help with this because it goes beyond my knowledge of docker. You can check lemmy logs to see if it is receiving request from lemmybb. Apart from it I am not sure what to do.
Try changing this to
LEMMYBB_BACKEND=http://127.0.0.1:30850 and see if it works.
Rocket has launched from http://127.0.0.1:8703
Make sure these ports are the same. Since your UI is running on 8703 you should use 8703 in the nginx config as well.
hedgedoc landing page says “real-time collaboration” but i can’t find any more info on it.
The UI doesn’t allow specifying sort order it seems but if you go to https://lemmy.ml/communities, the default sort order is close to what you want.
Nevermind I take it back. It may not be close to what you want.
Enjoy this: https://github.com/warpdotdev/Warp/discussions/400
I’ll get the popcorn.