@trevor People in lemmy open-source community not seeing the relevancy of the open-source guarantee of F-Droid... SMH

@TwinTusks @w00t

Looks like yesterday Youtube simply stopped serving the format 22 (ytdl -f22, IIRC that was 480p video+audio) on all videos, so now anything that had this format selected as default is failing (@invidious). -f18 is still there (360p).

@sweng

> you agree to allow others to view and "fork" your repositories

How did you come to the conclusion that this does not grant the permissions to fork? It's literally in the sentence. Where else did you find the definition of "forking", if not here? This is what Github defines in the TOS, this is the label on the button in github UI, so clearly this is also what winamp means when they forbid "forking" and that means it's against the TOS. There is no other "forking".

@sweng @BrikoX No, the TOS "just" says that by making the repo public you are granting all github users the right to fork it. So that right has already been granted.

@theshatterstone54 @django

done, but be advised, it's 2.7GB

@cmnybo @marvelous_coyote That's.. not how it works. You wouldn't see any copyrighted works in the model. We are already pretty sure even the closed models were trained on copyrighted works, based on what they sometimes produce. But even then, the AI companies aren't denying it. They are just saying it was all "fair use", they are using a legal loophole, and they might win this. Basically the only way they could be punished on copyright is if the models produce some copyrighted content verbatim.

@FuckyWucky @corvus

If I have to choose between having a corrupt inefficient financial system with thousands of middlemen, vs this guy yelling at me his nonsense.. I'm choosing this guy yelling at me.

@SorteKanin I'd like to see that. I have already onboarded about 35 students and my whole family to matrix, nobody had any problems with signup. Bigger problem is later if they get the infamous "Unable to decrypt message" error.

@Faresh 1.) Making it easier to analyze. There are multiple steps in the whole process which may be hiding an exploit. The "tarball-not-same-as-git" is a clear example. Sure, reviewing will still be necessary and it will still be difficult, but it doesn't have to be as difficult as today. 2.) stop giving maintainer rights, fork instead. That's what pull requests are for. 3.) we should be careful if our critical infrastructure depends on a hobby project - either pay, or don't depend.

@shnizmuffin @Zen

Issues, milestones, discussions, pull requests, build logs, they all stay on the chosen host. That host can then add specific conditions to creating accounts, or participating in the discussion, searching code etc. Such as force you to have a phone number in your account, otherwise you won't be able to comment on issues. And all of these things might be locked in without a way to export and migrate to another host, so yes, it definitely matters where the project is hosted.

@podified

Now how many of them are not actually open source?

@SNFi Woodpecker passed 1.0 recently and it's much better. Try it again.