You have to make a fork aka copy and modify to contribute via pull requests. The license is fundamentally broken.
Have strong opinions, but I welcome any civil fact-based discussion.
Mastodon: @BrikoX@freeradical.zone
You have to make a fork aka copy and modify to contribute via pull requests. The license is fundamentally broken.
Your proposal seems to target the same issues as with multi-community support https://github.com/LemmyNet/lemmy/issues/818, which just got 6000€ funding from NLnet. Which seems to be a cleaner way of achieving the same goal.
Some suggested points are also against ActivityPub standard.
No audit, no 2FA, no transparency report, limited servers, proprietary clients. There are better options.
It is. Different clients handle it differently. If you note, the repository where the request is made is for lemmy-ui, not lemmy backend.
E.g. Photon shows a single item with a dropdown to expand matching posts if they were posted at the same, which is common with cross-posts on All, Local, Subscribed feeds.
And then it lists all cross-posts on individual pages in a neat list with stats like votes, number of comments, etc.
Mattermost is only source-available due to their dual licensing.
Try FreeTube.
Instance blocking only hides communities from that instance, but not users.
You are correct, I somehow got confused… It was v1.2.0 release, I updated my original post. The release didn’t even mention the license change. https://github.com/eythaann/Seelen-UI/releases/tag/v1.2.0
It’s not mentioned, but I think the compatibility layer for 1.19 releases breaks support for older versions. Ask your instance admins to update the backend.
It’s another fake open source license. While source code is public under the license, you can’t modify or republish so if the project decides to sell you are fucked.
v1.2.0 release changed the license from MIT to PolyForm Strict License 1.0.0 which removes ability to re-publish and make changes to the project. In the day when fake open source projects sell out daily, it’s a good sign to avoid this project.
The video is 2 part, first is the summary of the case and another is about why this argument from Disney is the biggest pro piracy argument.
Basically, the case is about a doctor who had a food allergy and went to a Disney owned restaurant that promised to cater to people with food allergies. The doctor asked staff 5 times to make sure they were aware of her allergies, and all 5 times they said yes. It’s literally the most straightforward wrongful death case ever. But then Disney decided they want to fuck more people over, so they made an argument that the case should tossed and move to arbitration because her husband signed up to Disney streaming service on a free trial, years ago. And Disney is ignoring a lot of other facts, like that husband is not the one suing, her estate is, he cancelled the trial before the period ended, so he wasn’t even a subscriber at the time. The streaming site has an arbitration clause, but Disney park doesn’t so it doesn’t even matter. If the case can’t go forward, it will be only because US is a corporate-owned shithole, legally it’s a moot argument.
As far as piracy, it just highlights how fucked up everything is since if the husband just pirated, DIsney couldn’t have used that argument in court. So Disney created a situation now that if you want to be able to sue them for your loved one’s death - pirate Disney. It’s the most pro piracy argument that even the biggest normies can relate to.
Not entirely about free music, but you might find Bandwagon interesting https://lemmy.zip/post/20835272
Lemmy development was funded by NLNet by the way.
EU has a similar program called Horizon Europe, which spent around €95.5 billion so far. Though it’s broader in scope, not limited to just software, but includes various open source research too.
It’s listed as a honorable mention in the article.
I think it more comes down to it not being Discord than people liking it.
Element X (Matrix client). Basically anything that offers F-Droid or open source release will have builds without built-in notifications. Play Store/App Store builds requires using native notification systems.
I’m not sure if it’s spelled out in the ToS, but there is no way to prevent pull requests on public repos, it’s a functional requirement.