Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×

Comment Re:Jokes on them. (Score 1) 49

Heck of a business to be in. Make a service that has been available for free in some form or another for decades. And then compete with dozens if not hundreds of other startups and open source projects. Maybe I should sell of the few shares of WORK (Slack) that I have.

We have had jabberd setup at work for about 15 years. But a few years ago, my work decided to pay for both Slack and Teams. Teams is sort of free, but not everyone actually wanted MS Office so it was only free in our IT department's weird fantasies.

How do I find my coworkers when we're on 3 different services. I run 3 different apps/tabs. Also a handful of coworkers refuse to use chat programs, and will video conference but only if you set it up via email in advance.

I'm not really trying to complain. More pointing out that the tech industry is full of brilliant people who can't even make a simple agreement on which nearly identical pieces of software to use company-wide.

Comment it's science (Score 1) 37

Out of an abundance of caution, let's assume a new technology has unintentional consequences until proven otherwise. That's it. Be a "doomer" until we stop having fundamental questions about the performance of our AI systems. That you can trick an LLM into giving you restricted information should be a warning sign that we don't fully understand what we're doing in this industry.

Comment Re:Peace and prosperity (Score 1) 123

Back in the old days they'd off the idiot son of the ruler to make room for a more reliable heir. The great thing about dynasties is the family running things has an interest in keeping their reputation. But you still end up fighting to settle grey areas of succession like with Lancaster and York in the War of the Roses.

Comment Re:Jokes on them. (Score 2) 49

These IRC clones like Discord and Slack are so incredibly broken. We've had the technology to chat online for decades, and the visually impaired have been using screen readers and braille with IRC since the beginning. With Discord and Slack, it is much more cumbersome to navigate with a screen reader. Since it is ultimately a web app. The ability to also do voice chat is nice, but for us old farts we don't really want to talk on what amounts to a chaotic party line.

I feel like both IRC and Jabber/XMPP missed an opportunity to offer some of the quality of life features that Slack and Discord have. The ability to start your own private zone inside the server, where you can customize the channels and welcome message is pretty huge. We used to do welcome messages with bots back in the day, and it was much more cumbersome. Do I need custom animated reaction "emoji" ? Not really, I don't need chocolate to survive either but I don't mind having either around.

Comment Re:Ctrl-Z (Score 1) 201

While I'm glad you got the reference. I do know how termios works. You can change the key for this with an ioctl() to update the c_cc array and pick a different suspend character for the terminal driver (the suspend character causes the terminal driver to send a TSTP to the current terminal owner). This setup works roughly the same on most SysV style Unixes (not just Linux).

From the command-line, you could do something like:
    stty susp ^K

And this will make well-behaved interactive programs use the new suspend key. Some programs like Vim don't honor the terminal driver, and handle suspend themselves. So by default you will still use Ctrl-Z when in Vim, even if you configured your terminal differently. Which is an example of the millions of little cuts that has ruined Unix over the years. A fundamental misunderstanding by application writers in how the subsystems work, they end up making these islands of configuration that pretend they aren't operating in a shared environment. In Vim's defense, taking over your terminal is a work around for another problem. Leaving the stop/start/intr/eof characters (^Q and ^S and ^C and ^D) bound to the terminal driver is not ideal for full screen interactive applications. And other characters don't make sense outside of ICANON mode such as line editing kill(^U), word erase (^W), etc.

Not that Unix terminal I/O is some perfect system. Because for the life of me I don't understand why some Linux systems default to erase ^H and some to erase ^?, sometimes on the same distros but under different terminal apps. It's a super old problem, Unix couldn't pick a standard for what to do with a keyboards backspace for 50+ years and Linux continued the "tradition" for another 30+ years (despite mainly using IBM style keyboard layouts with a simple backspace and no rubout, erase, or other confusing electric typewrite modes).

Slashdot Top Deals

Genetics explains why you look like your father, and if you don't, why you should.

Working...