

Lee-bruh is definitely the way to go since it fluidly connects to the first syllable of “office”. If you do “lib-ray” or “lee-bray”, you’re forcing a ton of unnecessary annunciation on yourself.
Lee-bruh is definitely the way to go since it fluidly connects to the first syllable of “office”. If you do “lib-ray” or “lee-bray”, you’re forcing a ton of unnecessary annunciation on yourself.
Nah, should’ve been prior to the gender-affirming surgery.
Why pay for anything ever if it’s going to potentially get taken away?
Because it’s called “lifetime”? As in the entire point of the product is that it will not ever be taken away with the exception that you close your account? “Why pay for anything if there’s nothing enforcing the core premise of the product?” The gardener advertised a “whole-yard mow” for $100, but I’ve already gotten the area around the driveway, and honestly would it really be that bad if they just stopped right now?
You can talk about odds all you want (although I think around $100 million in VC funding puts those odds squarely in favor of “lifetime” users getting the floor sawed out from under them Looney Tunes-style), but the fact it’s even possible is what’s deeply disturbing, because it’s deliberate. Lifetime’s meaning should be unambiguously stipulated in a contract, not inferred. Know why? Because companies out there advertising “lifetime” subscriptions right now have little disclaimers like “approximately five years or so but honestly we don’t really know or care lol this license disappears whenever we want it to”).
People are assuming it’s for the lifetime of your Plex account, but my response is: based on fucking what? Plex on their website doesn’t seem to specify this anywhere, even in their terms of service. People asking on their official forums receive responses saying things like “probably for the lifetime of your Plex account” with no sources to anything. I’m not trying to sealion here; I literally can’t find a single instance of Plex stating officially in writing or verbally what “lifetime” actually means to the end user. If Plex isn’t going to rugpull, why can’t they add a couple sentences to their TOS saying something like: “The purchase of a lifetime pass grants the user a non-transferable license for [blah blah] starting from the date of purchase. This license will not be revoked unless 1) the associated account is terminated by the account holder or 2) the aasociated account is terminated by Plex for one or more of the reasons outlined in section [blah]”?
They could, they should, they don’t, and you have no good explanation, otherwise you would’ve offered one by now. They have enough money to afford a legal team that wouldn’t overlook that. The answer is that they want to reserve the right to destroy the “lifetime” pass whenever they want. If you can find official documentation from Plex Inc. saying that if I buy a lifetime pass today for $250, the license will only end with the termination of the account, then I’ll have no idea why they make this too hard to find, but I’ll take back everything else I said in this comment and stop using “lifetime” in scare quotes. I genuinely want to know if they say anything about this anywhere.
Another reason donating to FOSS is better than paying for proprietary software. Proprietary software devs get to run around stealing whatever code they like from the open-source community and never suffer any consequence because they don’t make their source available. I can think of a select few proprietary projects that have the balls to be source-available.
If you want to intentionally create a system that lets you evade accountability for stealing code, “fine”, but I have zero respect for you or your product, and I’m certainly not paying you a dime. I’ll put my money toward the developers who work to better the world instead of the rat fucks who steal from them to make money and pollute the software ecosystem with proprietary trash.
You literally said you have Plex pass in the other comment, why are you playing dumb?
They care about the people who don’t have a “lifetime” pass? Having empathy for others who don’t have what you have, caring about the ethics of a company whose products you use and pay for, and taking a stance that software should be as free and open as possible aren’t “playing dumb”. If anything, as someone who isn’t just using Plex for free, they’ve earned more of a right to complain, because they’ve shown they’re willing to pay for quality services but think this one is exploitative.
Maybe even disregarding empathy, they’re worried that existing features will become locked behind a tier that the “lifetime” pass doesn’t apply to? Maybe they’re worried that their “lifetime” pass won’t be so “lifetime” if “lifetime” wasn’t explicitly defined to mean lifetime at the time of purchase? Anything bad that can happen will happen with VC-fueled enshittification.
I also want to emphasize that relicensing from the GPLv2 to something proprietary is damn-near impossible for a project this large with a team who are so ideologically motivated to make FOSS. If I today submit a PR to the Jellyfin codebase, they can’t legally relicense to a proprietary license without 1) getting my consent to give them ownership of my work (I’m not likely to be paid off or convinced it’s a good thing that work I submitted for free is being enshittified), or 2) removing my work from the project if they can’t get in touch with me or if I say no. To emphasize: this consent is affirmative.
Thus, the process is to survey who’s contributed to the project, reach out to anyone whose work is still in the project (preferably in writing in a permanent, court-admissable format like email), ask them to transfer ownership of their copyright to you, keep track of who’s said no, said yes, or not answered, fulfill conditions for anyone who wants something in return, and meticulously rip out all of the code from people who say “no” or don’t answer. One of the project’s major contributors died 10 years ago? Legally, too fucking bad: they didn’t relinquish shit to you. Rip out that legacy code and start over.
Just like for instance if you want to take a Wikipedia article and own it for yourself, you can’t just go ask the Wikimedia Foundation nicely. You have to contact every single contributor whose work is extant in that article, and rip out work that isn’t explicitly given to you by its owner.
Some points as someone who does not use Tailscale:
TL;DR: This isn’t a binary “corporate versus non-corporate”.
Dollars to donuts it’s the corpo-fascist “tread on me harder, daddy” version of “freedom” they’re advocating for.
Not quite. Jellyfin does take in donations, but they intentionally hide this feature on their website – first you need to go to their Contribute
page, then you need to read “Find a way to contribute” blurb and notice and click Other
, then you need to click Help Pay for Expenses
, then they give you a speech practically asking you to reconsider:
As a project, we generally do not like asking for donations - we are entirely volunteer-run and intend to keep Jellyfin free as in beer, as well as free as in speech, forever. We do not wish, support, nor intend donations to privilege any user’s voice or priorities. That said, if you do want to help us cover some operating expenses like our VPS hosting, domains, developer licenses, metadata API keys, and other incidental expenses, check out our OpenCollective page to donate. Our entire budget as well as all expenses are publicly visible there.
And then you have to click that link and intentionally donate money – any amount you want either one time or monthly. The level of integrity compared to Plex – who take in VC money hand over fist and are descending into nickel-and-diming their customers – isn’t night-and-day: it’s the surface of a star and the center of the Boötes Void.
same can be said of FOSS. back channel deals, betrayals, hostile takeovers. all of these things can(and have) happen to FOSS projects. all under a false pretense of “openness”. it’s stupid easy to change licenses and lock out contributors. it’s happened several times. although you can technically argue anything before the license change could be forked, the event usually puts a bad taste in the public mouth and contributions dry up anyway. nobody wants to support a project with uncertainty.
“you could technically argue”??? That’s literally, unambiguously the law. That’s how the licensing works. This isn’t a technicality; it’s a fundamental, widely understood feature of the license. That’s how the license was designed to work. On top of that, licenses like the GPL have extremely stringent requirements for changing the license. (Here, Jellyfin uses GPLv2, so we’ll go with that.)
Everyone with work in the current codebase has copyright over that work under the GPLv2. Nobody relinquishes that to some centralized entity. Thus, you have two options for every single individual person whose contributions are still extant in your project (no matter how large): 1) get their consent not just to relicense but to the specific license you want, or 2) remove their work from the project either because you can no longer contact them or because they’ve said no.
The fact that you called this process “stupid easy” for anything but the smallest, most insular project is the dumbest fucking thing I’ve heard today, and I’m not even wasting my time reading the rest of your comment given how shockingly willing you are to not just speak about things you have zero understanding of but to somehow arrive at the most false statement possible about them.
Absolutely true for FOSS. For freeware? My opinion is that it’s money wasted because, unlike FOSS:
Here’s Jellyfin’s ‘How to Contribute’ page, incidentally, for no particular reason. Let Plex eat up their $90+ million in venture capital instead of taking money from the little guy and then fall off a cliff into an abyss of enshittification.
Exhibit #46,853 for why freeware will inevitably fall out from under your feet and why you should exclusively use FOSS wherever possible.
is it illegal for a majority of people to vote third party
No, we live in a first-past-the-post system where votes disappear into a black hole if they aren’t cast for the candidate with the plurality of votes, you smarmy fucking dipshit.
I’m really disappointed not to see Okular there. It’s FOSS, and it’s very cozy and useful.
Are people even thinking for five seconds about the ideas they’re upvoting?
This is just masturbating your rage boner to fantasy land punitive justice, not a serious policy suggestion to fix a single problem with the police.
This user’s entire history (username included) is spent signal-boosting attacks against Wikipedia. (Incidentally, they just deleted one from this very community because they got called out for it). This user is a ridiculous troll and should be banned from communities for their transparent, bad-faith agenda. I’m sure if there’s a story worth posting, somebody other than “wikipediasuckscoop” can post it. It’s so transparent that in an age where the Internet is blanketed with far-right disinformation, one of the last remaining bastions of truth that refuses to compromise and bend to said disinformation will come under attack by bad-faith, far-right actors desperately flailing to discredit it. This user doesn’t give a single shit about gender equality; they simply aim to discredit a resource standing in the way of their agenda.
A gender gap is a longstanding and severe issue on the English Wikipedia, but there’s a lot this article leaves out about its monumental and ongoing efforts to increase its coverage of women and to welcome more women into the project. This especially includes WikiProject Women in Red, far and away Wikipedia’s largest collaborative project whose entire purpose is to create new biographies about women. A large part of this biographical underrepresentation stems less from a bias in the editors themselves and more from the way that historical women have often been left out of published, reliable sources, and it’s taking scholars enormous efforts to bring those women to the surface today. It also says: “just 10-15% of its editors are female.” What this fails to acknowledge is that there’s an option simply not to declare your gender at all. To be clear, the ratio is atrocious, but 10–15% is likely an underrepresentation: women may be substantially less likely to self-declare their gender on the Internet than men. The Wikimedia Foundation has outreach, activism, etc. focused specifically on recruiting women to the project and has for well over a decade now. Wikipedia really is trying, and its experienced editors are constantly aware of this.
The article does put forth three hypotheses for why this gap exists, but I don’t think they put forth compelling evidence for the hypothesis that it exists because of the culture on Wikipedia or that it’s – in general – Wikipedia’s “fault”.
Outdated on Windows? Because on Linux, the LibreOffice UI is great, imo.