finnn (u/finnn) - Readit News

finnn commented on Bird.makeup: a Twitter to ActivityPub bridge bird.makeup/... · Posted by u/tambourine_man

finnn · 3 years ago

ah yes, another fork of BirdSiteLive. Every one seems to make their own fork of that thing. And none of them (that I've found) set a user agent when delivering messages to other AP servers.

You can see where bird.makeup sets the headers here[0] (with a distinct lack of user agent) and an issue I filed against the upstream[1] asking them to please set a user agent.

[0] https://git.sr.ht/~cloutier/bird.makeup/tree/master/item/src...

[1] https://github.com/NicolasConstant/BirdsiteLive/issues/188

finnn commented on Notkia: Linux phone in the shape of Nokia, with LoRa + WiFI + BT connectivity hackster.io/reimunotmoe/n... · Posted by u/ddtaylor

monocasa · 4 years ago

They have shut down third party clients, and reserve the right to continue that. Both use f the name signal, and connecting to their backend without it being their official client are the reasons given, and those seem to apply to signald just as much.

https://github.com/LibreSignal/LibreSignal/issues/37#issueco...

finnn · 4 years ago

oh wow HN is parroting this bullshit again.

Moxie and Signal didn't do anything other than asking LibreSignal politely to stop using their servers. They didn't "shut down" anything, and they have shown no interest in shutting down signal-cli/signald.

MobileCoin, the cryptocurrency that Signal incorporates and essentially sanctions, uses signald for their bot[0].

the Signal Matrix bridge has hundreds if not thousands of open source users, plus Element One and Beeper users, all using signald and not having any repercussions for years. The only 3rd party Signal client that's caught any flak from Signal that I'm aware of is LibreSignal.

also see: last time this came up[1]

[0] https://github.com/mobilecoinofficial/mobot/blob/dev/RUN.md

[1] https://news.ycombinator.com/item?id=27682490#27683374

finnn commented on Element One – All of Matrix, WhatsApp, Signal and Telegram in one place element.io/blog/element-o... · Posted by u/mcjiggerlog

pmlnr · 4 years ago

I've seen your project! Congrats, it is very nice. I stopped fiddling with transports because signald doesn't compile/run on freebsd (some of the java libs behind it rely on native libs which have problems compiling), and for now I've put it aside.

finnn · 4 years ago

https://www.freshports.org/net-im/signald/

finnn commented on Command Line Interface for Signal github.com/AsamK/signal-c... · Posted by u/janekg

jchw · 5 years ago

Not equally enforced is the phrase you probably want, since the linked thread contains evidence of multiple instances of enforcement...

finnn · 5 years ago

Could you point me to some of those instances?

finnn commented on Command Line Interface for Signal github.com/AsamK/signal-c... · Posted by u/janekg

gnull · 5 years ago

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.

finnn · 5 years ago

Okay, that's fair. I interpreted them as a response to the original question about if the policy is enforced.

finnn commented on Command Line Interface for Signal github.com/AsamK/signal-c... · Posted by u/janekg

monocasa · 5 years ago

moxie views the servers as his, to change policy wise as he sees fit. I'm not sure you can separate the two practically.

finnn · 5 years ago

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.

finnn commented on Command Line Interface for Signal github.com/AsamK/signal-c... · Posted by u/janekg

gnull · 5 years ago

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

finnn · 5 years ago

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 much in the way of people actually experiencing issues interacting with the Signal server. Again, would appreciate it if you could link me to such a thing. As I mentioned elsewhere, I maintain an unofficial signal client and I try to be aware of these sort of things.

finnn commented on Command Line Interface for Signal github.com/AsamK/signal-c... · Posted by u/janekg

gnull · 5 years ago

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

finnn · 5 years ago

Sorry what am I looking for in this 200 comment reddit thread? I don't see any comments from moxie himself, just a lot of other people claiming to know what moxie wants. Are there reports of specific issues with 3rd party clients or comments from a Signal employee or something?

finnn commented on Command Line Interface for Signal github.com/AsamK/signal-c... · Posted by u/janekg

gnull · 5 years ago

I guess what finnn meant is that nobody can actually stop you from ignoring moxie's statement.

finnn · 5 years ago

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://github.com/AsamK/signal-cli/blob/05abb3f9f6294677d2d...

finnn commented on Command Line Interface for Signal github.com/AsamK/signal-c... · Posted by u/janekg

Macha · 5 years ago

> It's also not enforced

https://github.com/LibreSignal/LibreSignal/issues/37#issueco...

When did this stance change? Is there a current statement from moxie to that effect?

finnn · 5 years ago

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: signal-cli also sets a user agent clearly identifies itself: https://github.com/AsamK/signal-cli/blob/05abb3f9f6294677d2d...