telegraf
spec
telegraf | spec | |
---|---|---|
14 | 12 | |
7,710 | 3,064 | |
1.5% | 0.5% | |
8.9 | 8.4 | |
2 months ago | 5 days ago | |
TypeScript | WebAssembly | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
telegraf
-
Is there any telegram bot to forward any message given to an special channel?
Simply use telegraf : https://telegraf.js.org/
-
I own an advertisement group and would like two things.. a bot that prevents people from using advertisements more than a thousand characters... and a bot for English only groups. anyone?
this is pretty simple , you can create a bot yourself which simply listens for every message checks length and if exceeded deletes the message (bot must be added as admin ingroup and shows have read permission in bot settings) , I would suggest you to use https://github.com/telegraf/telegraf for the code,
-
How to create a Telegram Bot using NodeJS
In this project we will use the Telegraf library to create the bot. To install it, you can use the npm install command.
-
🥳 KaufmanBot v 3.2.0 🥳
Changed the main library for working with telegram from https://telegraf.js.org to https://grammy.dev, updated the source code for better work with typings
-
Telegram Bots for Begginers
Of course, it's good to write API requests yourself. It reduces the dependency on third-party libraries and allows you to control the behavior of the code more. But when there are more such methods than twenty, it already increases the size of the code. It becomes difficult to manage all the logic. This is where third-party libraries(frameworks) come to the rescue. After choosing a language, you can consider the options of different libraries from the list here, on the official Telegram page. For JavaScript I recommend using node-telegram-bot-api and telegraf. For Python you can take pyTelegramBotAPI and aiogram(highly recommended).
-
Show HN: We are trying to (finally) get tail-calls into the WebAssembly standard
It’s an expressive type system, but ime it allows developers to go crazy on type interdependencies and general entanglement, so you can’t just go to the “header” and quickly figure out what your method or a return value really is, despite TS has structural typing.
E.g. look at this: https://github.com/telegraf/telegraf/blob/v4/src/telegram-ty...
-
Newbie Help: Telegraf telegram bot with async/fetch, media send and async management
The bot uses telegraf framework, which is an overlay for the original telegram api, which is a nightmare in code form.
- Desarrollando un Bot para Telegram
-
Telegram celebrates 700M Users and introduces Telegram Premium
Honestly I found their API one of the worst ones I've ever used. The documentation is lacking, and they have some unintuitive quirks like posting messages with http GET requests and randomly concatenating strings in params (botNAMEOFBOT anyone?).
I didn't enjoy using it without a third party library [1].
Sending a single message is easy, but using the rest of telegram's features is "meh" when using pure API calls.
If you want to see a well designed API, you should take a look at FTX or Stripe. I love those two :)
[1] https://telegraf.js.org
-
Telegraf VS Node-Telegram-Bot-API
Today the most popular ways to build telegram chat bots in node js are Telegraf and Node-Telegram-Bot-Api. The second is more popular by weekly downloads(250.000), but in this post I don't want to equalize them by stats. I want to talk about my experience with them, in which cases I used them and show you really nice guide, especially for Telegraf, cause they haven't readable docs for newbies or people who don't use typescript.
spec
-
WASM Instructions
You can parse many things from this file, what are you trying to extract?
https://github.com/WebAssembly/spec/blob/main/document/core/...
-
The fastest word counter in JavaScript
Still strikes me as super sad JS never got SIMD support. It seemed like there were some strong candidate specs. On Node there are some add-on npm libraries that implement.
My understanding was the main protest was that we would get wasm & some certain implementers said they wanted to focus their energy on wasm.
That was well over half a decade ago & wasm is still in incredible infancy, with basically only statically linked capabilities in the spec.
Wasm SIMD proposal itself only merged into wasm in November 2021. https://github.com/WebAssembly/spec/pull/1391
It seems really unfortunate to have decided to keep JS the slow inferior language.
-
Is Blazor server and Blazor Webassembly going to be a big market? I am trying to figure out a niche to go with and I have some asp.net core mvc experience but I am working on a e-commerce .net6 Blazor Webassembly app.
Blazor and WASM itself (outside of dotnet) are relatively new tools and they already show impressive results. They will keep getting better with every release. E.g. this proposal https://github.com/WebAssembly/spec/blob/main/proposals/simd/SIMD.md which should bring WASM closer to "near native speed". Blazor already started working on it true.
-
Smolnes: A NES Emulator In
Big fan of this author's work.
They have a Gameboy emulator written in C, which can be compiled to WASM and run in the browser.
https://github.com/binji/binjgb
I learned a lot from the code.
Also I love this project with a bunch of demos in hand-written WebAssembly Text (WAT) format, which is like low-level Lisp that works only with raw memory, numbers, and minimal syntax.
https://github.com/binji/raw-wasm
Then I discovered the same author is quite active in the WebAssembly ecosystem, including specs and tooling. Fascinating stuff!
https://github.com/WebAssembly/spec
https://github.com/WebAssembly/wabt
-
Exploring WebAssembly, The Underlying Technology Behind Blazor WASM.
[The WebAssembly specification (https://webassembly.github.io/spec/) maintains that the standards apply to more than just the browser host, but also to any other compliant host runtime (what the specification refers to as an embedder).
-
Show HN: We are trying to (finally) get tail-calls into the WebAssembly standard
Heya,
(1) Thank you for implementing this in JSC!! I hope they take it, it makes it into Safari, and the tail-call proposal advances.
(2) I don't think you are exactly right about the call stack being observable via thrown exceptions. There's no formal spec for the v3 exceptions proposal yet, but in the documents and tests, there's nothing that would change in WebAssembly core to make the call stack observable. It's true that the proposal amends the JS API (but only the JS API) to describe a traceStack=true option; from Wasm's perspective I understand that's just an ordinary exception that happens to include an externref value (just like any other value) to which Wasm itself attaches no special significance. The engine can attach a stack trace if it wants, but there's no requirement (here) about what that stack trace contains or whether some frames might have been optimized out.
(3) I think the real reason that a Wasm engine can't implicitly make tail calls proper is that the spec tests forbid it, basically because they didn't want the implementation base to split by having some engines perform an optimization that changes the space complexity of a program, which some programs would have started to depend on (the spec tests say: "Implementations are required to have every call consume some abstract resource towards exhausting some abstract finite limit, such that infinitely recursive test cases reliably trap in finite time. This is because otherwise applications could come to depend on it on those implementations and be incompatible with implementations that don't do it (or don't do it under the same circumstances.)" More discussion here: https://github.com/WebAssembly/spec/issues/150
- WebAssembly 2.0 Working Draft
- A challenger to the throne of vector graphics. SVG is dead, long live TinyVG
-
Microsoft joins Bytecode Alliance to advance WebAssembly – aka the thing that lets you run compiled C/C++/Rust code in browsers
The WASM paper discusses that in the final section: https://github.com/WebAssembly/spec/blob/master/papers/pldi2017.pdf
-
Is there a small, well-specified language with lots of example programs?
WebAssembly has a formal specification that includes both operational semantics and natural language-based descriptions of everything in the language. The official repository also has a lot of tests. Besides tests, you should be able to find lots of examples by searching.
What are some alternatives?
node-telegram-bot-api - Telegram Bot API for NodeJS
uwm-masters-thesis - My thesis for my Master's in Computer Science degree from the University of Wisconsin - Milwaukee.
node-telegram-bot-boilerplate - 🤖 Create telegram bot with this friendly nodejs boilerplate
Oberon - Oberon parser, code model & browser, compiler and IDE with debugger
pyTelegramBotAPI - Python Telegram bot api.
meetings - WebAssembly meetings (VC or in-person), agendas, and notes
Express - Fast, unopinionated, minimalist web framework for node.
component-model - Repository for design and specification of the Component Model
telegram-bot-api - Telegram Bot API server
proposals - Tracking WebAssembly proposals
aiogram - aiogram is a modern and fully asynchronous framework for Telegram Bot API written in Python using asyncio
wit-bindgen - A language binding generator for WebAssembly interface types