I don't understand why technologies need to distinguish between synchronous (chat) and asynchronous (email) communication. There is certainly a difference in UI, but couldn't the supporting technology be the same? Couldn't we build an email app on top of a chat server? Or a chat app on top of email (DeltaChat does this). Would it make sense for a company to pick one chat/email platform and use it for both sync and async communication? (assuming the platform has both sync and async applications)
The Alot is an amazing creature. Just discovered this article during my roaming through terminal email clients.
I'm trying to wrap my mind around how to make mbsync work well with gmail.
It seems that mbsync creates a "Starred" folder, but it also attaches the important modifier onto them. Locally, it seems to make sense to not have the Starred folder and just filter to important emails.
Also, on gmail, I see the same email in my inbox and in the starred view. This means the email is duplicated by mbsync, right? Seems bad.
Does anybody have ideas for how to use mutt and gmail effectively together?
I wrote this explanation of #Federation for the non-technical user. It's not very in-depth, nor very long. I'm not totally satisfied with how I wrote it, so I may rework it in the future when I have more motivation.
Let me know of any problems or issues you find.
I'd like to know why so many people have gravitated towards Matrix, but not many towards XMPP. Also, why do Matrix detractors not advocate XMPP?
In particular, I'm concerned with the experience for non-technical users as well.
@sir, I'd appreciate your input, since I know you advocate IRC; is there anything specifically wrong with XMPP?
I've been using #Matrix for getting to about a year now. It's been a good experience, since I've stuck with using Synapse and Riot (the reference server and client), but everything else is incomplete. In addition, Synapse is a memory hog.
I've also become aware of #XMPP, which seems to be a much simpler protocol. As I'm googling around, I've seen articles debunking XMPP myths, but then I also see a bunch of articles of companies moving away from #XMPP, because it's "outdated".
Maybe I should know this by now, but there is one thing I don't understand about the #Fediverse:
What is the difference between all the services (e.g. between #Mastodon and #PixelFed). Obviously PixelFed is for images and thus has an accordingly catered UI, but does the server also need to give special consideration to images? Isn't everything #ActivityPub? Does each service have to extend AP to support its type of content?
Any #Ultimate #Frisbee enthusiasts on the #Fediverse? The game aligns well with decentralization because it is officiated by the players on the field rather than by referees appointed by a governing authority. Even at the highest level, when there are observers, they only give input when appealed to by the players.
Anyway, I just play because it's a ton of fun and was easy to get into. The systems and strategies are a lot more complex than I initially thought. It's fascinating really.
Type system idea: the three type composition operators are ^ (product), | (sum), and ~ (name). Structs are just product types with each part having a name.
type point = x~int ^ y~int
type bool = true~() | false~()
type shape =
circle~(c~point ^ r~int)
| square~(tl~point ^ br~point)
Should ^ be commutative? If each side is named, then I would want that, but that seems a little inconsistent.
x~int ^ y~int === y~int ^ x~int
x^y !== y^x
Just saw this article on OCaml Planet - I will have to watch these videos sometime.
Is there an open source client for Vimeo? There seem to be a lot for YouTube, but I didn't get any results for Vimeo.
I'm not sure I like Arch that much. It's not about Arch's minimalism, which I am a fan of. On #NixOS, I expect a newly installed package to work immediately (though not necessarily have every possible feature). On Arch, WeeChat, Haskell, and other packages were giving me headaches.
Anybody agree? Is my approach wrong?
Wedding Vows Show more
Minister to groom: do you, Richard, solemnly vow, in sickness and in health, for richer or for poorer, that you are never gonna give her up, never gonna let her down, never gonna run around and desert her, never gonna make her cry, never gonna...