PrincipleOfCharity

My problem with what you said is that it isn’t just capitalists that use patents and copyrights. Russia and China have patents and copyrights. It isn’t limited to capitalists, and saying so confuses people on what the actual issues are.

This isn’t really correct. Free Open Source Software is very much owned. It is just that the owner doesn’t charge for it, has stated that there are rules for use and modification of the software. FOSS was a clever trick that used copyright against itself. It is was a really brilliant trick, but that trick was only necessary because copyrights exist in the first place. If copyrights didn’t exist then it wouldn’t be illegal to redistribute Adobe Photoshop.

You may argue that copyrights are necessary for the betterment of society, but that is debatable. The biggest case against copyright being necessary is, in fact, the FOSS movement. It proves we don’t actually need companies like Adobe to make all our stuff and charge a lot for it.

The idea of free software isn’t political; ie socialist/communist. Free software is also compatible with free market capitalism. In a capitalist market free of coercion there is nothing that stops one from copying something then changing and/or selling it.

If you make a microwave and I buy one and reverse engineer it then I could produce and sell it just fine. Similarly, if you created a program called Adobe Photoshop, and I got a hold of the code, then I could copy and resell it. Neither capitalism nor the free market has a concept of patents or copyrights which are a political thing. Everything is free to reproduce.

Making the software free is just the logical economic price of a product with a marginal cost very close to zero. Give it away and let everyone build on top of it to make increasingly better things because that is the most efficient way to manage those resources. It’s like the progression of science. We give credit for discovery, but encourage all science to happen in the open so others can take the ideas and build on them without being encumbered.

I hope you don’t think that science is socialist/communist.

Note: After going through the trouble of writing this I became concerned that my use of the loaded term “free market capitalism” could be misunderstood so I’ve decided to define my terms. Free market capitalism isn’t a form of government. Capitalism just means stuff can be privately owned. A market is how capital is coordinated. The free refers to the market transactions being voluntary/free of coercion. So free market capitalism is the “voluntary coordination of private capital”. That definition can exist under varying forms of government which is why I argue that it isn’t a political system in itself.

Reddit is an example of a Group system where posts are associated with a group. This is the model Lemmy uses.

Twitter is an example of a Person system where posts are associated with a person. This is the model Mastodon uses.

Some services can do both; like Kbin with their microblogs and magazines.

Sounds like the Wordpress implementation uses the Person system that Lemmy does not support at the moment, but probably works on Mastodon and Kbin (idk for sure).

Then the p2p network is really the “server” and the phone is still just a client. I’m also not sure that a p2p network could be queried very well because something would have to be able to produce aggregated and sorted results. It isn’t like pulling one file from a swarm. It would be like a blockchain and the phone would have to download the whole dataset from the p2p network before running queries on it.

What you are talking about sounds kind of like the Nostr protocol. It is a distributed social network trying to solve the same problem that ActivityPub is but in a slightly different way. All the events are cached on multiple relays and the client applications query those relays looking for information that gets aggregated and sorted on the client however it wants.

ActivityPub is all about pushing content around to subscribing servers. It sort of expects the subscribers to always be online which would not work for a phone. Servers could resend missed events, but essentially you would miss every event that occurs while the phone is asleep or doesn’t have the app running.

Also, every event that occurs needs to be processed and stored whether or not you are actively looking at it so it would be a huge battery drain while it was running.

It is definitely a service best run on an always-on server with a client application in a phone just asking the server for the latest stuff on-demand.

I have also thought this is a good idea. I think that the ActivityPub standard should have a required field that lists a copyright license. Then a copyleft style copyright should be created that allows storing and indexing for distribution via open-source standards, and disallows using for AI training and data scraping. If every single post has a copyleft license then it would be risky for bigtech to repurpose it because if a whistleblower called them out that could be a huge class action suit.

A good question is if a single post can be copyrighted. I think it could. Perhaps you would consider each post like a collaborative work of art. People keep adding to it, and at the end of the day the whole chain could function as a “work”. Especially since there is a lot of useful value and knowledge in some post threads.

You can do that, but there are a couple of things to keep in mind.

Different apps may only be compatible with certain database products and versions. I could be a real pain if you have to spin up a new version of a database and migrate just for one service that updated their dependencies or have to keep an old database version around for legacy software.

If you stop using a service then it’s data is still in the database. This will get bloated after a while. If the database is only for one service then wiping it out when you are done isn’t a big deal. However, if you use a shared database then you likely have to go in and remove schemas, tables, and users manually; praying you don’t mess something up for another service.

When each service has its own database moving it to another instance is as easy as copying all the files. If the database is shared then you need to make sure the database connection is exposed to all the systems that are trying to connect to it. If it’s all local then that’s pretty safe, but if you have services on different cloud providers then you have to be more careful to not expose your database to the world.

Single use databases don’t typically consume a lot of resources unless the service using it is massive. It typically is easier to allow each service to have its own database.

I’m confused. Isn’t the commission that is paid just a cut of the profits from sales? The 85% not paying commission would be because their app is free. Apple’s argument is that they are providing a huge platform and infrastructure for app developers; many of which are utilizing it for zero cost (except the annual $99 developer fee).

If someone then uses that infrastructure to make money then Apple takes a cut of either 15% or 30% to help sustain the whole thing. Those numbers are argued to be too high although they are basically in-line with the mark-up of most goods and services.

The real complaint is that Apple doesn’t allow alternate app stores that would compete, and theoretically push down the commission to whatever the free market determines is reasonable (and presumably below 15%). Apple, of course, argues that they do it for safety purposes. One way to offer lower commissions is to have less strict screening processes to save money. This could end up being a race to the bottom of quality which may not really benefit users.

I was like, “Portainer costs money? When did that happen. I thought it was open source.” Granted it has been awhile since I used it.

You want to check out the Community Edition. Here’s their Github.

Is the hash map immutable? If so, look at the rust-phf crate.

Interesting thought that is definitely worth considering. I used the term “Reddit refugee” in reference to my status. I am a little hesitant to shrink language by turning it into a competition or making words political. Refugee legitimately has multiple definitions, and the appropriate course of action would be to qualify the term; political refugee or Reddit refugee.

This sort of concept leads to all sorts of other similar issues. If I am having difficulty making it through a hike and I comment that I need to just “soldier on”, does that make light of the sacrifices of real soldiers who are dying all over the world? Should most people be disallowed from saying that they are starving because there are people in the world who are actually starving and not just hungry? Is it insensitive to say that I’m struggling to make it through the day at work when others, somewhere, are struggling to even stay alive?

For what it is worth, I’m okay with “refugee” by itself implying “political refugee”, and requiring other forms to be qualified.

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.

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.