Friendica VS nomulus

You might want to look into some of the Facebook-like open-source social networking programs like Friendica, Hubzilla, Libervia, or GNU Social

I think that Friendi.ca is the fediverse equivalent of FB, in the same way that Mastodon is to twitter. https://friendi.ca

In addition to what has been said, you can also use Friendica, another great decentralized alternative (server list). It supports RSS, along with being a regular social network.

facebook being whatever it is would be friendi.ca

Given the similarity to FB, what's the advantage over Friendica or Hubzilla? Both support federation with other servers and can be run as a closed community too.

The Fediverse has many different types of platforms, including video hosting on Peertube or Friendica which is similar to Facebook. Mastodon got the most publicity, but it only uses a fraction of the possibilities that ActivityPub offers.

or https://friendi.ca/

Friendica is powerful, but it's also very complex. If your primary goal for the server is simple discussions about your website, Friendica might be more than you need.

Are there any plans to set up some kind of presence in the decentralized fediverse (e.g. on Mastodon) or a community channel via the Matrix protocol? Services like Mastodon or Friendica are federated social networks licensed under FLOSS-licenses. Those "talk" to each other using open protocols like "ActivityPub" and/or "DFRN". Matrix provides similar functionality compared to Discord and is free (libre) and open source as well. Basing communication on free software can be seen as a political act. ;)

It's possible to register at the root, but ICANN has disallowed it for gTLDs (countries see ccTLDs as TLDs they "own" so ICANN isn't interested in trying to impose too many rules on them - http://ai. )

And companies have definitely purchased their own TLD for use cases that don't violate ICANN. For example:

https://blog.youtube

https://applecard.apple

https://pki.goog/

https://goo.gle

and of course https://registry.google / https://blog.google which was the domain submissed.

https://github.com/google/nomulus

That's at least 10 engineers maintaining one component. Add in SRE and product executives, you are looking at expenses in the two digit millions minimum.

The decision is definitely short sighted but somebody high up no longer wants it as a loss leader.

I don't know what to say other than that my experience here is precisely the opposite of yours. Different areas of the company? I use a LOT of third party libraries in the course of my employment, and third_party in my experience is full of legitimate third party libraries, not ones that are developed by Google.

Anyway, here's the list of dependencies for my project. There's a lot of third-party stuff in it: https://github.com/google/nomulus/blob/master/dependencies.g...

Indeed that is correct. For more information see:

https://registry.google

https://nomulus.foo (our open source software that runs our TLDs)

You can escalate to legal for edge cases, but you should be able to handle base cases yourself. As an example, I work at Google on an Apache 2.0-licensed open source project, and we have dozens of third party dependencies: https://github.com/google/nomulus/blob/master/core/build.gra...

It wouldn't remotely scale across Google if we had to escalate to legal every single time we pulled in a new dependency. Instead, there's a company-wide allowlist of accepted software licenses, and you only need legal help for exceptions beyond that.

So yes, we do have to know some basics of software licensing. It's just part of being a SWE.