

Linksys MR7360. I just got official support, so i had to install a snapshot and manually install luci.
Why this one? Because it was 50% off due to a local shop closing. Last one on the shelf too.
Linksys MR7360. I just got official support, so i had to install a snapshot and manually install luci.
Why this one? Because it was 50% off due to a local shop closing. Last one on the shelf too.
I’d score openwrt as a perfect 5/7
OpenWRT on a new router. The wifi works better, ethernet works up to 980Mbit/s and I don’t have all my traffic routed trough a Huawei device.
And it allows you to configure everything.
If I have a complex regular expression to code into my app, I write it in pomsky, then copy paste the compiled regex to my source file, but also keep the pomsky source nearby. Much more maintainable.
Because not all parts of the repo have this status. Some are stable, well tested and critical.
No it is not. It depends on the codebase - if it is something relatively new, a proof of concept or something that is bound to change soon, there is no point in slowing the development down just because it is “too large to digest”.
Ah, yes, the reflog incantation. It is said that it can be performed only by those who have rebased on an hard reset origin.
Seafile is ok. It has a weird docker container setup (multiple processes running in a single container) but works okayish
Immich is great for this. You can share an album (or a sungle photo) by creating a link. That link can be password protected and have an expiry duration set.
I mean, updating the rules would help - clarifying that feeding data to any model / doing analysis on it requires copyright - but I doubt that it would stop companies from doing it. Because it is hard to prove in court that your work has been stolen.
But there is no real way of enforcing the rules. How would be combat piracy? If you make BitTorrent protocol illegal, people will just that using HTTP or anything else to share copyright-ed material.
Interesting, but probably not general and scalable way of fighting this problem. This practice is would be hard to implement for other types of content.
I think that copyright law is inherently unfit for internet. In its core, it is a legal restriction on re-publishing content which cannot be enforced on the internet. It does not prevent piracy or AI companies from collecting data. So I’d say that we should do away with copyright law altogether. This would, of course, remove a lot of incentive for producing content, but I think people would still produce content, even if they are not paid to do it, as long as their basic needs are satisfied. So if we, as a human race, progress to UBI, we can also solve copyright problem.
But if we get stuck in capitalistic age, I guess we have to pretend that information can be owned and legally restricted from redistribution.
UptimeKuma looks nice. Simple, but it does what it is supposed to.
Forgejo, immich, planka, seafile
You’ve just reminded me to fix cert renewal on my instance. I’m using let’s encrypt & their certbot with nginx and it is great.
Recently my nginx config got too complex, so nginx plugin stopped working correctly, because it wasn’t able to inject the config for ACME challenge correctly anymore. The solution was to manually configure location /.well-known/acme-challange
to read from a local directory and configure certbot to use a local webroot directory instead of fiddling with nginx config.
Yeah, idk, ive never actually used win 11 and have barely used win 10. It just a meme.
That’s a valid argument, but a very weak one. If we are not completely sure something is an improvement in all aspects are we just to dismiss it altogether?
They’ve lost potential revenue, but that is not the same as if amazon would come to their house and had stolen their only rucksack prototype.
Potential revenue is not your property.
It still sucks though.
This is all hard to do because it is hard to determine people’s race on lemmy. Some usernames give it away but most don’t. And I don’t go snooping trough their post history to find that out.
Can you expand on this wild claim? The whole point of containers is isolation so what you are saying is that containers fail at that all the time?
It could be run after git checkout and then rustfmt before commit.