It is defined by the instance's admin generally.

Try to ask your IT guy, maybe he'll know more about this!

I see the only use of 3PIDs in a professional setting where people have to find co-workers using emails or internal phone numbers.

In my opinion, it is really useless for anyone else.

I've never used the feature on Matrix because as you say, it doesn't really apply. Matrix (or really Element here) doesn't require you to use an identity server at all, so I don't really think it invalidates the protocol in a meaningful way.

Matrix is not.

You know that the identity server is not mandatory and is only useful in a professional setting right?

If you really want to, you can host it yourself.

without one clients will not be able to look up user IDs using 3PIDs, so its relatively important. hosting it yourself means having to email or message "us" in order to federate it.

So don't use a 3PID to add someone, use their MXID. It's a unique, global identifier and is similar enough to an email address.

There's also a Matrix URI specification in the works (https://github.com/matrix-org/matrix-doc/pull/2312). Once that lands, we should start seeing support for Matrix URIs in applications. This will allow applications to also start recognising MXIDs and converting them into working links, which will in turn help with people's recognition of the MXID.

I've been using Matrix for three years I believe and I can't remember a single time when I needed to use 3PIDs.

does matrix store anything in the server or is this really p2p? can this be a good replacement for say, telegram?

Yes, this is really sad to see that much people in the OSS scene using nonfree ways to communicate.

At least, IRC had open-source servers and clients but in my opinion, it's too old nowadays.

OSS primarily uses a non-free way to host source code (GitHub), so it's not much different to use Discord.

So what if Github itself is not OSS? The technology behind is already open source and decentralized. You can switch to a Gitlab instance with just a few mouse clicks while also migrating your issues and pull requests.

I don't believe issues or pull requests are part of the Git repo. If there is a way to migrate them it would involve some GitHub API which could be shut down.

The commits in pull requests are part of the git repo, in that they can be fetched from the repo's remote. The comments are not.

as said; the issues are not part of the repo.

as much as many projects could use a clean slate here, i dont think the burden of migranting them manually or the act of just dumping them is realistic.

> So what if Github itself is not OSS? The technology behind is already open source…

So is much of the technology behind Discourse.[1]

[1] https://discord.com/open-source (click on "OS Libraries")

And it's sad to see.

There are at least a few different "OSS scenes" that have different priorities. More principled, idealistic developers fall under a different category than more pragmatic ones, so it should be no surprise that they use different tools.

Using non-Free tools has been shown to be distinctly non-pragmatic under a wide variety of considerations.

A better term would be something like "Tied programmers" or "Dependent progammers". Maybe "sharecropper progammers"?

"Sharecropper programmers" might be an accurate way of describing developers for Apple platforms, but that's not what is happening when people use GitHub and Discord to work on open-source software. They can easily move their Git hosting and chat to another platform—they just choose to use the popular, coincidentally non-OSS, platform for its pragmatism.

A large base of existing users, easy onboarding, and good visibility makes a big difference for many OSS projects. Using a self-hosted Git hosting system and mailing list is a lot of work—and it adds a not-insignificant barrier to entry for potential contributors. What issues exist with popular, proprietary Git and chat tools that make them unsuitable for OSS development?

What are some of the considerations you're thinking of where using a popular option is not pragmatic?

> nonfree ways to communicate

Does that include Hacker News?

It does, currently waiting to be either invited to lobsters or for the registrations to open again.

Check out federating reddit -like service lemmy.ml: https://dev.lemmy.ml/

> Yes, this is really sad to see that much people in the OSS scene using nonfree ways to communicate.

And the reasons are entirely understandable:

- you don't have to run your own infrastructure

- you don't have to run your own protections against fraudulent activity, DDOSes, bots etc.

- you don't have to worry about availability on any number of platforms, including mobile

free software as a hosted service is a thing.

It is a thing, is there enough of this thing? Is it free? Do these hosted services provide the infra and protection? Do these hosted services solve the issue of the dearth of clients for these services?

And if you look at hosted services like IRCCloud, it turns out they are not that different from Slack/Discord: closed source, for full range of capabilities you need to use their apps.

You need to change the homeserver url to another one. There is a list here https://www.hello-matrix.net/public_servers.php

Also what do you mean by "That are always full and require invite" ?

That list is unfortunately no longer maintained and quite outdated. https://publiclist.anchel.nl/ might be better.

Thank you both for highlighting my point.

I didn't went into details since I'm relatively new to Nix.

I'll make a follow-up in more time (some months) and go in more details!

Not a comment on your post but the NixOS ecosystem in general

Probably should've used the word "dislike" instead of hate. Apologize.

As someone whose been using Nix for almost a year (not NixOS as long) I struggle that there is zero advanced write ups.

Could be because it's the same experience which is good news.

But there's a series of advanced concepts that deserve more love: custom Nix cache, distributed building, remote deployments , NixOps, writing eloquent derivations, secret management (please!), how to sanely use vim_configurable etc...

I spent a long time documenting the Maven (Java) documentation and recently had it approved.

Seems really useful, thanks for the links!

Seems interesting, thanks for the link!

I see, thanks for the message! I'll make a small correction.

Edit: Correction published!