21–30 of 75 posts
This makes me really miss Keybase.io. Anyone around from Keybase? Will it just bit rot away or will it get some attention/love in the future?
Earlier quoted context omitted.
signal-cli uses a clearly identifiable user agent [0] that could easily be blocked if Signal wanted to. signal-cli could escalate by trying to evade that kind of a block, but as it stands signal-cli has been operating without trouble for several years. I meant they may ask some clients not to use their servers, but they don't have any enforcement mechanism in place beyond asking them to stop on github. [0] https://gi…
They can apply measures to the users. They are not doing it right now, but they could suddenly start. By the discussion on some reddit threads [1], this moxie guy looks sketchy to say the least. But I support the devs who work on alternative clients. The official Electron app is just bad, especially on Wayland. Hope signal-cli will keep working. [1]: https://www.reddit.com/r/linux/comments/mp2j0j/starting_a_na...
Most people here who are interested in privacy know who "this Moxie guy" is.
Earlier quoted context omitted.
You are looking for links to what moxie said and people's experiences of interacting with him. The links to LibreSignal (already mentioned here) and Wire stories summarize most of what I was pointing at: https://github.com/LibreSignal/LibreSignal/issues/37#issueco... https://medium.com/@wireapp/axolotl-and-proteus-788519b186a7
I'm looking for people's experience interacting with the Signal server , not moxie. We're talking about if the server enforces any kind of client restrictions. I haven't looked super deep, but to the best of my knowledge that's not something that happens really. I looked through that reddit thread (thanks for that BTW, whisperfish seems interesting) and skimmed over that enormous GitHub thread, but I couldn't find mu…
Earlier quoted context omitted.
I'm looking for people's experience interacting with the Signal server , not moxie. We're talking about if the server enforces any kind of client restrictions. I haven't looked super deep, but to the best of my knowledge that's not something that happens really. I looked through that reddit thread (thanks for that BTW, whisperfish seems interesting) and skimmed over that enormous GitHub thread, but I couldn't find mu…
moxie views the servers as his, to change policy wise as he sees fit. I'm not sure you can separate the two practically.
Is the policy enforced? I've seen no evidence of it.
Earlier quoted context omitted.
moxie views the servers as his, to change policy wise as he sees fit. I'm not sure you can separate the two practically.
We know the policy, no one is confused about the policy, all 3rd party clients violate the policy. Is the policy enforced? I've seen no evidence of it.
Other things that are being brought up here are at least as important and interesting to discuss.
Earlier quoted context omitted.
We know the policy, no one is confused about the policy, all 3rd party clients violate the policy. Is the policy enforced? I've seen no evidence of it.
Most of the replies in this sub-thread are not about servers possibly disrupting the work of custom clients right now. But you react as if they were. Other things that are being brought up here are at least as important and interesting to discuss.
Earlier quoted context omitted.
I said it's not enforced. I cannot speak for moxie or Signal. I can speak for my own experiences, as the maintainer of a fork of signal-cli, and I have never seen any evidence that Signal's servers block signal-cli or my fork. I don't know about signal-cli but my fork clearly identifies itself in the user agent (and another field called the "signal agent") to the server. If they wanted to block me they could. edit: s…
Not equally enforced is the phrase you probably want, since the linked thread contains evidence of multiple instances of enforcement...
Earlier quoted context omitted.
I said it's not enforced. I cannot speak for moxie or Signal. I can speak for my own experiences, as the maintainer of a fork of signal-cli, and I have never seen any evidence that Signal's servers block signal-cli or my fork. I don't know about signal-cli but my fork clearly identifies itself in the user agent (and another field called the "signal agent") to the server. If they wanted to block me they could. edit: s…
Not equally enforced is the phrase you probably want, since the linked thread contains evidence of multiple instances of enforcement...
Earlier quoted context omitted.
Not equally enforced is the phrase you probably want, since the linked thread contains evidence of multiple instances of enforcement...
Can you link to one or two? I read through most and haven’t seen any, but I may have missed it.