Update Home
parent
d8c18df2b2
commit
93a3cbc71a
1 changed files with 22 additions and 24 deletions
46
Home.md
46
Home.md
|
@ -1,28 +1,26 @@
|
|||
Welcome to the Wiki.Things to consider
|
||||
Write the go service
|
||||
Turns out it’s actually a client not a server?
|
||||
Poll-based vs webhook-based behavior configurable with parameter
|
||||
Get everyone on twilio account
|
||||
Done!
|
||||
Write deployment stuff (make, docker, helm, etc.)
|
||||
Document:
|
||||
How to deploy
|
||||
How configuration details
|
||||
Special:
|
||||
Document creating compliant sms marketing campaign on twilio
|
||||
Document other twilio setup (sort of unknown complexity right now)
|
||||
jack worked for them and may have better insights, but they were mostly on the security team iirc [T]
|
||||
HIGH PRIORITY: confirm billing policies to ensure there isn’t a ~secret~ clause where they can just let us rack up a bill and invoice us later in case of some kind of catastrophic failure or spam influx
|
||||
Signal groups getting large feature updates early 2024, this may change the process dynamically
|
||||
Others: i.e. Discord, WhatsApp, Telegram APIs likely relevant
|
||||
SMS is important for non-smartphone users and less cross-platform stuff
|
||||
Can Twilio manage the queue for us?
|
||||
Get request to API url - how to edge trigger instead of purposeful Gets
|
||||
Rate limits/Verify seems to be the relevant factor here
|
||||
Possible name change?
|
||||
## Things to consider
|
||||
- Write the go service
|
||||
- Turns out it’s actually a client not a server?
|
||||
- Poll-based vs webhook-based behavior configurable with parameter
|
||||
- Get everyone on twilio account
|
||||
- Done!
|
||||
- Write deployment stuff (make, docker, helm, etc.)
|
||||
- Document:
|
||||
- How to deploy
|
||||
- config options
|
||||
- _Special:_
|
||||
- Document creating compliant sms marketing campaign on twilio
|
||||
- Document other twilio setup (sort of unknown complexity right now)
|
||||
- jack worked for them and may have better insights, but they were mostly on the security team iirc [T]
|
||||
- HIGH PRIORITY: confirm billing policies to ensure there isn’t a ~secret~ clause where they can just let us rack up a bill and invoice us later in case of some kind of catastrophic failure or spam influx
|
||||
- Signal groups getting large feature updates early 2024, this may change the process dynamically
|
||||
- Others: i.e. Discord, WhatsApp, Telegram APIs likely relevant
|
||||
- SMS is important for non-smartphone users and less cross-platform stuff
|
||||
- Can Twilio manage the queue for us?
|
||||
- Get request to API url - how to edge trigger instead of purposeful Gets
|
||||
- Rate limits/Verify seems to be the relevant factor here
|
||||
|
||||
|
||||
Twilio dev console:
|
||||
## Twilio dev console:
|
||||
Pin these things:
|
||||
“Phone numbers”
|
||||
“Messaging”
|
||||
|
|
Loading…
Reference in a new issue