News for hackers. Stuff that matters.
Re:A Slack clone in 5 lines of bash by lelanthran on Wednesday July 05, 2023 @04:40AM (#36597544)
> But then more difficult questions arise: - Is the price of slack worth it, when the alternative is having more educated users that can do very basic command line calls ?

I'm not sure that it would be difficult to wrap that up in a web interface running on a single server that does nothing but execute those command-line calls - auth, data and everything but session would be managed by the web server.

You could perhaps even make a local GUI application that spawns ssh once and reads+writes to it, and have your 90% slack functionality done in a weekend.

Re:A Slack clone in 5 lines of bash by sharikous on Wednesday July 05, 2023 @05:19AM (#36597812)
Yes and this GUI application should be cross platform so make it Electron.

Wait, there has been a leak from the company so we need some security staff on it and maybe mandated TFA.

And it's nice to have a way to call people and not only chat.

I wonder if there is already an app that does that, even if it's bloated it would be more convenient...

Re:A Slack clone in 5 lines of bash by lelanthran on Wednesday July 05, 2023 @05:29AM (#36597901)
> Yes and this GUI application should be cross platform so make it Electron.

Why? What's wrong with Qt? or any of the other x-platform UI toolkits I already use to target Windows, Linux and Mac?

(Your other points are irrelevant. I never claimed that suc will match slack 100%, feature for feature).

Re:A Slack clone in 5 lines of bash by revelio on Wednesday July 05, 2023 @12:02PM (#36602354)
That can be done just with an ssh:// URL handler. It already works on macOS, you can open terminals with an ssh session direct from web pages.
Re:A Slack clone in 5 lines of bash by lelanthran on Wednesday July 05, 2023 @12:35PM (#36602872)
TIL :-)

I did not know that. Can confirm that it works in FF on Linux.

Re:A Slack clone in 5 lines of bash by numpad0 on Thursday July 06, 2023 @12:15AM (#36611186)
I'm not sure where to post this reply but I have a hot take cooking up for about a week now: Is it too crazy to just leave a clustered SQL DB open to the Internet, static asset on S3, and call it THE backend of a social-* (-networking, -game) app? It's mostly SQL anyway. Maybe a message signing system like IPsec auth header can be set up with a client cert, and TLS packet encryption can be dropped, if it's going to be public data or data is to be advertised as "e2e encrypted". Isn't that going to cut a lot of backend cost?