Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Status.im Invests $5M in Riot.im

blog.status.im

Post reply on HN
Print view View original

81–90 of 90 posts

Re: Status.im Invests $5M in Riot.im

#81

Post by Arathorn »

snvzz wrote: post #77
Arathorn wrote: post #76

Earlier quoted context omitted.

> It had problems with signatures when messages contained a certain field, so some messages appeared and others were missing. Did you file a bug on this? We're not aware of any signature problems whatsoever in Synapse (or Matrix). > Why do messages have so many fields? So looking at a message like this: { "origin_server_ts": 1517313544657, "sender": "@kitsune:matrix.org", "event_id": "$15173135441073284GrtsX:matrix.o…

> issue To be clear, it got solved, and it happened several months ago. > the Python/Twisted impl is very heavyweight (but getting better) Constantly near-saturating rpi2 cpu while doing effectively nothing last time I turned it on. (70%+ cpu time). This is why I'm thinking I'll wait for golang until I try again. >Right now the protocol is relatively good Couple questions: - If I delete my server database, start anew…

> If I delete my server database, start anew, and join a room I used to be in, will I end up in a bad state, or are things more robust these days? I remember reading about it somewhere.

It should end up (eventually) in a consistent state, but it can take a while to sync up again.

> Does the server _still_ solve a bunch of names and open hundreds of connections / server event interval or whatever it was called?

It's still full mesh, so whenever you send a message in a room, your server has to make a HTTPS hit to every other server which is participating in that room. In a massive room like Matrix HQ, this could mean 800 hits or so. It shouldn't do DNS every time, and it shouldn't open a new connection every time, but haven't checked the connpooling recently; hopefully it hasn't regressed.

Re: Status.im Invests $5M in Riot.im

#82

Post by Arathorn »

wk2jkhkjdfglsl wrote: post #65

