Introducing Threads in Beta!
element.io
external-link
All users can now opt-in to our Threads Beta! Threads helps declutter the main room timeline by moving conversations and topics into the right panel.
@Echedenyan
admin
link
fedilink
3
edit-2
2M

I think that is being converted in a tool similar to Mattermost or Rocket Chat for internal chats in a company.

poVoq
link
fedilink
22M

That is clearly the way their current investors want to make back their money… company and public sector internal chats without open federation. Makes sense from a business perspective and is a relatively ethical choice (deployments for the military aside), but it will not make home users very happy.

I’d rather have the military finance Free software than tossing tax money into proprietary sinkholes. That said, of course in an ideal world we wouldn’t need any military…

@morrowind
creator
link
fedilink
32M

I think it can be used for both without trouble.

@ieure
link
fedilink
-42M

why do they keep making it worse

down daemon
link
fedilink
7
edit-2
2M

threads are great when used right, especially for very large rooms. it’s the only slack feature i like. that being said, it’s a learning curve. the slack i was in had a custom Thread emoji to remind people to reply in-thread

m-p{3}
link
fedilink
62M

Personally I’ve found threads useful when used in some workflows.

@vikaren
link
fedilink
22M

threads was one of the things I was missing from Element, why does it make it worse? We’ve been having threaded discussions since USENET, it’s good feature.

@ieure
link
fedilink
11M

Chat systems aren’t email, or Usenet, or forums, and while it is a good feature in the context of those async / longer-form communication, where you need the context, it doesn’t work nearly as well for realtime chat, where you already have the context because it happened two seconds ago.

The convention of replying in thread or in channel is a combination of personal preference (I like/dislike or am/am not used to threads), group expectations (we have agreed to reply in threads/in channel), and muscle memory (I mostly talk in channels that reply in thread, but this one expects it in channel). As the number of participants increases, it gets hard to manage, so you get a mix of in-thread or in-channel replies (and in-thread replies to in-channel replies), which leads to a fragmented, inconsistent mess and people complaining about both styles at once.

@snek_boi
link
fedilink
22M

I can see how this makes it more cluttered, less intuitive, and seem as if the basics aren’t taken care of (e.g., when will we get P2P?). This makes me think of Google Wave, which I think was brilliant. Unfortunately, I understand that many users weren’t able to understand how it worked. I wonder if times have changed enough for people to be able to understand something like threads.

I say that because I think it’s an interesting feature. The only reserves I have is how this will be presented so that cognitive loads are reduced, and the possibility that, even at its simplest, the least technically-savvy users will not intuitively understand it. Maybe that’s also your reserve(?).

If you want to see how it works, you can also look at Zulip, a forum-messenger-mailinglist hybrid.

Tmpod
link
fedilink
22M

basics
P2P

P2P on Matrix is far from being a basic feature imo

@snek_boi
link
fedilink
12M

You’re right. In terms of implementation, it apparently isn’t so because it’s technically difficult.

However, many privacy-oriented people consider it a requisite to be able to use it. Insofar a something is considered a requisite, it can also be basic.

@LeftyLayman
link
fedilink
12M

What part?

An open network for secure, decentralized communication

  • 0 users online
  • 3 users / day
  • 6 users / week
  • 19 users / month
  • 52 users / 6 months
  • 1.35K subscribers
  • 110 Posts
  • 352 Comments
  • Modlog