• 0 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: June 29th, 2023

help-circle


  • I replied to lazy guru below but basically I feel as though his argument about stifling innovation is a sorta win some lose some reason and allowing instances to go proprietary isn’t conducive to an open ecosystem. Basically the only way as a user to ensure you’re not inadvertently running proprietary code you might not want to run would be to host your own instance. Additionally to piggy back on that hosting your own instance might not be as feature complete due to wide spread use of proprietary or custom extensions used by other instances. A Lemmy extension betters the entire Lemmy ecosystem, a sublinks extension only betters the sublinks instance that developed it(unless they decide to contribute it back and hopefully they will)


  • I would argue that by sharing code it makes everyone more productive because you can borrow code from other places and improve on it rather than having to reinvent the wheel because the plugin you want to improve is proprietary. Anyway that aside my problem with this is on the desktop permissive licenses are fine because the user using the software can choose not to install any proprietary addon’s. In the case of the web this is now controlled by the person hosting the service. AGPL ensures that the ecosystem remains open. With a permissive license on the web the only way to ensure an open environment is to host your own instance yourself because you can’t control what any other instance does. Personally if I were a Lemmy host I’d use sublinks but I’d always ensure any changes were openly shared since I feel as though that’s the only way to be fair to your users…but as a Lemmy user I wouldn’t touch it with a 10 foot pole unless it was my own instance since there are plenty of AGPL Lemmy instances to chose from. Lastly GPL does not require you to release your code publicly. The only requirement is that your users have access to it. That means it is fully in license to sell software, the only requirement is that the people who bought your software receive code and are able to redistribute that code. Yes, that is a tad purpose defeating but the official upstream never has to be made public and ultimately people redistribute all kinds of software whether open or closed source, whether allowed by the license or not. As far as I’m concerned if the official version requires purchase most users are likely to pick that over other options. RHEL is a good example of this. AGPL obviously makes everyone visiting the site a user so it’s less able to facilitate that but I figured I’d clear up that misconception.


  • I’ve thought sublinks was really cool, a lot of which because it’s Java and I feel like modern Java doesn’t get the love it deserves…but I am worried about it not being AGPL. At least for me the fact that Lemmy couldn’t have it’s codebase closed was a large appeal and this move doesn’t sit well since it would allow instances to close source their backeds if they wanted to. I feel like AGPL is a requirement for user freedom with websites as it’s the only open source license for the web.


  • Doesn’t change the fact that it’s not illegal in a lot of countries because it’s drawn art and not abuse which is the A in CSAM. That instance is in the Netherlands where I believe Loli is legal for the reasons I’ve mentioned…anyway the point of my bluring comment was you could blur it…which is on the client level so you don’t have to see it in order to block it. I wasn’t suggesting the blur as a permanent fix. Also if you’re that worried about browser cache just use private browsing or something so the cache is immediately wiped afterwards…but whatever. Also mere fact that you know what’s on the instance means you must have seen something by accident…so it’s already in your browser cache so that’s a moot point anyway.



  • ObjC has always been a language that’s interested me in the sense that it’s very unique and it just seemed interesting. That being said I’ve never been involved in the apple ecosystem, not open enough for me so I got my mobile start on Android with Java…then realized I loved java, hated android development and never went back to mobile platform stuff LOL. I still haven’t moved to kotlin and with modern Java as it is I don’t currently plan to. Maybe I’ll give it a try if I ever try android development again but for now I’m just a user on the mobile side.