We still use Meetup for our functional programming meetup that's been going on for about a decade, but I gotta say as an organizer, it's a very buggy piece of software.
Editing an event never goes smoothly, it pretty much always eats half of your edits, etc.
It's also not exactly free. But it's risky to try to move a large group onto some new platform, so here we are.
It absolutely would - if you accidentally pressed back or refreshed the page, if fields don't pass validation, if there's a server error or a network issue when you try to submit, if your credentials expire while you're editing, etc.
Not defending meetup but people have every reason to try to override default UA behavior.
Comments
We still use Meetup for our functional programming meetup that's been going on for about a decade, but I gotta say as an organizer, it's a very buggy piece of software.
Editing an event never goes smoothly, it pretty much always eats half of your edits, etc.
It's also not exactly free. But it's risky to try to move a large group onto some new platform, so here we are.
It's sad that webdevs ditch web standards in favor of painful implementations, in many cases just for bells and whistles in exchange.
What we get is what you described.
I wish more editing forms were just a <form method="POST"> with <input value="whatever" /> and an <input type="submit"> for me to click.
No system designed around that would ever eat up half our edits.
It absolutely would - if you accidentally pressed back or refreshed the page, if fields don't pass validation, if there's a server error or a network issue when you try to submit, if your credentials expire while you're editing, etc.
Not defending meetup but people have every reason to try to override default UA behavior.