Getting used to it. Some thoughts here https://lemmy.ml/post/53408086/28100807

Like most projects, I use AI for most of my work these days. It’s a tool, which helps me plan, research and code new ideas/features. It makes a lot of my work easier. I share the concerns about yolo/vibe-coded slop, but it’s who wields the hammer that matters. I’ve been a software engineer for 20+ years and you can check from my Github history that I’ve been doing this way before any AI hype. The idea and execution is 100% me. I’m building something I want, use, and care about myself.

I know I won’t change your mind here, and that’s fine. Don’t use it. But you might want to reconsider calling everything that uses AI garbage. By that standard you won’t be able to use any tech at all anymore. Chill out, touch grass and enjoy your day!

I probably don’t. I know copyleft vs permissive can be heated debates and I don’t have a very strong opinion. My decision and reasoning is mostly based/aligned with https://shazow.net/posts/permissive-vs-copyleft/

At the current stage, and as solo dev, I don’t believe that either licensing is realistically going to have any meaningful difference. There are plenty of cases where copyleft didn’t prevent capture. And permissive projects that thrived above corporate versions.

But I’m curious to learn and appreciate the feedback. Can you elaborate? What’s the main concern. What assurances, or protections do you hope to get from GPL? Is it about using the project, or contributing to the project?

Thank you! Let me know when you get to it. Always open to hear feedback :)

I understand the concern, but MIT has been very intentional to signal the opposite of what you’re worried about. Paperweight runs fully local. Everything works without any back-end or external services. No one can turn this into some paid SaaS to lock features. It already passes the walk-away test and there’s literally nothing to rug and if the project ever goes into a direction you don’t like you don’t lose access or need anyone’s permission.

While GPL theoretically gives you the same opportunity, I feel like it adds some overhead and potentially locks out genuine contributors.

And especially in the age of AI, code is cheap and if someone wants to build a closed Paperweight, the license is not going to stop them.

Fair, thank you!

That’s fair. I’m still experimenting with pricing/licensing models, so appreciate the feedback. To be clear, the license grants you permanent use and at least all updates, including V1 which is documented on Github. Not making any promises what’s after yet, because in all honesty. I don’t know yet what a V2 or other features would look like. Just trying to be transparent on what you’re getting right now + upcoming updates. We’ll see what’s after, and open to ideas

No plans on a Docker compose for now, but feel free to submit an issue. RE licensing, there’s some discussion on it below. FOSS describes software licensing, which is all MIT. There are 2 features “gated” behind a license check, which supports development and gives the convenience of a ready-made build (which have costs involved). But all code is open, and you’re welcome to modify/fork out if you prefer to run your own.

Thank you! Appreciate that. Would love to hear your thoughts when you get to spin it up!

Thanks!

Sure, like most projects I use AI assistance a lot for most of my work these days, ngl. Its helps me plan, research and code new ideas/features and makes a lot of my work easier. Having said that, I fully understand and share people’s feelings about yolo, vibe-coded slop. I’ve been a software engineer for 20+ years. AI helps with a lot, but also feels like the honeymoon phase is wearing off actually. It doesn’t give me the joy of building stuff. I still test, review and ship everything myself. You can check my Github history that I’ve been doing this way before recent AI hype.

Either way, the idea and execution is 100% me. I’m building something I want, use, and care about myself. Whether I’ve used AI is not too relevant, imo. It’s that all alternatives have been caught selling your data (Unroll), heavily rely their centralized services or require you to give up your data in order to remove it. Which is ironic. Paperweight is the only tool I’m aware of that does this entirely local and is open-source.

P.S if its quality you’re worried about, Paperweight has been audited through Google’s CASA assessment and Apple’s developer verification (admittedly, not a super high bar).

Exactly. Thank you!

Hi, nice to see you here! Would love to hear your thoughts. And thanks for standing up in the comments. Much appreciated :)

Correct. But all code is there, so you can fork them out yourself if you want.

Thanks for the reply! And good question. Yes, all code, including all paid features are open source too. Not just open core. There’s nothing proprietary. Some of the paid features are gated behind a license check, but it’s all part of the same repo and MIT licensed. It’s all there to inspect or fork if you want. The perpetual license however helps support development and gives the convenience of a ready-made build.

We actually moved recently from GPLv3 to MIT to be fully permissive.