there’s an entire wikipedia article for this that makes it super easy https://en.wikipedia.org/wiki/Pirated_movie_release_types
there’s an entire wikipedia article for this that makes it super easy https://en.wikipedia.org/wiki/Pirated_movie_release_types
Is it just me or does that “comparison” make no sense for this thread. It’s mostly comparing vaultwarden to the cloud version of bitwarden, not the self hosted version. It only mentions the self hosted version in passing. It doesn’t do anything to help someone choose between vaultwarden and self hosted bitwarden
I’m not sure if I would even recommend starting with fdm if your goal is resin. So little that you learn about fdm actually transfers to resin, they really are that different. If your end goal is resin because you want to make miniatures, you’re just wasting money getting an fdm printer.
It sounds like what you need to do at this point is find what IP address your lemmy instance and mastodon instance containers are using on your VPS. you can do “docker inspect containername” and look for the IP address in there. it might be something like 172.16.0.1 for lemmy and 172.17.0.1 for mastodon. then you want to set up your reverse proxy to point lmy.my-domain.tld to 172.16.0.1:80 (or whatever port you set lemmy to use) and then mstdn.my-domain.tld to point to 172.17.0.1:80 (again, port might be different, i dont know what the default port is)
-IF- both of the containers are using the same IP, then you will need to make sure that they are using different ports. if they are on the same ip and same port, whichever container loads 2nd will fail to properly load, because when a port is taken on an IP address, it is reserved and nothing else can try to listen on that port.
So a reverse proxy is sort of like a phonebook or directory, it routes outside requests to the appropriate place. So imagine your reverse proxy is a receptionist, someone comes in and says “hey I am looking for plex.mydomain.com” the receptionist would then use the phonebook and say “ok if you are looking for plex.mydomain.com, go to building 192.168.1.10 (the ip), room 9000 (the port)”
Since you are asking about dockerized services, the networking for those can be done in several different ways, but the one thing that really matters is that each service needs to have a unique combination of ip and port, because only 1 service can live at each address. With docker, you could set up multiple services that use the host server’s ip, in which case each container will need to be on different ports, or you could have it so each container has its own ip, in which case the port can be anything.
https://github.com/ahmetoner/whisper-asr-webservice
this project might be of interest for you, it is a web service/api for transcribing with whisper ai. You can either use the web site or make programmatic calls to the API using it
homeassistant community store has a cloudflared add-on that works great to get it to easily work over cloudflare tunnels
I believe in China red/green meaning is reversed for things like this, where red means positive/good and green means negative/bad
Just fyi how a client handles multiple DNS servers might not always be you expect and just depends on how it was implemented. Some clients can just send a DNS request to all DNS servers at once and take whatever responds first, essentially randomizing which DNS server gets used
I’m not gonna lie, between the dirty camera lens and the color of the filament, I can’t tell wtf is going on in this pic at all
Yeah, I think it falls squarely into your thing about a new term from open source as its not recognized as being open source by the OSI and probably won’t be due to it being too restrictive, but the restrictions close the loopholes, forcing the software to be more free at the same time so it’s kind of in a weird spot
MongoDB has a modified version of the AGPL that they call Server Side Public License that might interest you. Specifically the change in section 13:
“Service Source Code” means the Corresponding Source for the Program or the modified version, and the Corresponding Source for all programs that you use to make the Program or modified version available as a service, including, without limitation, management software, user interfaces, application program interfaces, automation software, monitoring software, backup software, storage software and hosting software, all such that a user could run an instance of the service using the Service Source Code you make available.
By my reading, it closes that loophole you mention by specifically calling out interfaces and APIs as also requiring the source to be available. At the top of the page I linked there is also a PDF showing the removals and additions they made to the AGPL to end up with their SSPL.
You didn’t keep your 2fa backup codes like they tell you to do?
You can usually find precompiled shaders to download, for ryujinx look at ryusak
I’m fairly certain hardware based 2fa has been around since the early 90s maybe even earlier. It’s not the maturity that’s the issue, as I’m fairly certain its significantly older than application based, but that it’s extremely inconvenient for the user to have to buy a physical key and keep it safe
kbin and lemmy are different softwares, but they are both used for link aggregation and the 2 softwares use a common protocol, so they can talk to each other. So there are kbin servers and lemmy servers, and they are all interconnected.
So now we can take this post as an example:
You are a user on kbin.social
You posted this question on /m/nostupidquestions@lemmy.world - this means the community you posted on is actually hosted on lemmy.world
lemmy.world then tells other instances that its federated with that someone just made a post on /c/nostupidquestions on its instance. what kbin calls magazines are called communities on lemmy, hence the /c/ instead of the /m/.
kbin.social and all the other instances will then also show this post, even though it originally was created on a different instance
Think about what happens to water if it’s heated above 100C… it turns into steam! The more water there is in the plastic the more steam there will be, causing the various issues like bubbling. The release of steam also means some of the heat is not being absorbed by the filament, leading to temperature issues as it exits the nozzle
What the dough is made out of isn’t relevant to it being a noodle or not though, unless you think rice noodles aren’t noodles because they aren’t made of semolina, eggs, and oil and aren’t typically cooked by boiling but rather by soaking in hot water?
Neither have sauce in them, they are more akin to a calzone