Its turtles cats all the way down.

Poor soul.
Reminds of the soft-drink brand corona.

ok.
just for you,

“2025-08-11”
that is from 3 months ago. I think that was another repo.

this repo I included had update until today.

I have the opposite opinion about this issue.

MIT-like licenses allow corpos to take over a project and make it private step by step (kinda like boiling a frog), first create a “open source” fork and fund it to the max. then step by step make it not open source. after a while (could be years) there is no open source influence and most of the project is under the command of the corpo.

the most recent one being android.

I have come to the conclusion that people that use MIT-like licenses don’t care at all about software freedom (which is kinda obvious if you read MIT license itself).

so I try to contribute to projects that are immune to that by using copy-left licenses ,so called viral licenses that “limit” the ability of corpos to take over a project with the intention of making private or even create a private fork of it.

you are corporation and want to contribute to a project to make it better? cool, so it would not matter to you if the license is MIT or GPL? right??? you don’t want to do a sneaky fork and make it private, right? so you would have no issue with GPL.

when free software devs recommend using MIT-like licenses I am reminded of the meme cartoon about sheep recommending befriending the wolf.

It is almost like they learned nothing from software development trends of rent seeking private sector.

the beauty of GPL-like is that I can be sure when I help it make better I am not helping a private entity later take it over and privatize it. I want to help humanity not help private sector make money with propriety software.

when you make your license MIT-like you are not saying I am maximizing software freedom. you are saying I don’t care what happens to this software.

gross but accurate.

a bit late to the party but I was is the same boat as you so here it goes:
I have not found an option to hide them without blocking but if your issue is mainly languages that you don’t speak, in lemmy setting you can select to show only stuff that are in languages you select.
also you can deselect “undetermined” option for language to not get non-selected language for post that don’t set their languages.

snitches get stitches.

can someone tell me the is replaced with Þ ?

tt-rss and frehsrss are two different self-hosted apps. are you sure using that app doesnt mess with freshrss?

it works with freshrss self hosted?

I remember that extension but I didn’t user it because it didn’t cleanup after it self (old not needed images stayed in cache).

what is “your phone”? you mean an app? I know about text caching (I don’t know if frehsrss has an option to get original page for RSSs that has just a simple text that redirects to full page), but even inoreader that had that (if i remember correctly) didn’t have image caching.

freshrss doesn’t cache images. how do you do it offline?

it is not always women’s fault. sometimes it is the migrant’s fault. /s

sureeee. I am gonna press x.

Did you know that is the reason my country (Iran) voted no to this resolution?

because Iran backs one state that everyone lives in it and refugees have come back.

oh dont get me wrong. as I said I agree with most of your original (and now second post).

my gripe with grain was not about av1 per se. it was with movie makers that add it just because they think it is how movies should be

this is retarded to me: “Reasons to Keep Film Grain On: Artistic Effect: Film grain can add a nostalgic or artistic quality to video and photography, evoking a classic film look” because the reason is just “nostalgic” that the director has, as in if he was born after digital era, he would have an issue with it and not add it (usually).

about h264 and transparency, the issue is not that h264 can get that but at high bitrate, the issue is that av1 (as I read) can’t get it at any bitrate.

but overall I agree with you.

I even recently was shocked to see how much faster av1 encoding has gotten. I would have thought it was still orders of magnitude, but with some setting (like x265 slow setting) av1 is has the same encoding speed.

I want to agree with you and I do to a large extend. I like new codecs and having more opensourcy coded is better than using a codec that has many patents. long term patents(current situation) slows technological progress.

what I don’t agree with you is some details.

first, Netflix youtube and so on need low bitrate and they (specially google/youtube) don’t care that much about quality. google youtube video are really bit starved for their resolutions. netflix is a bit better.

second, many people when they discuss codecs they are referring to a different use case for them. they are talking about archiving. as in, the best quality codec at a same size. so they compare original (raw video, no lossy codec used) with encoded ones. their conclusion is that av1 is great for size reduction, but cant beat h264 for fidelity at any size. I think that h264 has a placebo or transparent profile but av1 doesn’t.

so when I download a fi…I mean a linux ISO from torrents, I usually go for newest codec. but recently I don’t go for the smallest size because it takes away from details in the picture.

but if I want to archive a movie (that I like a lot, which is rare) I get the bigger h264 (or if uhd blueray h265).

third: a lot of people’s idea of codec quality is formed based on downloading or streaming other people’s encoded videos and they themself don’t compare the quality (as they don’t have time or a good raw video to compare).

4th: I have heard av1 has issues with film grain, as in it removes them. film grain is an artifact of physical films (non-digital) that unfortunately many directors try (or used to) to duplicate because they grew up watching movies on films and think that movies should be like so they add them in in post production. even though it is literally a defect and even human eyes doesn’t duplicate it so it is not even natural. but this still is a bug of av1 (if I read correctly) because codec should go for high fidelity and not high smoothness.

you didn’t do the wrong thing.

what many people don’t notice is that support for a codec in gpu(in hardware) is two part. one is decoding and one is encoding.

for quality video nobody does hardware encoding (at least not on consumer systems linux this 3050 nvidia)

for most users the important this is hardware support for decoding so that they can watch their 4k movie with no issue.

so you are in the clear.

you can watch av1 right now and when av2 becomes popular enough to be used in at least 4 years from now.

“Train your replacement” USA edition.