To add onto this, I have been using Libreoffice Online or Collabora Online for the last 4 years or so. I used to compile LOOL myself but eventually I just switched over to using the Collabora Online Development Edition that Collabora releases. I am using it integrated with Nextcloud.
I enjoy using it and it has been a life savior for the times I need to work on a document with someone else since I can just send them a share link for it. The fact that it uses leaflet which is meant for maps does mean that the latency to the server matters quite a lot to experience but I don't mind that much, personally, with my not great 120ms RTT to my server.
Element's primary paid service is Element Matrix Services [1] which is exactly for that. They run a Matrix server for you, optionally on a domain that you provide.
A change in your repo does not need to result in an import path change if you set up vanity URLs for your import path. For instance, all my go libraries use the import path of gomod.garykim.dev even though the repos are actually hosted on GitHub. That means if I ever change to self-hosting, for example, I just need to update some of the meta tags on the gomod.garykim.dev website to change the repo location.
I've been running a Matrix server for a half a year and I have not run into any problems. The main thing that surprised me was how much database space Synapse took on my server but that was an easy enough issue to deal with. That may also have to do with the fact that I'm in some of the most complex rooms that exist on Matrix.
I tried running a XMPP server for a bit but that was a rather frustrating experience between getting it to integrate well with the rest of my infrastructure, figuring out what configuration was needed and what XEPs were needed, what clients had the features I needed, what clients supported the OSes I used, and spam. To be fair, the reason I thought setting up Synapse was extremely easy may have been because I did it with almost twice as much experience with devops than I had when I tried to setup the XMPP server.
Regarding registering with a central authority, you're probably thinking of identity servers. Identity servers are used to provide 3PID (email/phone number) -> Matrix ID mappings and are completely optional. There have been attempts to decentralize that as well but for one reason or another, no good way to do it has been found. At least the source code of the identity server is open source[1] so there is that.
Otherwise, to set up a Matrix server, you simply have to either set up a json response from "/.well-known/matrix/server" or an SRV record on DNS that points to the Matrix server.
I also have mine set up though without a default_policy so I can have the server forget stuff in my bot control rooms cause they get cluttered with useless stuff pretty fast.
DCOs don't give copyright ownership to anyone else or even any more rights to anyone else. It is simply a declaration that you have the permission to license the code you wrote under the license you're giving it for.
I'm using a .dev domain name as my primary email address and in the last few years of using it, I have only run into one website that did not support it properly. I ended up using my .com email alias for that website.
Adding on to this, I personally have improved versions of open source software projects that I just forked for personal use because pushing the improvements upstream would mean having to sign a CLA which is something I am completely unwilling to do.
It is possible that the lack of useful contributions is due, in part, to a CLA being required.
It is important to consider, though, that the reason flying is extremely safe is because we do freak out about everything that goes wrong in aviation. Commercial aviation is one industry in which there is a strong correlation between safety and profitability so the industry does freak out over every problem.
Of course, it's a balance, and the balance that commercial aviation has found is heavily focused on safety.
I lived in Singapore and while I was there, I used MyRepublic's mobile plans. The plan I was using was $24(SGD) a month for 17G. Rarely had connectivity issues though for the most part, I stayed in the more populated areas so I may not have had the same connectivity issues as you.
One of the nice things was that each telco would keep changing their plans to be better and better so it paid to pay attention and change plans whenever a better one came along.
> Main guy commiting 600k lines and the second most committed guy 450 lines.
> So yeah, it wouldn't take him a whole lot of time if he really wanted to change the license by removing all the others' commits and rewriting it by himself.
Good point. I may try to get involved in its development as well to spread that out a little more.
> Also, what does AGPL has anything to do with keeping the license open sourced?
The AGPL requires that any code linked to it also be distributed with an AGPL license (the difference from the GPL being that hosting over a network counts as distribution). Every part of the project is technically linked to itself so if someone makes a change, no one else can use that change in the project under a different license.
At least for me, the fact that it is purely licensed under the AGPL and that the copyright is owned by multiple people makes me far more comfortable with using it. It's a guarantee that the project will remain open source so I don't have to worry about suddenly being in a situation where I have to migrate away because the company or person decided that they don't want to have this be free and open source software anymore.
I guess, to a certain extent, that's because I'm an individual, not a company, and one that tends to open source pretty much everything they write. This is the same licensing that I use for pretty much all my projects (AGPL with no CLA).
This is actually the situation I'm in. Google Play Services are disabled on my device so I cannot use any YouTube premium features anyways.
If there was a way to pay for YouTube premium and make the money go to the creators I watch while using a FOSS client like NewPipe, I'd be willing to pay several more times the current price of YouTube premium for that.
I believe the F-Droid version is currently one patch behind. You can actually add https://archive.newpipe.net/fdroid/repo in F-Droid as a repository and you'll get the updates for NewPipe a lot faster.
I actually ended up going down a different route and created my own F-Droid repository for NewPipe and a couple other apps so I could get faster updates for them and I trust the upstream developers.
I'm a Gitea maintainer and I still do most things on GitHub rather than my self-hosted Gitea instance because a lot of open source projects as well as the people willing to help with them are there. Overall, your project tends to get more attention and contributions if it's on GitHub.
Now, we can discuss about whether or not that's a good thing and the quality of the kind of contributions you tend to get because of the lower barrier but GitHub, at least currently, still has a place in the workflow of a lot of people.
What you propose would also be really awesome. A feature like this in Gitea could be really nice. If you'd like, you can open an issue on the Gitea issue tracker [1] for the feature.
Collabora Online is Collabora's branded version of LibreOffice Online. They also have a version they call Collabora Online Development Edition that you can find here for personal use: https://www.collaboraoffice.com/code/.
Both LibreOffice Online from Docker Hub and Collabora Online Development Edition have a configured limiation of 20 connections for 10 different doucments so personally, I'd recommend building from source. You can find the source code for LibreOffice Online here: https://git.libreoffice.org/online.
I suspect the lack of a stable version of LibreOffice Online is intentional as a way to try to drive more business towards companies such as Collabora.
I don't know how I would live without that. I tend to make rather verbose branch names and typing it all out stuff like push would take forever.
Though, you have a much more fun solution.