babolivier

And has been operating as a fully fledged subsidiary of the foundation since 2020: https://blog.thunderbird.net/2020/01/thunderbirds-new-home/

> 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.

    Location: London, UK
    Remote: Yes, happy with hybrid too
    Willing to relocate: No
    Technologies: Python (Twisted, Flask-like, Django), PostgreSQL, Go, Rust, designing (incl spec work) and implementing decentralised HTTP+JSON REST APIs (e.g. Matrix), Git, Docker, CoAP, CI/CD, TDD, JavaScript, Salt, Ansible, Grafana, Logstash, Graylog, Warp10
    Résumé/CV: https://brendan.abolivier.bzh/cv.pdf
    Email: hello at brendanabolivier.com

    Location: London, UK
    Remote: Yes, happy with hybrid too
    Willing to relocate: No
    Technologies: Python (Twisted, Flask-like, Django), PostgreSQL, Go, Rust (basics), designing (incl spec work) and implementing decentralised HTTP+JSON REST APIs (e.g. Matrix), Git, Docker, CoAP, CI/CD, TDD, JavaScript, Salt, Ansible, Grafana, Logstash, Graylog, Warp10
    Résumé/CV: https://brendan.abolivier.bzh/cv.pdf
    Email: hello at brendanabolivier.com

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.

Of course it's not there yet, though it's quite likely to get there in the future.

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.

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.