Live data from Hacker News

Command Line Interface for Signal

github.com

71–75 of 75 posts

Re: Command Line Interface for Signal

#71

A really useful tool for us folks who don't use smartphones, been using it for the last 5 years to have Signal-desktop without a smartphone. Can't thank the maintainer and contributors enough! https://ctrl.alt.coop/en/post/signal-without-a-smartphone/

> us folks who don't use smartphones

Good to know you. I'm working on a plan to get rid of it myself in the near future, Is there any community for non-smartphone but technically inclined?

Re: Command Line Interface for Signal

#72
post #69
post #39

Earlier quoted context omitted.

It looks to me like those clients were removed due to trademark infringement (having "Signal" in their name), I don't think they were taken down because their code connects to OWS' servers (would GitHub or Google ever honour a takedown request like that?).

Sending messages to authors of third party clients that you are not ok with their use of your servers (literally the exact comment the link I and other posters shared): > I'm not OK with LibreSignal using our servers, and I'm not OK with LibreSignal using the name "Signal." You're free to use our source code for whatever you would like under the terms of the license, but you're not entitled to use our name or the ser…

I see what you mean, I guess the mix-up here is that we have different working definitions of "enforcement".

For example, I would argue that Moxie's desire for unofficial clients to not use the word "Signal" in their project name is a statement of policy, whereas the takedown requests to remove the projects from GitHub and the Play Store are examples of enforcement of that policy.

That said I think I can be convinced that directly informing a violator of your policy of said policy is a type of enforcement in itself.

Re: Command Line Interface for Signal

#73
post #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)

I should have said this is my comment above, but keybase had a CLI from the start that would do anything the UI would. It would make it usable on a headless machine, and was so easy to script. With the keybase CLI you could write a simple chat bot in a few lines of bash. I had a few "reminder" bots that were just lines in a crontab. Those were the killer features for me.

Re: Command Line Interface for Signal

#74
post #63
post #55

Earlier quoted context omitted.

There are several great e2ee features: - 250GB of free storage - personal subdomain that serves your public folder - git (e2ee)

>250GB of free storage Would be more useful if you could upload more than one file at a time.

In what situations does that matter?

Re: Command Line Interface for Signal

#75
post #53

Earlier quoted context omitted.

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.

Absolutely, but there are at least some circumstantial things you have heard/read to opine this way?
Post reply on HN