Gitlab and Element's website structure is different. element.io is the site for the managed product, so even their "on-premise" installer is meant to be used in a commercial relationship. For install docs you'd probably have to purchase their product (which isn't available freely).
TLDR, check out the project, run `yarn install`, then edit the config file, then `yarn build`.
And, yes, that is all there is to it. It's significantly simpler to deploy than GitLab.
Finally, you keep mentioning self-hosting; you _can_ just use a non-self hosted application like the downloadable version of Element, SchildiChat, Fluffychat, or any other client.
No reason to bring hosting into the mix for the client, if that's causing concern.
You yourself say in a different comment that you are currently assessing Element:
https://news.ycombinator.com/item?id=34779070. Either you have a formed opinion Matrix, or you don't. Which one is it?
You keep saying Element instead of Matrix, and obviating the whole Matrix ecosystem. Matrix protocol has several server implementations, and many more things around:
https://matrix.org/docs/projects/try-matrix-now
I'm fine with Matrix, but I'm not seeing the people around me moving to it, even with a more friendly solution like Element. It's already hard to make them use Signal just because they want users to remember a pin...
This is NPR One, no? That's why I've been using it - it gives you a nice steady stream of NPR's programming and outside podcasts, randomly sampled at first, which in time starts preferring your favored content (which it learns by you "liking" content).
They used to include a blurb about it on all NPR podcasts. I think they removed it because local stations were complaing that they were diverting their listeners away from the local station to a centralized app. So it’s been more low key since then.
Matrix[1] is trying to solve that issue, I'd highly recommend looking into it. I actually pipe most of my various "chat" networks (including WhatsApp) into it via bridges[2].
As you said, we in Europe are kind of forced to have WA installed, but at least you don't have to use it as your primary client if you don't want to. You can even deploy it to an Android VM and go completely headless, if you feel the need.
> As you said, we in Europe are kind of forced to have WA installed, but at least you don't have to use it as your primary client if you don't want to.
Haven't used WhatsApp for months and then only for a few days to talk to someone from US.
My friends were heavy WhatsApp users but we changed one group after another to Telegram after WhatsApp were brought.
Telegram is far from perfect though so I hope to move to Matrix within a few months.
An incognito browser would ignore all client-side cookies, so the Slack web client would not try to - say - resume a previous user's session or re-use any previously saved data.
Likewise, incognito mode will also ignore most cached web content, meaning all assets on the Slack web app will get loaded again from scratch. This "clean state" start could, theoretically, get around issues with old - potentially incorrect/outdated - assets being loaded, even though that really shouldn't happen under most circumstances.
