* installing the program, from https://jami.net or appstores or whatever * creating an identifier when prompted * establishing contact with other parties * creating groups * inviting contacts to groups * starting a group call
surely you've received the URL through some kind of communicator that had to be installed, and the contact set up
Jami is that kind of communicator. once you have it installed, and contacts set up, leveling the playing field, getting into a conversation, or starting one, is actually easier than visiting a URL
I'm told most people hardly ever look at their email these days. indeed, a lot of people don't even have one.
and they're not wrong. why use email that they need to go visit a web page to see, when a communicator like Jami brings messages, files and calls right into their devices?
I don't think I've come across this concept before. what are these "inbox rules" you speak of?
Jami, being Free Software, could probably have that and any other features that are desirable added. they don't even have to make sense for the business model of the original developers, and we're already at an advantage because Jami is not built with a goal of surveillance, control and exploitation
I don't mean to invalidate your experience, but communication media are very much what we (and our communication parties) make of them. I find the asynchronicity of email generally welcome, but I've also been in very high-bandwidth email communications, and some people expect immediate responses; I've also been in very low-bandwidth chat groups, but the interactivity can be useful at times. the very same social media networks can be overwhelming or desertic, depending on your contacts, and on what you use it for. in my case, missing an email can be a problem, but missing a chat message is no biggie, so "catching up" can be as easy as "mark it all read" (if there are even such markers in the chat client). but while some people use chat for throw-away conversations, some run businesses out of it, and for them discarding chat messages could be as bad as missing an email or a critical notification. my observation is that the properties we tend to assign to these media are not inherent to the media, but to the customs of the groups we interact with through them.
@7666@lxo@valhalla i will add that chats are really high-bandwidth and that's great for some things but i only got so much bandwidth in me and i really like email and fedi for the ability to just ignore it for hours and more or less get all the same info
@lxo@valhalla email is transactional by nature, meaning you can inject pre-processing filters/rules/logic/whatever into that before it is deposited into a mailbox. i have about 30 that do labeling, "mark as read" duties, sorting into subfolders, blocking, and more, which keeps the signal to noise ratio really high. chat on the other hand is more real-time and you can't quite as easily filter, sort, etc., that's why i generally don't prefer it.
even fedi has the same sort of transactional backing using posts allowing for filters, blocks, rewrites, whatever
GNU Jami offers some hope for that sort of features, that could presumably be added initially with its plugin architecture
that it uses per-conversation git repos with per-message commits underneath seems to make classification as simple as tagging the commits under some convention. that sort of thing would definitely be welcome to me. it's too easy to get things lost there.