All of this user’s content is licensed under CC BY 4.0
Flatpak – It’s not without it’s own issues, of course, but it does the job. I’m not fan of how snaps are designed, and I don’t think canonical is trustworthy enough to run a packaging format. Appimages are really just not good for widespread adoption. They do what they are designed to do well, but I don’t think it’s wide to use them as a main package format.
Idk anything about that community, but I feel like it’s safe to assume that Discord isn’t going to take kindly to the existence of a server that, from the name, appears to be centered around piracy. I haven’t checked (someone please correct me if I’m wrong), but I feel like it’s safe to assume that piracy is something that would violate Discord’s ToS. Just use Matrix – I implore you.
Y’all don’t update your services?
It would put the more popular instances under enormous stress, if they had to serve every single subscriber from any other instance.
From what I understand, media (images, videos, etc.) is not cached. Does that not mean that, in the worst case where every post contained an image, the instance would be serving every subscriber, anyways?
I don’t really understand this reasoning. Some server would still need to receive those requests at some point. Would it not be better if those requests were distributed, rather than pounded onto one server? If you have a server caching all the content for its users, then all of its users are sending all of those requests for content to that one single server. If users fetched content from their source servers, then the load would be distributed. The only real difference that I can think of is that the speed of post retreival. Even then, though, that could be flawed, as perhaps the source server is faster than one’s host server.
For your reference, please see the updated post. I ran a S.M.A.R.T test, and the drive is indeed borked.
Thank you very much for all of the extra information!
I ran a S.M.A.R.T short test, and, yeah, the hard drive is quickly dying:
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
Failed Attributes:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 001 001 051 Pre-fail Always FAILING_NOW 1473
Please correct me if I am wrong, but this feels like a flaw with how Lemmy (perhaps other fediverse apps as well, I’m not sure) is designed. Why do I need to store all posts made to a community that one of the users on my instance subscribes to? Would it not be better to simply store my user’s posts, and comments, and the posts made to any communities hosted on my instance? Why do I need to store information from other instances, and users?
it is storage that requires more attention
Please correct me if I am wrong, but this feels like a flaw with how Lemmy (perhaps other fediverse apps as well, I’m not sure) is designed. Why do I need to store all posts made to a community that one of the users on my instance subscribes to? Would it not be better to simply store my user’s posts, and comments, and the posts made to any communities hosted on my instance? Why do I need to store information from other instances, and users?
That disk certainly isn’t healthy.
For my own future knowledge, what, exactly, in the logs, led you to that conclusion?
image the whole thing with ddrescue
Since you mention “image”, I’m assuming that I would need a drive at least equal to the size of the source drive to store the image? The issue is that the source drive is 2TB in size, so I would need to source another 2TB drive (at least) to store the image.
Unless you’ve done it already, I would recommend that you open a feature request on Jerboa’s GitHub.
Unfortunately, I cannot rename the files (extraneous reasons out of scope here).
If its only one season you could manually name them S01E01 etc.?
Unfortunately, I cannot rename the files (extraneous reasons out of scope here).
Whats the reason it doesn’t identify it?
I’m assuming becuase it doesn’t follow the format of S1, S2 etc for the first season. The show that I have has the first season self titled, then the other 3 are numbered in the proper way.
Did jellyfin wrongly identify the series as a version of it that doesn’t have this season?
Very interesting idea! But, unfortunately, no I don’t think that is the case here, as it’s the first season that is not being identified with the last 3 are being identified just fine.
Unfortunately, I am unable to downgrade to LTS. I need the latest kernel version for a my WiFi card (I’ve had a ton of annoying driver issues with this specific card that seem to now be fixed in the latest few kernel updates).
Nothing logged.
I have the exact same issue. I’ve never been able to see any errors in the logs. Essentially just says “going to sleep” then that’s it.
Using Nvidia with closed source drivers by chance?
No, I have an AMD GPU.
some hardware specs might help others with assisting you.
Noted! I’ll update the post.
Ah, dang, yeah that would do it. Thank you!
It appears I have misread the stack exchange posts I was looking at. I thought I read that they said that chown
, by default, traverses the symbolic link, but, in actuality, what they were saying was that it, by default, changes the ownership of the target file of the symbolic link.
you could use a lower quality stream (…) for motion detection, then use that to trigger recording on a higher quality stream.
Brilliant idea! Thank you for the suggestion!
If doing CPU-based motion analysis
Whyd do you specifically mention CPU-based motion analysis? Does this idea not work with the Google Coral TPU, for example?
What packaging format was Firefox installed through?