Actually, that is not always the case. The paper is often impregnated with waxes, inks, or oils specifically to prevent decomposition because you don’t want a container for a product that had an indeterminate shelf life to decompose; and again it introduces a significant hamper into recycling the container. It’s not “far” better unless you’re buying into base level green washing. 🤷‍♂️

The inside lining is generally plastic or metallic foils and causes these types of containers to be significantly harder to recycle than if they were made from a single material instead. The only way around this is larger, reusable containers with no waste. 🤷‍♂️ Not to say you’re the problem, just saying that it not being “made of plastic” doesn’t really matter as it’s still not made of biodegradable materials.

If you have an old desktop to repurpose, jellyfin is best ran on one of those with an Intel a380 gpu as long as the motherboard supports resizable bar. Cpu-wise jellyfin doesn’t really do anything intensive, and intel’s gpus all come with the same 2x video pipelines so upgrading to a 770 wouldn’t add any performance. If you’re buying new, my recommendation would be to get one of those intel white label laptops xpg made for a while. They can be had around $300-500 and come with a intel arc gpu you can use for encoding, resizable bar, decent ram, and a decent cpu. Great little jellyfin boxes.

I see what you mean and understand you. It’s very idealistic and I appreciate the thought of it, but it just won’t apply to a modern world full of varied people in the way you wish. The reality of it is that most people simply are not interested in participating and it’s not in the best interests of any project to expect to change that. Contributions from someone who shares no passion or interest will be less qualitative at best. That’s not even to mention that you’re likely missing the forest for the trees, as most open source software is built upon hundreds of other projects. You cannot reasonably expect participation on that scale. You can encourage, desire, or structure an income stream to support it; but you cannot expect it as it’s just not rational.

Not sure what part of the open source community you’ve been diving into, but the expectation of contribution to the project is not realistic nor logical as there’s not “always” something a person can contribute and you’d absolutely run afoul of “too many chefs in the kitchen” (even Wikipedia acknowledges this and has structured editing in a way to help alleviate the issues). Though open source for me, and a lot of others, has always embodied passion, a desire to aid the community, and a drive to prevent closed alternatives. None of that is based around “co-op” style expected contribution development. Hell, even Stallman famously addressed my “free as in beer” statement, saying that open source is more akin to “free as in speech” overall, but since this particular project is not monitizing and are GPL 2 licensed, they are absolutely free as in beer.

(https://www.wired.com/2006/09/free-as-in-beer/)

I understand this, but we need to be reasonable and avoid extremes. This software is extensively free (as in beer) and requires development support. As long as the prompt doesn’t cross any lines into exploitive territory I think it’s fine. It would be nice for them to have explored other fundraising avenues first though and have saved this as an exhaustive “final” option.

Something something Hollywood accounting.

Is this the new embrace, extend, extinguish?

They love Linux*!

*the windows subsystem for Linux

There are going to be very few hashing algorithms that can take a certain byte value and hash it down into a unique smaller byte value. If you miscoded the database and stored the hashed passwords into a value of a fixed length, you have to abide by that length without some trickery or cleaveriness. Is that not the case? Every time I’ve seen this limitation in wild code that has been the case.

The answer is always a poorly coded database. :(

The new prison bottom.

Haha, I was reading through these and realized we both named our catch a rides after a borderlands theme. Mine is Hyperion, or hype for short.

Hyperion, Hype for short.

Thank goodness we can count on various humans pack rat archival behavior.

Thanks for the psa op

It is a high risk job along the lines of coal mining and such, since it will result in an increase in transmitted disease risk. It’s important to acknowledge that, but I am on the side of it being work. I just think we need strong protections in place and regulations to handle it akin to other dangerous jobs. Like, a sex work branch of OSHA.

If it’s time, storage, and compute sensitive to generate it beforehand why on this green earth would you want to do it at stream runtime? Do you enjoy the thought of waiting 5-10 minutes for a stream to start or causing continual buffering problems during the stream? Also to my understanding the way it is built requires that the encoding be done for the entire length of the stream before any benefits are shown, so starting the process at stream launch would be less than useful even under the best circumstances. I think what you want to do is to sort your library into two, one you want to watch, and an archive. From there you can enable trickplay on just the “want to watch” library.

We don’t ignore them. We scope out implementation plans constantly, it’s just when they hit the MBA managers desk they tend to end up in the shredder.

Prison for this grifter when?