[HN Gopher] GNU Emacs Telegram Client
___________________________________________________________________
GNU Emacs Telegram Client
Author : medo-bear
Score : 80 points
Date : 2022-01-18 19:46 UTC (3 hours ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| HeckFeck wrote:
| I'm starting to doubt my doubt I have for the Church of Emacs. It
| seems anything really is possible for those who repent, memorise
| the collected essays of Richard Stallman and pray in Lisp.
| [deleted]
| miki123211 wrote:
| It's amazing how versatile the Telegram API is.
|
| I think the reason why it's that good is that it's literally the
| same API that the official apps use. There's no separate,
| restricted API for external developers, your app is treated in
| the exact same way as the official ones are. Even things like
| account creation and payments are exposed.
|
| The protocol is very esoteric and hard to understand, though. It
| wouldn't necessarily have to be that way, it just feels like
| their documentation is aimed at mathematicians, not developers,
| especially the parts concerning binary serialization. They
| definitely suffer from a "reinvent the wheel" syndrome, they have
| a proprietary client-server encryption layer where plain old
| HTTPS would do, same for data serialization. Things are
| reasonably well documented, though, and implementing a fully-
| featured client with 0 external dependencies is feasible. Voice
| calls are a notable exception here, the calls API has very little
| documentation and all it gives you is an opaque blob that you're
| expected to give to their own voip library.
| tanduv wrote:
| This isn't completely accurate.
|
| This client and all other 3rd party clients use tdlib, which is
| Telegram's open source client library to their servers. tdlib's
| development is notoriously behind compared to the client
| library used by their 1st party apps (which isn't tdlib). A
| good chunk of Telegram's modern features (voice chats, voice
| calling, chat reactions) aren't available on tdlib.
| james-redwood wrote:
| Emacs extensions never fail to astound me. It's almost an OS in a
| sense within a text editor.
| kunagi7 wrote:
| Well, it's not exactly a great idea but you can replace init
| with Emacs and it will boot [1]. You have basic utilities like
| a shell, file manager and with plugins you can run a music
| player...
|
| [1] http://www.informatimago.com/linux/emacs-on-user-mode-
| linux....
| jeofken wrote:
| It quite literally is a lisp runtime with text editing stuff.
| There are many resources on how to implement lisp, but for the
| text editor part, this book "The craft of text editing" was
| very good http://www.finseth.com/craft/
| ska wrote:
| > It's almost an OS in a sense within a text editor.
|
| That's actually not a terrible articulation of its design
| philosophy.
| necrotic_comp wrote:
| I was going to say - that's basically what emacs _is_. It 's
| a LISP machine that has an initial set of applications built
| in for editing text.
| tazjin wrote:
| telega is amazing. One of the overall best chat clients I've
| used.
| nine_k wrote:
| The thing being impressive as it is, I could understand how most
| things work in it.
|
| But they support _animated stickers!_ This is both wonderful and
| terrifying. Verily, Emacs is an operating system (with a decent
| editor built in). What next, a DAW?
| cle wrote:
| Emacs is a great environment for live coding music (not exactly
| a DAW, but more like a music REPL I suppose).
|
| https://www.youtube.com/watch?v=Ix2b_qFYfAA
|
| https://www.youtube.com/watch?v=Tjf-NJNfOP4
|
| https://www.youtube.com/watch?v=imoWGsipe4k
| yewenjie wrote:
| Telega lets you write messages in org markup, which I wish I
| could do everywhere.
___________________________________________________________________
(page generated 2022-01-18 23:00 UTC)