PrincipleOfCharity

joined 2 years ago
[–] PrincipleOfCharity@0v0.social 5 points 2 years ago (5 children)

I have recently been thinking that copyright and patents should be enforced until the creator made back their money plus a set profit; like 30%. The reason for this is that it makes it similar to physical products which are often sold at cost plus some profit; usually around 20-50% depending on competition.

Doing it this way has some interesting side effects.

  • It puts creative production on par with physical production.
  • It requires transparent accounting.
  • It covers the hard work required to develop something while not giving windfall profits to minor discoveries that just piggyback off the work of others.
  • The more that is charged for a protected product, the quicker it enters the public domain. If you needed to keep a copyright for a long time then you wouldn’t charge a lot for it which is still beneficial to the public.

There could be some nuances. I’d imagine that there would be some threshold amount that covers smaller items. Maybe everything is covered for the first $200,000 or so. If one was claiming more than that for R&D then they would have to produce accounting demonstrating that amount. That way smaller creators aren’t necessarily burdened like a large corporation that does R&D for a living would be.

Obviously numbers could be fudged, but with it could be set up so that is difficult. Accounting could be adjusted. Perhaps quarterly or yearly reports have to be made on which projects money was spent on. That way there would be a paper trail that would make it harder to pretend like more work was done on something than actually was.

Just a thought.

I’m not super concerned. It’s been a little over a week since stuff hit the fan. Contributors need time to learn the code base. People are starting to help with the easy stuff, but the two main devs still need to check everything because they are the only ones that can understand how those changes affect long term visions. Also, the urgent fixes are all somewhat-breaking changes which is why it’s looking like the next release is going to be 0.18 instead of 0.17.5. It makes sense to get as many urgent breaking changes in as they can before publishing, and it’s only been 8 days since the last release to identify, code, and test.

[–] PrincipleOfCharity@0v0.social 1 points 2 years ago (1 children)

For personal projects this is fine, but I’m curious why you feel the need to have every crate be the newest? Once you have it compiling, why upgrade dependencies at all unless you have to? Compiling a new binary is way more work than just running the one that is already compiled. You talk about minimizing build times with this method, but it isn’t clear why recompiling at all with newer dependencies is beneficial.

Theoretically, every update to a crate is better than the last, but sometimes it’s just adding non-breaking features that you weren’t using anyway. You could just check crate updates every once in a while looking for performance gains or features you would like to make use of.

[–] PrincipleOfCharity@0v0.social 3 points 2 years ago* (last edited 2 years ago)

It sounds like you are referring the federation. When something is posted to one server, that server has to then propagate it to the other servers. That process is not instant; especially in large servers. In fact, right now with the Lemmy software it is a bit of a bottleneck that will be worked on soon. issue/3230

Another possible reason for this is caching. Browsers and servers save pages a lot to reduce load and make things go faster. That means that I sometimes you can see an old version of a page for a bit until it refreshes. Set correctly, a cache shouldn’t get too stale, and using the browser refresh button could fix it.

Not sure if this is the same problem, but it has been noticed that passing messages between federated instances has been hampered by the way the "worker threads" are currently been done. The big instances are essentially getting overloaded with outbound federation work. Solutions for that are in the works. issue/3230

Might be the only video game cover he gets on at this rate.

[–] PrincipleOfCharity@0v0.social 2 points 2 years ago* (last edited 2 years ago)
  • 100 searches: Free
  • 300 searches: $5/month
  • 1000 searches: $10/month
  • Unlimited: $25/month

Going over is 1.5¢ per search.

[–] PrincipleOfCharity@0v0.social 3 points 2 years ago (1 children)

It is not super clear whether Christian would have sold Apollo to Reddit. I know he mentioned them buying it from him for $10 million, but he has also said that he wouldn't sell Apollo to someone who was just going to mess it up because he cares about it. Reddit would have definitely made it a shell of what it currently is.

He was pretty much asked this question in a recent interview.

NP: If they’d offered to buy the app from you, would you have sold it to them?

I guess it depends on the stage. I mean, I’m just some guy, so if the number was high enough, sure. Absolutely. At the stage where it was clear that they weren’t interested in having third-party apps around anymore, just because of the pricing and some of the API changes around explicit content or whatnot, if that was the point where they said like, “That being said, we would like to maybe work with your user base or take your user base and figure out a way to make them happy in the context of the official app and work with you and your app through an acquisition,” I honestly would have listened to that.

Prior to that, it would have had to have been a pretty good number, just because I love building Apollo and being so in touch with so many people through the community. It would have to be a big number, losing such a big part of your life and what you do every day. There’s an emotional penalty to losing that is hard to quantify with money, as superficial as that sounds.

view more: ‹ prev next ›