If all you're wanting to do is hide your home ip, could you just put it behind cloudflare?
boothin
joined 2 years ago
Typically you'd have a server running on a device on each UPS, and the clients would be the other devices also plugged into that UPS, so when that UPS is low, everything plugged into it will turn off. If you have another UPS elsewhere in the house, you would have another server installed on a device there so it can monitor that UPS that it is plugged into, and tell the other devices also plugged into that other UPS to shut down. Without knowing the layout you are running though, there's no way to know if NUT is what you need or want.
So in your case it would likely be to plug your server and nas both into the same UPS, and when the server detects the UPS is low battery, it will tell the NAS to shut down. This would also require the switches/router/whatever to also be on a UPS to hold power of course. So then it basically becomes each little cluster of devices that need UPS would also have a switch nearby that is also on the UPS
This isn't quite blocking the entire instance, but it blocks any posts that are hosted on the instance. It would not, for example, block a link post to youtube that is posted to lemmy.ml
Look into NUT, Network UPS Tools. It runs in a server/client type of set up. You'd install the server onto the device that has the UPS data connected to it. It then monitors the UPS status and can tell all the clients to shutdown when the UPS is running low.
If you're using the search in the magazines tab, leave off the prefix to the community name. So you'd want to search for climbing@lemmy.ml
And if you are the first person to search for a community on another instance, you won't see any of the old posts because it is not retroactive, but any new content will show up as its posted
When you say peak do you mean like a one off large spike, or it constantly hovers around 96Mbps? If it hovers around 96 Mbps that is really high if you aren't serving multiple clients at the same time. You can also try turning up the "Transcoder default throttle buffer" setting in the transcoder section of the server settings. This makes the server pre-transcode farther ahead and can help with making sure the stream is constant.
Also, what version of the nvidia drivers and CUDA are you on? For best results you should be on at least version 525 and cuda 12.
Lastly, you say you are on gigabit, so why is your upload only 130-300 Mbps? Is the pc conncted to your network via wifi?
The domain page is for the domain the post links to. For example, if you make a post that links to a youtube video, the domain for the post will be youtube.com. Since all text posts created on lemmygrad.ml are hosted on lemmygrad, the domain is lemmygrad.ml. But then if someone posts a youtube video to a lemmygrad community, the domain for that post would be youtube.com, so would not be blocked. That means you would still see that post, even though it was posted to a lemmygrad community.
The post's domain is the little url next to the post's title. Like in this image, you can see the domain for the top post is kbin.social and the bottom post is imgur.com. Even though that bottom post was posted to woodworking@lemmy.ca the domain is imgur, so something like that would not be blocked if you block the instance's domain.
https://imgur.com/a/93Yy449.png
You can quickly tell if Plex is hw encoding by looking at the server dashboard while someone is watching a stream. It will say (hw) next to transcode like this: https://i.imgur.com/rxDxbeV.png
How is your plex server installed, docker or directly on the system?
I don't know which sorting algorithms are affected by this same issue, but there is a known issue for the hot sorting: https://github.com/LemmyNet/lemmy/issues/3076
Something that helps a little is if you manually go to the domain page (or click on a domain next to a post that shows the domain) you can block it from there. For example if you wanted to block lemmygrad.ml posts, you'd go to https://kbin.social/d/lemmygrad.ml and block it from there. This doesn't remove posts from the instance that link to other sites, but will at least remove all the text posts
I had a similar issue where it was thin in regular intervals similar to what it looks like in your pics, the issue I had was the extruder gear was clogged up on one side so it wasn't gripping the filament and slipping until it spun around to the unclogged side and it would extrude normally again.