This is a known issue (tracked at https://bugzilla.mozilla.org/show_bug.cgi?id=2007074, as mentioned by a previous comment). A fix has landed in Thunderbird Daily a couple of weeks ago, and should be released in Thunderbird 154 which comes out next month.
> At present, EWS is our best way to enable support for both Exchange Online and on-premise installations.
> Graph API has been considered and may be considered again in future, but it currently provides narrower support than EWS and lacks some functionality for desktop applications. Even with the announcement that EWS support will be removed for Exchange Online, it's still valuable in the short term for enabling access for a wide userbase and in the long term for supporting users using on-premise installations.
Are you looking for a full stack developer or a developer specified in backend work? From the look of the ad on your website it looks like the former but the title is pretty confusing to me.
I've been using a Fairphone 3 with /e/OS for about 6 months now, and I've generally been quite happy about it Hardware-wise it's great; sowftware-wise it's not quite there yet (I've seen a few audio bugs, also the app store is very buggy and relies on a questionable third-party source for APKs for which /e/ offers no support (when reporting a bug with an app search causing an error message I've been advised to use Aurora instead, which isn't a great thing to hear) and which can have several weeks of lag on app versions, and also (bis) the tech support isn't there yet in terms of being accessible to non-tech people), but it's definitely going in the right direction!
It sounds to me from this article like the case was dismissed because the plaintiff didn't sue for the right thing, rather than specifically the GPL being judged inapplicable.
Some countries can have blurry lines between companies and non-profits; in this case, Matrix.org is a Community Interest Company in the UK (https://matrix.org/foundation), so I assume that'd apply to it as well.
> How to make this request sound convincing? Block any attempt of viewing a page until whitelisting is applied.
Well, that's the best way to push people suddenly decide they're not interested in your content anymore and instantly leave the website. This otherwise interesting post unfortunately brings no durable solution, nor one that respects user and their consent to privacy. I'd even say that first one is an infringement of GDPR, since it states that lack of consent to a feature that's not necessary to run the service can't deny access to the said service.
Also, French media tried this specific solution way earlier (and way before the GDPR applied) and they had to roll that back because that was actually causing the size of their online audience to decrease.
I'd say they're quite high because not being "yet another IM thing" but rather becoming the way to bring all comms togeter is one of Matrix's core missions.
Of course it's not there yet, though it's quite likely to get there in the future.
> Plus, XMPP can be used for great amount of stuff non-IM related, while Matrix seems very focused around its IRC-like use case
I don't really agree here. While Riot is focused on a IM use of Matrix, Matrix itself is open enough to be usable in any use case requiring a payload to travel from A to B. You could think of Matrix use in IoT, social networks, forums, etc. Some people even made a working PoC of a blog using Matrix, and I heard some others are also working on building a system to bypass information censorship using Matrix as its only back-end.
I don't know XMPP enough to state which spec is wider than the other, but what I know is that Matrix isn't limited by what Riot or other Matrix-based IM clients can do.
Is it only me or does this website (supposed to help me "Find something to watch tonight") mainly gets me trailers of movies that'll get release in weeks or months?
Yep. You might be able to configure Graylog to alert you when an extractor fails, but I didn't go this far (as I said, we switched to another solution since then).
I'm not saying that's the best way to do it, just that it's how we did it back then. Of course there might be better ways to do it. I was in charge of exploring this way (which we didn't end up keeping, as I hint at at the end of the post), and thought it would be valuable to share what I learned with people.
Regarding your latter point, as I mentionned, a pattern fails silently if it doesn't match a log entry while parsing incoming entries. That's why Graylog requires you to load a log entry example when creating an extractor, and let you try it while defining the pattern (with the "Try" button next to the pattern input field). I didn't put enough emphasis on this feature in my post, though.