-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking issue for migration to Ekztazy.jl for Discord API #124
Comments
Awesome! Yes, we should do it. |
Hi there! I want to give a bit of time to our bot at HoJ. Has anyone started to migrate to Ekztazy.jl? |
@tk3369 actually started to work on a new API, recently: https://github.com/tk3369/Discorder.jl/tree/tk/revive-project |
OK, so the new plan would be to bribe @tk3369 so that we can migrate to Discorder.jl haha. Joke aside, how much work is left to reach that point Tom, and ... do you need some help? |
Yeah I'm still trying to get Discorder.jl going.
The foundation is there and usable - making requests and gateway interface
for real-time communications. I spent quite a bit of time designing the
control plane, which makes the gateway interface more error-resilient and
manageable. The next step is to design and implement the higher level
user-facing APIs.
See "Current Status" section here:
https://github.com/tk3369/Discorder.jl/blob/tk/revive-project/README.md#current-status
Want to join the force? I'm actually going to be working on this project at
the Hackathon room in JuliaCon Gather Town.
Tom
…On Fri, Jul 29, 2022 at 11:25 PM Jean-Francois Baffier < ***@***.***> wrote:
OK, so the new plan would be to bribe @tk3369 <https://github.com/tk3369>
so that we can migrate to Discorder.jl haha.
Joke aside, how much work is left to reach that point Tom, and ... do you
need some help?
—
Reply to this email directly, view it on GitHub
<#124 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAI3EZTCZD7JP3GCBOAWTMTVWTDEJANCNFSM5QCIYWTA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
No description provided.
The text was updated successfully, but these errors were encountered: