You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first big project I'm undertaking in the transition away from Twitter is Drummer.
In the new post-Twitter world, Drummer will manage identity for itself using email addresses, and thus it will use HTTPS.
So the first step in the conversion is getting rid of all the hard-coded HTTP URLs in the app.
I'm sure they're not all gone yet, but the app does boot up without errors now both on a test server (which uses HTTPS), and the same code runs on the current Drummer site (which uses HTTP).
You can help test it out by using Drummer with the JavaScript console open, and note any errors that have to do with HTTP and HTTPS and report them here.
I'm not looking to fix old bugs at this time, just get the same piece of software we've been using for many months to work in the new context.
The text was updated successfully, but these errors were encountered:
The first big project I'm undertaking in the transition away from Twitter is Drummer.
In the new post-Twitter world, Drummer will manage identity for itself using email addresses, and thus it will use HTTPS.
So the first step in the conversion is getting rid of all the hard-coded HTTP URLs in the app.
I'm sure they're not all gone yet, but the app does boot up without errors now both on a test server (which uses HTTPS), and the same code runs on the current Drummer site (which uses HTTP).
You can help test it out by using Drummer with the JavaScript console open, and note any errors that have to do with HTTP and HTTPS and report them here.
I'm not looking to fix old bugs at this time, just get the same piece of software we've been using for many months to work in the new context.
The text was updated successfully, but these errors were encountered: