.azw3
didn’t they switch to epub last year?
.azw3
didn’t they switch to epub last year?
so… netflix with extra storage?
evolution could happen in jumps. How often that happens is debatable.
raspi with vlc, mulvad and qbittorrent installed.
my last super simple project with js:
and the initial stuff was done with chatgpt. From start to finish the project took me about an hour (including deploying it to my server)
He also insists on refactoring any block of code longer than two lines into its own function
Thanks, uncle Bob.
[something] is sometimes a relaxing process
Yeah, no.
https://www.astralcodexten.com/p/why-im-less-than-infinitely-hostile
tldr: there are some legitimate use cases. But not in the first world. And they are unrelated to what crypt-bros are trying to sell.
disclaimer 1: the javascript for the comments is really bad and may freeze your browser
disclaimer 2: while the ideas in the article are interesting, they are flawed (or at least debatable). See comment-section for details.
user shouting
user: “YOU MUST IMPLEMENT XYZ!!! IT’S ESSENTIAL FOR MY USECASE”
answer: "Thanks for your feed back. We accept pull requests. "
and the user was never heard from again.
what is the bare minimum of security measures you can do?
I guess just the normal things with p2p stuff: make sure no ports are exposed except for the essentials, update software, use SSL wherever possible.
When you don’t use VPN, people will see your actual IP adress and will launch the same kind of attacks, they also launch on servers [1] to try to hijack your system and add them to their bot net.
[1] port scans, login-attemps, applying known exploits. If this doesn’t sound scary, you should try operating a server that is exposed on the internet and then look at the number of login attemps.
yt-dl has a speedlimit. yt-dlp has not.
I recommend to use relevativ paths in the compose files. e.g.
- '/home/${USER}/server/configs/heimdall:/config'
becomes
- './configs/heimdall:/config'
you may want to add “:ro” to configs while you are at it.
also I like to put my service in /srv/ instead of home.
also I don’t see anything about https/ssl. I recommend adding a section for letsencrypt.
when services rely on each other, it’s a good idea to put them into the same compose file. (on 2nd thought: I am not sure if you already do that? To me it is not clear, if you use 1 big compose file for everything or many small ones. I would prefer to have 1 big one)
you can use “depends_on” to link services together.
you should be consistent with conventions between configurations. And you should remove config-properties that serve no purpose.:
while you are at it, you may want to consider using an .env file where you could move everything that would differ between different deployment. e.g.
consider using podman instead of docker. The configuration is pretty much identical to docker-syntax. The main difference is, that it doesn’t require a deamon with root privileges.
you may want to consider to pin version for the containers.
pro version pinning:
con version pinning:
the option to have two instances is nice for maintenance stuff, e.g.
another benifit of containers:
Because it implies that synchronous code […] [is] still quite popular.
it isn’t?
why use a resource folder for it, when you can embed a base64 encoding directly into the source file?
there is an ad in the terminal!
you mean the “longer security updates with ubuntu pro” thing?
not exactly free, but have you tried phpstorm from intellij?
semi-related: would it count as piracy, if you reconstruct the 3d model from the 2d promo-images?