Its good that Riot gets money, but its incredibly damning for Status, an ICO that was meant to produce its own chat platform. This shows status has no technical ability of their own, and has to ride on existing open source products. The status investors paid to build a new platform, and the team is unable to deliver this. By paying an existing open source project, yes we all win, but that is not what people (not myse…

Status isn't actually using Matrix in its own tech - they seem to be getting on great with their own React Native / ClojureScript / Whisper/PSS stack :)

Re: Status.im Invests $5M in Riot.im

#83

Post by Arathorn »

fegul wrote: post #78

One of my biggest concerns with Matrix was the amount of device data that it exposes. It's extremely easy to fingerprint the devices that someone is using (it literally tells you right within Riot) and by design could make it easy for someone to track you or target your device if there are any known exploits for it.

We've already fixed this - devices are now described as "Desktop", "Mobile" or "Web" by default. It was a thinko (mine actually) that we put too much detail in the device descriptions originally :(

Re: Status.im Invests $5M in Riot.im

#84

Post by Unklejoe »

tachion wrote: post #16
Unklejoe wrote: post #3

Cool. I just set up my own Matrix server (Synapse) the other day and have been using Riot.im on my iPhone. To be honest, everything works much better than I expected. Right now, my only complaints are that there are some notification settings that you can't change from the app, and that the user interface is a little redundant. I'm highly optimistic though.

And who are you talking to? The problem with Matrix (or other messenger technologies) is not that they're not good enough (in most cases nowdays) but that if not enough people are using them, they're useless, even if technically superior. I have pretty great working Jabber server but the issue is I have literally 2 people left I can talk to using it nowdays and both hardware and maintenance costs when compared to ben…

Sorry for the late response, I just saw this. I'm currently in a group chat with two other close friends. We were originally using GroupMe, but I convinced them to switch and register on my server (after I made sure that it was working reliably myself).

At the moment, it's the only messaging platform that I use. I use regular texts to talk to everyone else.

In my case, I don't need everyone to be invested into the network for it to be worth it. I'd say that around 95% of my daily communications are in the one Matrix group chat, so I've reduced my reliance on centralized services quite a bit.

I've set a general long term goal for myself to gain more control over my own data. The first step was purchasing my own domain and migrating away from Gmail. This is just another small step.

Re: Status.im Invests $5M in Riot.im

#85

Post by snvzz »

Arathorn wrote: post #81
snvzz wrote: post #77

Earlier quoted context omitted.

> issue To be clear, it got solved, and it happened several months ago. > the Python/Twisted impl is very heavyweight (but getting better) Constantly near-saturating rpi2 cpu while doing effectively nothing last time I turned it on. (70%+ cpu time). This is why I'm thinking I'll wait for golang until I try again. >Right now the protocol is relatively good Couple questions: - If I delete my server database, start anew…

> If I delete my server database, start anew, and join a room I used to be in, will I end up in a bad state, or are things more robust these days? I remember reading about it somewhere. It should end up (eventually) in a consistent state, but it can take a while to sync up again. > Does the server _still_ solve a bunch of names and open hundreds of connections / server event interval or whatever it was called? It's s…

>whenever you send a message in a room

Just to be clear, I saw this behavior without sending anything to any room. Just by being in the room.

If the server interval setting was 5 seconds, it'd literally do hundreds of connections every 5 seconds.

Re: Status.im Invests $5M in Riot.im

#86

Post by Arathorn »

snvzz wrote: post #85
Arathorn wrote: post #81

Earlier quoted context omitted.

> If I delete my server database, start anew, and join a room I used to be in, will I end up in a bad state, or are things more robust these days? I remember reading about it somewhere. It should end up (eventually) in a consistent state, but it can take a while to sync up again. > Does the server _still_ solve a bunch of names and open hundreds of connections / server event interval or whatever it was called? It's s…

>whenever you send a message in a room Just to be clear, I saw this behavior without sending anything to any room. Just by being in the room. If the server interval setting was 5 seconds, it'd literally do hundreds of connections every 5 seconds.

there is no such server interval setting, and there never has been? i can only assume that this was the retry schedule doing exponential backoff, trying to contact servers that are down. currently we don't have the concept of shared retry hints (as deciding whose hints to trust would be hard), so every server has to work out which servers are available in the mesh itself. After about 10 minutes it calms down.

Re: Status.im Invests $5M in Riot.im

#87

Post by piroko »

anderspitman wrote: post #63
ATsch wrote: post #62

Earlier quoted context omitted.

As far as I can tell (and from asking the developers), this is simply caused by the matrix.org servers being overloaded. Other homeservers don't seem to have this issue.

Good to hear. I was hoping that would be the case, and obviously it's not bothering me enough to do more than a cursory google search.

I’ve been running my own homeserver for over a year now. As long as I’m not joined to the “giant” rooms like #matrix:matrix.org and #riot:matrix.org, my user’s messages send instantly. Definitely recommend running your own server if you can manage it

Re: Status.im Invests $5M in Riot.im

#88

Post by anderspitman »

piroko wrote: post #87
anderspitman wrote: post #63

Earlier quoted context omitted.

Good to hear. I was hoping that would be the case, and obviously it's not bothering me enough to do more than a cursory google search.

I’ve been running my own homeserver for over a year now. As long as I’m not joined to the “giant” rooms like #matrix:matrix.org and #riot:matrix.org, my user’s messages send instantly . Definitely recommend running your own server if you can manage it

Excellent. I can and will soon. That's actually how I started out, but had some other performance issues. After a bit of googling I realized I'd need to read a bit more before running my own copy of synapse (was also uneasy about the security implications of all the federation stuff and want to make sure my server is hardened enough before I open those ports).

Re: Status.im Invests $5M in Riot.im

#89

Post by snvzz »

Arathorn wrote: post #86
snvzz wrote: post #85

Earlier quoted context omitted.

>whenever you send a message in a room Just to be clear, I saw this behavior without sending anything to any room. Just by being in the room. If the server interval setting was 5 seconds, it'd literally do hundreds of connections every 5 seconds.

there is no such server interval setting, and there never has been? i can only assume that this was the retry schedule doing exponential backoff, trying to contact servers that are down. currently we don't have the concept of shared retry hints (as deciding whose hints to trust would be hard), so every server has to work out which servers are available in the mesh itself. After about 10 minutes it calms down.

homeserver.yaml

# The federation window size in milliseconds

#federation_rc_window_size: 1000

federation_rc_window_size: 60000

That's how high it needs to be set, apparently.

Re: Status.im Invests $5M in Riot.im

#90

Post by Arathorn »

snvzz wrote: post #89
Arathorn wrote: post #86

Earlier quoted context omitted.

there is no such server interval setting, and there never has been? i can only assume that this was the retry schedule doing exponential backoff, trying to contact servers that are down. currently we don't have the concept of shared retry hints (as deciding whose hints to trust would be hard), so every server has to work out which servers are available in the mesh itself. After about 10 minutes it calms down.

homeserver.yaml # The federation window size in milliseconds #federation_rc_window_size: 1000 federation_rc_window_size: 60000 That's how high it needs to be set, apparently.

That doesn't control how aggressively the server connects out to other servers though - it limits how rapidly the server processes inbound requests; upping the window from 60s to 1s means that it will only process 10 requests from a given server in a 60s window (rather than 1s window) before deliberately falling behind. Interesting if changing it helped your problem; not sure how to interpret that.
Post reply on HN