The Changelog


Refreshed design of the venue listing page.


Improvement to community inquiries created from emails (e.g., when a participant replies to their ticket email, we forward the content to the organizers). Extraneous text removed from forwarded reply emails. If contents of email cannot be extracted, automatically reply to sender of email telling them this, and asking to use contact form instead. Email triggering the inquiry is no longer attached.


When creating or editing a ticket type, added an option "End of event" for "Prepayment closes" and "Registration closes".


Updated registration widget to set "style" attribute of widget iframe to be 300px (or value specified via data-width), to ensure that it displays with the correct width, regardless of the css of the page it is embedded in.


Within the community administration, improved the design of registration and member pages.


Require users to be logged into a Doorkeeper account with a verified email address to use the contact the organizer form. Introduced to combat an increase in contact form spam.

reCAPTCHA v2, which we were previously using, appears to have been beaten by spammers, and so is no longer an effective method. We've investigated reCAPTCHA v3, but as it tracks all your actions across the site and sends them to a third-party (Google), we're concerned about the privacy implications, and so have decided against implementing it at this time.


Require users to be logged into a Doorkeeper account with a verified email address to comment on an event. This is just a preventive measure to prevent spam comments, as we haven't had any spam comments since introducing this feature. However, because notifications about new comments are sent to participants, we're extra paranoid about preventing spam. In most cases, email addresses are automatically verified, so most users shouldn't notice this change.


When displaying the name reading (furigana) of a participant, use div tags with css, instead of ruby tags. Recent versions of Safari have a bug where ruby tags cause the webpage rendering to break under specific circumstances.


Improve display of "printable" pages: the guest list, receipts for tickets, tickets themselves, and receipts for a Doorkeeper subscription.

Prevent deletion of events with registrations. These events can still be published, and if all tickets are cancelled, the event can still be deleted.

Published our interview with Koichiro Nishijima (article in Japanese), a core member of JAWS-UG Okinawa.


Filter topic event listings by prefecture (e.g., Business events in Tokyo).


Improve display of tickets that have been added as Apple Wallet passes.

Tweak the design of page for choosing which community to hold a new event in.

When viewing event listings on mobile, show a single header for all events starting on a given date, rather than repeating the start date for each event.


Redesigned the event and community listings (such as your recommended events) to declutter the page, quickly provide you with the relevant information, and look better on mobile.


Introduce a page that lists all of your calendar feeds.


Improve performance of event participant export.