Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Arathorn
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
391 ms
·
2581.
▲
by
Arathorn
11y ago
[Slightly naughty crosspost from https://drewdevault.com/2015/11/01/Please-stop-using-slack.h... ] There are an increasing number of plausible FOSS alternatives to Slack out there like Zulip, Mattermost, LetsC
2582.
▲
by
Arathorn
11y ago
It also supports Matrix natively as well as IRC, which almost gives you best of both worlds :) http://matrix.org/blog/project/glowing-bear-weechat-plugin/
2583.
▲
by
Arathorn
11y ago
It should be trivial to federate it via Matrix.org if they felt the urge :)
2584.
▲
by
Arathorn
11y ago
The wiki page was in response to the XMPP bit of http://matrix.org/blog/faq . Coincidentally Matrix is a Wave-like protocol that hasn't been shoehorned into XMPP.
2585.
▲
by
Arathorn
11y ago
+1 that JSON-over-WS is not a panacea. Long-polling is inelegant but is pretty efficient with HTTP/2.0, and trivially degrades on older HTTP stacks (e.g. in embedded devices) which don't know anything about WS. Dave Cridland'
2586.
▲
by
Arathorn
11y ago
http://matrix.org/docs/spec/#m-room-redaction is the current API for removing messages. Matrix uses namespaces for extension to survive mutual parties extending it ( http://matrix.org/docs/spec
2587.
▲
by
Arathorn
11y ago
As the spec says, the ID service is optional. We haven't even bothered speccing it because the current logically-centralised thing is placeholder until we find a good decentralised solution. "Strong identity system" simply r
2588.
▲
by
Arathorn
11y ago
I'm pretty sure we don't claim identity mapping anywhere as an integral key feature; if we do, it's a mistake. We always decoupled the identity mapping layer from the core messaging layer to avoid the Hard Problem of decentr
2589.
▲
by
Arathorn
11y ago
heavenlyhash: I think you struck a nerve ;) Dave: yes, the Matrix 3rd party ID to Matrix-ID mapping service is currently logically centralised. The good news is that the service is entirely optional and you don't have to use it , and
2590.
▲
by
Arathorn
11y ago
I'm not sure that creating a new vendor-specific protocol without federation or cross-vendor interoperability really helps anyone but you ;)
2591.
▲
by
Arathorn
11y ago
Oh, in terms of the risk of federation causing lock-in: it's inevitable that folks will add domain-specific extensions to try to force people to use their platform. This is no different to me sending you an attachment over email in so
2592.
▲
by
Arathorn
11y ago
The example 'Matrix Console' iOS & Android apps are aesthetically very ugly, but still very functional and usable from a geek perspective. Meanwhile we're currently replacing the example Matrix Angular webapp with a Matr
2593.
▲
by
Arathorn
12y ago
Interesting - this is new to me (and ironic, given Aether was a candidate name for Matrix!). The projects seem very similar in some ways - both python/twisted/sqlite server stacks + angular frontend. The big differences seem to
2594.
▲
by
Arathorn
12y ago
So, signed-message history is purely for integrity, not privacy. The problem is that if all your rooms are completely decentralised, how do you stop a rogue server injecting false information about the past? All servers have a keypair tha
2595.
▲
by
Arathorn
12y ago
IRC's longevity and appeal is fascinating - it seems like that the more constrained the bandwidth of communication, the more compact the configuration, and the more quirky and charismatic everyone's favourite clients (be they irss
2596.
▲
by
Arathorn
12y ago
Not quite - as PGP is a pita to use, and not a formal part of the SMTP spec. So refusing to read non-PGP would be suicide. But if it was considered table stakes to implement the crypto option of the spec, and all the decent Matrix clients
2597.
▲
by
Arathorn
16y ago
Well, whilst now a startup only in attitude rather than size, OpenMarket (formerly MX Telecom) is looking specifically for ops folk in the UK at the moment. If you're based around London and want to get involved in a small but deadly ops te