chat #2

Closed
opened 2023-11-29 12:50:59 -05:00 by adam · 1 comment
Owner

so that I have the option of breaking up vassago into microservices

most things, it's not about to go elsewhere - but I definitely want other services to be able to chat, and my best idea at the moment is to send a gray_message so vassago can forward those to a designated "chat at adam" channel

so that I have the *option* of breaking up vassago into microservices most things, it's not about to go elsewhere - but I *definitely* want other services to be able to chat, and my best idea at the moment is to send a gray_message so vassago can forward those to a designated "chat at adam" channel
adam added the
Message
label 2023-11-29 12:50:59 -05:00
Author
Owner

change of plans: give vassago an API - https://gitea.adamrgrey.com/greyn/vassago/issues/25

"but me, do I want the ability to like... set up watches and stuff?"
"neat idea, me. But 1) "what a cool thing i might use" is inadequate, and 2) have the hypothetical "plz set up a watch" function also accept a webhook."

change of plans: give vassago an API - https://gitea.adamrgrey.com/greyn/vassago/issues/25 "but me, do I want the ability to like... set up watches and stuff?" "neat idea, me. But 1) "what a cool thing i might use" is inadequate, and 2) have the hypothetical \"plz set up a watch\" function also accept a webhook."
adam closed this issue 2023-12-10 11:59:35 -05:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: greyn/franz#2
No description provided.