Finamp’s current alpha was a huge surprise to me. I stopped looking at development for a few months and in that time they completely reworked it
Finamp’s current alpha was a huge surprise to me. I stopped looking at development for a few months and in that time they completely reworked it
Nope, but it has become a backronym https://wikipedia.org/wiki/Object_storage#Origins
You would first need to define malicious code within the context of that repo. To some people, telemetry is malicious.
Yo, they added full page copies now? Gotta give it a spin again
To me on the security side of things caddy has a feature I have yet to see anywhere else: default reverse proxy headers.
Got something you want to lock down remote js loading on unless it explicitly requests an override? Default the variable to a locked value. The application can override it with it’s own header as necessary.
deleted by creator
Ha, gotta add this regex to my spam filters now that you’ve pointed it out
I wish nginx had the concept of default header values for reverse proxies…
I mean, you can kind of do it with macros but man…
If only you knew what they’ve been doing to the embedded devices lately…
I mean, you shouldn’t really parse any language (markup, script or otherwise) with regex. The point is there are other tools for the job that get you closer to what the actual interpreter is expecting to see. It’s really easy to botch a regex and accidentally create new syntax matches.
Regex is fine for noncritical parsing. You’ll often see it used for text editor / IDE language syntax highlighting, but you should also have noticed by now how often that tends to break down with more extreme combinations of syntax.
I do agree that lexers should still be preferred for manual manipulation of existing langues, but do whatever you want. It’s not like any of us can stop you.
If you’re just looking for RSS -> Push take a look at feedpushr
I use it with gotify without too many issues.
You say that like there a large overhead to containers…
Even in this case that overhead is negligible. Container configs and artifacts are also more portable and easier to backup.
It was dead however long ago when I submitted a PR. Still unmerged with no activity on the request so I just never went back to check.
It’s good to hear that they are working on it again though, if that is the case.
It depends on what you want. Do you want containers that don’t blow away your firewall? Podman is nice, but docker can be configured a little to avoid this. Want things that autostart and don’t have issues with entry points that attempt to play with permissions/users? Docker or podman as root is necessary. Want reasonable compose support? Podman now needs a daemon/socket. Want to make build containers and not deal with permission/user remapping at all? Podman is really nice.
Do not attempt to use podman-compose. That app is dead.
Unfortunately if you want to make tools that will be used by other people then you must add docker support. It just owns too much of the market.
Can confirm. Software is trash. Wanted me to connect it to the internet and setup a cloud access account. Like, dude, you’re a glorified battery pack I’m not adding a backdoor because you want to tell APC when my warrenty is about to expire so I can get marketing emails.
I present to you the holy hardware compatibility table:
https://networkupstools.org/stable-hcl.html
Anything not listed there is not worth buying.
If you distribute FLACs and have good musicbrainz integration (userscript or otherwise) you’ll definitely have an audience on Lemmy
Correct. I assumed a normalized kWh rating would be better than any instantaneous measurement I had on hand.
I agree limiting application scope is useful for multiple reasons, however Jellyfin started as a fork of Emby which already had music support. I have yet to find a standalone application that has enough features to sway me from just utilizing the existing media server functionality.