monty5811 / apostello Goto Github PK

Set up a demo site on Heroku (needs #12)

Cost indicators should be updated as outgoing SMS may be longer than the 1 message limit.

Should be: (num recipients)*ceil((length of message)/160)

The keywords table at /keyword/all/ currently shows the response that is sent when a user matches a keyword within the correct time limit.

This should be changed so that the currently used response is shown instead, i.e.

• if we are before the start time, show the too early time
• if the keyword is active, show the active response
• if we are after the end time, show the too late time

Show emails instead of usernames in user dropdown. E.g. the subscribe to daily email selection.

Page to more easily edit user permissions

This idea stemmed from the fact that there isn't a default way to remove someone from the list. The goal would be to have the ability to send to some subset of a group. i.e. If I have group A and group B, but I only want to send to members of A that are not in B, I should be able to specify that I want to send to A - B.

Having the ability to preform set operations such as union, intersection, complement, difference, and combinations thereof could add some powerful functionality to Apostello.

Remove django mailgun dependency

django-q.readthedocs.org

Seems to be simpler than celery and better integrated with django. Would also make implementing #29 easier as scheduled tasks are just django models.

Can simplify the ansible deploy - replace memcached and rabbitmq with redis. May make it easier to deploy to Amazon in the future too as it supports SQS (experimental in celery).

Add a setting to make it easy to customise the favicon used for an organisation.

In addition to #8, it would be nice to integrate also with Mailtrain.

Once you update the name of a person, in history, it still shows the old name, in my case, "Unknown Person".

Opbeat addon currently in invite only beta.

Wait until publicly available before implementing.

Add a first run page to help people with setup.

• Show the page if there are no users in the user table.
• Display a list of relevant settings and their current values
• Add a form to create a super user and bypass any verification steps
• Add a way to test email setup i.e. a send a test email button
• Remove the current auto admin approach

New setting to allow automatic addition of new people to designated groups.

Use formatted messages for the slack webhook

Ref: https://api.slack.com/docs/attachments

• Tweak the logging config to dump more useful information on exceptions
• Add more logging around common actions

I'm doing a free service to a couple of churches that use the same phone number. I think it would be nice to have a message in the form of join <group>, which might require approval.

A hack would be to auto treat groups as join keywords.

Another way would be to support multiple phone numbers are assign them to organizations. The thing is that it is possible (in the case of Orthodox churches, at least) that one person goes to more than one church.

Add option to automatically sync Elvanto groups.

• Add Elvanto group id field
• Add option to toggle syncing
• Add task to sync group membership

Add a field to the user profile that specifies how much each user is able to spend per message. This is intended purely as a sanity check and not to prevent purposeful abuse (there will be no rate limits, for example).

• Add field to model
• Add checks when sending
• Provide feedback to user
• Add instructions so admins can change the limit

Replace favicons with apostello branding.

Make setup clearer.

Any emails sent by django-allauth will not use the email settings set on the Sit Configuration page.

Should implement a custom EmailBackend so that the settings are enforced for all emails, including those send by third-party apps.

Run through deployment, following instructions exactly to find any errors

Look into pulling in contact details and groups from onebody.

• Add Procfile
• Add runtime.txt
• Add heroku.py to settings
• Use whitenoise for static files
• Add app.json for push to deploy
• Add instructions to the docs

Add proper login options to remove the Google Apps requirements.

• Login screen
• Login by email
• Allow vetting of sign ups - user cannot see anything until they have been verified
• Logout button

Make Heroku setup a little easier by adding the mailgun addon to the config.

Twilio supports large messages up t0 1600 characters, which it breaks transparently into 160-character ones. I've been broadcasting large texts for months and I wanted to switch to Apostello tonight but got hit with the 150 character limit. Please, add the option to have a textarea with 1600-character limit.

Would like matching keyword, with no autorespond checked, to still generate a successfully joined sms. If there is no keyword matched, then no autoresponse.

Setup a gh pages info site

Only been tested using a UK number. Need to test with other locales supported by Twilio.

Allow customisation of timezone and locale from env vars (it is currently hard coded in the settings).

There are several occurrences of "inour" instead of "in our" in the stock messages.

Add forms for the site configuration and default responses models so we do not need to go into the django admin as much.

The app sets up on Heroku, but then you can't do anything as you keep getting 403 errors on testing email, SMS, and admin creation.

Add field to site config model.

Render in not approved template.

• Show a list of outgoing SMS that have been scheduled but not yet sent
• Add button to cancel messages

Add option to prevent automated replies for a contact. Should help prevent some abuse.

• Add tests
• Add field to model (and migrations)
• Add help text and documentation
• Add checks to actually prevent replies
• Highlight blocked users in contacts table and incoming table

Create a reserved keyword that allows anyone to figure out the currently active keywords.

Potential trigger words:

• keywords
• list
• ???

Example

1. End user texts keywords
2. apostello replies The currently active keywords are: test, connect, ask, eat

Other considerations

• Need to update docs to reflect reserved keyword
• Should this be optional? Should admins be able to disable this functionality
• What if there are lots of keywords? Could get expensive to send. 10 should fit inside 160 chars (keywords cannot be longer than 12 chars)
• Update message that is sent out when a message fails to match any keyword to tell end users that they can see the list

Publish ansible playbook with instructions for use.

When creating a new keyword, contact or group, the wrench menu has a "remove" button in it.

This is a bug as there is no item to remove yet.

• Total number of messages in/out
• Most frequent texter
• Most frequent recipient
• Most used keywords
• etc

• Make login with Google more obvious
• Theme change password page
• Link to change password page if user signed up by email
• Send email to office email when a new user signs up (so they can approve them)
• Fix nav bar, so the cache is invalidated on user profile save (so we don't have to wait 15 minutes for the nav bar to update)
• Remove built in django-allauth messages

Add options to hide different login methods.

Would like to automatically create a new group with those that respond to a matching keyword. ie. all those who wanted to join the prayer chain and responded "pray" would automatically be added to a new group called prayer chain.

https://www.twilio.com/docs/quickstart/python/sms/tracking-conversations

Currently filters by first name only.