derin
Joined 11 years ago
Joined 11 years ago
It works fine, but I'll probably switch back to Matrix's push server at some point.
Edit: With Synapse + Element, obviously.
You probably want to read the open-source software's installation instructions at: https://github.com/vector-im/element-web
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.
How about choosing something that's federated? https://matrix.org/
Been listening to it for years, it's great stuff!
Edit: Just read Arathorn's comment above, very cool - I hadn't seen that one before.
Sadly none of the rewards are updated and the flair is no longer given out; at this point it makes sense to just see it as a donation.
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.
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.
I feel like all of these apps (with special emphasis on Telegram and Signal) have almost the exact same UX and features of WhatsApp... beyond adoption numbers.
Surely one of these can take its place?
yaourt xmake
section of the install section (the Arch Linux instructions).Yaourt is no longer actively maintained and poses security risks. Just linking to the AUR package is usually enough.
You have to either make a venv for a binary or just install a package, then reverse proxy 2 ports from your http daemon, and finally also hook things up to your Postgres database. After all that it's just a matter of configuring your homeserver's config (which is large, but you can easily get support via the community for any poorly documented options)
The documentation could definitely be improved, though.