Live data from Hacker News

Command Line Interface for Signal

github.com

51–60 of 75 posts

Re: Command Line Interface for Signal

#51
post #46
post #30

Earlier quoted context omitted.

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

> If you think running servers is difficult and expensive (you're right), ask yourself why you feel entitled for us to run them for your product. I don't get Moxie's stance. Aren't they running Signal as a public service? This sentence reads as if LibreSignal would be stealing profits from Signal by using later's servers. But there is no intention to raise profits / add monetization, is there?

MOB (MobileCoin) looks like an attempt at monetization, a bit shady if you ask me.

Other than monetization, I get Moxie stance, even though I disagree. If you control both the server and the client and don't allow alternative clients and federation, it is easier to make changes, keep focus, and you don't have to deal with complains from users with crappy clients.

Signal is also security and privacy-focused, and Moxie presumably want to keep that image. What if some forks throw away that aspect, for example by storing plain text message in "the cloud". Personally, I actually don't care that much about the privacy/security aspect of Signal, as weird as it may sound, for me, Signal is just a nice, no nonsense messenger with security as a bonus and I would welcome a fork that makes a convenience trade off. But these less secure clients may undermine trust for those who really see it as a primary reason.

Re: Command Line Interface for Signal

#52
post #35

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?

I've never seen or hear anyone I know use Keybase.io for actual texting, and I work at a large software company. Everyone just uses it for PGP keys, then forgets it exists.

For PGP keys, I've managed to replace my usage of Keybase with Keyoxide.

1: https://keyoxide.org/ 2: https://codeberg.org/keyoxide/keyoxide-web

Re: Command Line Interface for Signal

#53

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?

It will probably bit rot away, or be rebooted when Zoom wants to make a PR move. In my opinion, the Keybase founders always intended to sell it off and never intended to keep their promises of OSS-ing the tech. It was a cool idea, but I never saw any vision for the idea or really what benefits it brought the tech community.

Do you have any citations for the "founders intended to sell it off" part?

Re: Command Line Interface for Signal

#54
post #35

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?

I've never seen or hear anyone I know use Keybase.io for actual texting, and I work at a large software company. Everyone just uses it for PGP keys, then forgets it exists.

I do and know several people who do too. Although the UI could be improved.

Re: Command Line Interface for Signal

#55
post #21

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?

I still use Keybase heavily for work and personal contacts, and the Linux client just got updated. It's not really a platform with high visibility usage (which is a benefit IMHO).

There are several great e2ee features:

  - 250GB of free storage
  - personal subdomain that serves your public folder
  - git (e2ee)

Re: Command Line Interface for Signal

#56
post #44

So... we're gonna write code in python ...that interfaces with a CLI ...that's a wrapper around a Java library ...that communicates with Signal's API? Would it not be better to write code in python that communicates directly with Signal's API?

> Would it not be better to write code in python that communicates directly with Signal's API?

Only the official builds of the official signal clients are allowed to connect to the signal servers, everything else is considered unauthorized use (under the CFAA) by moxie, Signal’s lead dev.

At least that’s what he said on the bugtracker of the fork "LibreSignal" while forcing them to shut their fork down.

Re: Command Line Interface for Signal

#57
post #32
post #6

Earlier quoted context omitted.

It's not a licensing restriction, it's a terms of use for their network service. It's also not enforced. Their clients are open source, signal-cli uses a fork of the Android app's client library.

If their clients are open source, why would they have a ToS saying you can't make your own clients?

Because open source is only used as a publicity tool by Signal. That's why their server code was abruptly closed sourced without announcement for a year (purportedly to add a scam cryptocurrency that Moxie has a conflict of interest in).

It's hard to trust a project with a divisive, evasive and concealing leader.

Re: Command Line Interface for Signal

#58
post #53

Earlier quoted context omitted.

It will probably bit rot away, or be rebooted when Zoom wants to make a PR move. In my opinion, the Keybase founders always intended to sell it off and never intended to keep their promises of OSS-ing the tech. It was a cool idea, but I never saw any vision for the idea or really what benefits it brought the tech community.

Do you have any citations for the "founders intended to sell it off" part?

There's a "In my opinion" in front of that sentence. You don't need citations for opinions.

Re: Command Line Interface for Signal

#59

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?

What's so special about keybase? I feel like Signal is current solution to go to if you just need easy e2ee (espexially because of its big userbase). Otherwise it's Matrix for me as it offers "the future of messaging" (well, you wish)

Re: Command Line Interface for Signal

#60

It asks me to get a captcha on https://signalcaptchas.org/registration/generate.html , but the site does not seem to work.

"After filling the captcha, the site doesn't show the token but redirects to a signalcaptcha:// url that contains the token. [...] To see the URL you can open the browser developer tools (F12) before completing the captcha." https://github.com/AsamK/signal-cli/wiki/Registration-with-c...

Using Tor Browser I can see the signalcaptcha:// address in the window title of a detached Developer Tools window.

Post reply on HN