# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 10
# self = https://watcher.sour.is/conv/vyp5qoq
[Feedback on why I didn't choose Mattermost (lack of OIDC) · mattermost/mattermost · Discussion](https://github.com/mattermost/mattermost/discussions/24451) -- My discussions/feedback on Mattermost's decision to have certain useful and IMO should be standard features as paid-for features on a per-seat licensed basis. My primary argument is that if you offer a self-host(able) product and require additional features the free version does not have, you **should not** have to pay for a per-seat license for something you are footing the bill for in terms of Hardware/Compute and Maintenance/Support (_havintg to operate it_).
[Feedback on why I didn't choose Mattermost (lack of OIDC) · mattermost/mattermost · Discussion](https://github.com/mattermost/mattermost/discussions/24451) -- My discussions/feedback on Mattermost's decision to have certain useful and IMO should be standard features as paid-for features on a per-seat licensed basis. My primary argument is that if you offer a self-host(able) product and require additional features the free version does not have, you **should not** have to pay for a per-seat license for something you are footing the bill for in terms of Hardware/Compute and Maintenance/Support (_havintg to operate it_).
[Feedback on why I didn't choose Mattermost (lack of OIDC) · mattermost/mattermost · Discussion](https://github.com/mattermost/mattermost/discussions/24451) -- My discussions/feedback on Mattermost's decision to have certain useful and IMO should be standard features as paid-for features on a per-seat licensed basis. My primary argument is that if you offer a self-host(able) product and require additional features the free version does not have, you **should not** have to pay for a per-seat license for something you are footing the bill for in terms of Hardware/Compute and Maintenance/Support (_havintg to operate it_).
@prologic wow…
I really don’t see the train of thought of making something so simple to implement (specifically SSO) a paid “enterprise” feature to justify a price point.
Hell, I could probably implement the feature in a couple of hours and I have very limited development experience 😅
They could also re-evaluate the price point then add more features to the paid plan (that ideally add much more value than SSO) and then raising the price when it makes sense to. So many companies do this right now anyway.
On the whole paid features for self-hosting, I ran into this issue myself when implementing a SIEM on my network. I initially implemented the Elastic stack (Elasticsearch, Logstash, Kibana) but then they go ahead and lock things like creating detection rules and sending alerts via anything other than email a paid feature 🫠
I’d be much happier if the industry switched to a one time self-hosting service with no support, with the option to purchase support licenses at a monthly cost.
@prologic I had and have to work with Mattermost and RocketChat. Their web UIs pretty much feel like clones to me and they also both suck in my opinion. The threading view just doesn't really work out in my experience. To be fair, I'm just a simple user, it might very well be, that these instances are just configured in a weird way, no clue. But I'd stay away from these two softwares if I could help it. Since you seem to like Mattermost, you might want to have a look at RocketChat.
@prologic What I did as a work around for mattermost was hijack the gitlab oauth login with my own auth server.
@prologic What I did as a work around for mattermost was hijack the gitlab oauth login with my own auth server.