Hi @amyblais,
I could post this on the feature idea forum, but I can’t figure out how the signup on the site works. When I click on ”Create an account”, I get a prompt to verify my email address, and having done that, a page saying ”Go back to Production to finish logging in”. I don’t know what ”Production” is, and at no point was there any actual way to set up a password, so I can’t log in.
A ”Mark read” choice in push notifications about new messages, as seen in many IM apps, would be handy in Mattermost Mobile too. Currently the message can only be marked read by tapping the message to open the app (which is slow).
Have a ”Mark read” option underneath the expanded notification.
No ”Mark read” option, only ”Reply”.
As of this writing, push proxy v5.25.0 was released 5 days ago, but the published assets on Github only include the source code.
wget https://github.com/mattermost/mattermost-push-proxy/releases/download/v5.25.0/mattermost-push-proxy.tar.gz
Receive mattermost-push-proxy.tar.gz
404 Not Found
I have the same issue. I’m doing this in a Linux container (Ubuntu 20.04 inside Ubuntu 20.04), but like matthaios-easy-bi, I’m using npm run build:android to build (as per documentation). This has worked up until 2.0, but with 2.1 it always fails due to non-existent org.webrtc. Manually running npm install prior to npm run build:android makes no difference, nor does node node_modules/react-native-webrtc/tools/downloadWebRTC.js (although it does seemingly download the package successfully).
It’s not Mac-only either, I have the same issue trying to compile v2.1.0 on my Linux PC.
V2.0 had issues too, but FTBFS wasn’t one of them.
Vastaa viestiin sen kontekstissa (Mattermost Discussion Forums)
Hi @hmhealey,
Yes, it’s mainly about expectation. For an actual use case, I noticed this when mentioning an IRC channel name, which became a long, distracting and useless hashtag link, exacerbated by agglutination and multi-word hyphenation typical in Finnish, (e.g. #channelname-irc-kanavalla). I tried to make it less distracting by editing in a preceding backslash, only to discover that it didn’t work here.
There is no way to escape a word-starting hash character (#) in plaintext.
In MM 7.3.0, post this, verbatim: \#anything
#anything
Workaround: instead of ”\#anything”, post this: #anything
Using backticks (`\#anything`) also works, but obviously the word then gets formatted as code and not plaintext.
This is mainly an issue of inconsistency and surprise: backslash works to escape most other special formatting, so I’d expect it to work here too.
I’m getting these unrequested emails from my self-hosted instance, with no apparent way to disable them. This is bad, bad behavior.
Host an instance running Mattermost 6.6.1. Leave it ”collecting a bit of dust”.
Not to get spammed with unwanted emails.
Keybase key for verifying the tar archive’s signature is missing.
Get a public key to verify the tar archive’s signature.
404 not found
Note the literal use of example.com here; don’t replace it with an actual, working MM instance URL.
# /usr/bin/sudo -u mattermost /usr/local/bin/mmctl auth login http://example.com --name example --access-token 123456890abcdefghijklmnopq`
# echo $?
For a non-zero exit status to be printed.
The exit status is 0.