101–110 of 319 posts
Earlier quoted context omitted.
Can also mean annoying. As a general recommnedation, before naming a project or company something, always search whether it means something bad in the top 10 most spoken languages. For portuguese/spanish, there is always a high chance of being a slang that is NSFW
There's a Hyundai car whose name literally means "pussy" in Portuguese and Galician x) It's marketed as something else in those territories.
The fundamental problem with replacing Slack is network effects. Your coworkers and customers already use Slack. It works well enough. You can choose to switch your company away, maybe, but what do you do when vendors want to connect over Slack? Imagine if email was owned by a company? Edit: W̶e̶ ̶r̶e̶a̶l̶l̶y̶ ̶n̶e̶e̶d̶ ̶a̶n̶ ̶o̶p̶e̶n̶ ̶p̶r̶o̶t̶o̶c̶o̶l̶ ̶t̶o̶ ̶b̶u̶i̶l̶d̶ ̶o̶n̶.̶ We really need an open protocol to win…
But the point here is that you don't want the network effects. You want a chat server for people you know and explicitly invite, for a specific purpose, under your control. Maybe you want the data to never leave your colocated box and your VPN, and your server to have no public presence at all. There are things that Slack cannot easily offer.
Discord is winning because it's a dozen different communities in one single convenient client. Want your new chat platform to win? Convince all those communities to switch.
What's the rationale for the dual licensing? It looks like the Go backend is AGPL but the TypeScript frontend is Apache 2.0. Why not keep it all AGPL?
Backend under AGPL prevents someone hosting it as a service. AGPL specifies that hosting _is_ distribution. Therefore, anyone hosting it must do so with public code. This provides a soft form of exclusivity to run their own Cloud. A frontend, permitting customizability, white-labeling, and so on, makes more sense to be more permissive. Grafana is a solid example to illustrate why. Moved from Apache to AGPLv3 in 2021…
Couldn't help but smile because "chato" in portuguese means "boring", and this seems very easy to set up and use. Here's to more boring software! :)
Can also mean annoying. As a general recommnedation, before naming a project or company something, always search whether it means something bad in the top 10 most spoken languages. For portuguese/spanish, there is always a high chance of being a slang that is NSFW
Earlier quoted context omitted.
Backend under AGPL prevents someone hosting it as a service. AGPL specifies that hosting _is_ distribution. Therefore, anyone hosting it must do so with public code. This provides a soft form of exclusivity to run their own Cloud. A frontend, permitting customizability, white-labeling, and so on, makes more sense to be more permissive. Grafana is a solid example to illustrate why. Moved from Apache to AGPLv3 in 2021…
[flagged]
I don't think it does that, it prohibits them from modifying it and then using that mod to fork users away from the original software, aka https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
Earlier quoted context omitted.
Backend under AGPL prevents someone hosting it as a service. AGPL specifies that hosting _is_ distribution. Therefore, anyone hosting it must do so with public code. This provides a soft form of exclusivity to run their own Cloud. A frontend, permitting customizability, white-labeling, and so on, makes more sense to be more permissive. Grafana is a solid example to illustrate why. Moved from Apache to AGPLv3 in 2021…
[flagged]
I’ve known Hendrik for years, and he is one of the most talented developers I’ve ever met. I’m confident this project will become successful very quickly. Beyond the project itself, what fascinates me most is how he single-handedly developed it by leveraging agentic coding.
[flagged]