Crowdfunding the creation of the next version of LFGSS

Posted on
Page
of 66
  • ^^ Yes.
    ^ As soon as Microcosm is ready.

    Which is, as soon as it is stable (that bug list is empty and stays empty even with usage of Microcosm), has feature parity, and could cope with the load.

    Perhaps by the end of Summer. Sooner if we're storming along, later if we're bogged down.

  • Seeing some serious potential in this, well done so far fellas.

  • Seeing some serious potential in this, well done so far fellas.

    Am I rich yet?

    Well?!

  • strokes share certificates

  • Some time this morning, perhaps around 9:32am, the sandbox site will be reset.

    I have a couple of changes to the database that add columns, and as the new code refers to these column, not resetting the database will break the code.

    To those who are going ask about SQL migration and such. Yes, of course we'll do them, but not during the early part of the alpha when changes are likely to be quite frequent and people are cool with losing data.

    A few bug fixes will ship today, and the new events page (the create/edit is done, the read view is being refined). And we're planning to fix about 80% of bugs before next Friday.

  • An example of an event:
    https://sandbox.microcosm.app/events/1/

    Still broken (things like spaces and attendees not fixed yet), but you can see where we're going with that now.

    Imagine the first 80% of functionality that meetup.com or eventbrite offer... within a forum.

  • An example of an event:
    https://sandbox.microcosm.app/events/1/

    Bit short notice for me, sorry.

  • That's OK, it's not a real event.

  • performance seems to have taken a nose dive :(

    Indexes need recreating after the db change?

  • performance seems to have taken a nose dive :(

    Indexes need recreating after the db change?

    Could well be the case that VACUUM is needed.

    Trying to connect now to see.

  • PostgreSQL? - run a vacuum analyse - the planner stats are probably all off after the change (although if you are running autovacuum it should have picked it up)

  • Autovacuum is on.

    Though some tables still felt the need to be vacuum'd.

  • ok - feel free to give me a shout if you want any postgres help (replication, performance etc) - I spend a large part of my day job is pg DBA for some large (>100gb) databases

  • Persona is actually pretty annoying.

    It opens up in a popup window with no toolbars, so I can't just click on LastPass to insert my user details, I've got to fanny about opening up right click menus to insert my email address. Once I've done that it takes me to another page in the same popup where I've got to fanny about with the right click menus again to insert the same email address, this time with my password. Mozilla, y u fuck this up?!

  • Thanks, and I will definitely take you up on that at some point.

    For now, it looks like it was something in the Go code that caused it to stutter. I just redeployed the Go code with an extra piece of debugging info, and now the whole thing flies.

    Which leads me to believe that it was the Go code that was pausing.

  • Persona is actually pretty annoying.

    It opens up in a popup window with no toolbars, so I can't just click on LastPass to insert my user details, I've got to fanny about opening up right click menus to insert my email address. Once I've done that it takes me to another page in the same popup where I've got to fanny about with the right click menus again to insert the same email address, this time with my password. Mozilla, y u fuck this up?!

    Ah a fellow LastPass user.

    Does setting your details and logging on directly on their site not give you the prompts to save? https://login.persona.org/

    Once done, everytime I login with Persona LastPass correctly prompts for which identity and password to use.

  • What ver was just deployed? Was going to tag bugs which was fixed with that ver, to that ver...

    Also would be good to do this for future releases.

    That way we can generate release notes.

  • looks neat. BUT, does this mean the end of lists? This would be a massive cultural shift for LFGSS I worry!

  • ^^^ Yeah, it kind of works now. It adds my email address for me but not the password (even though there's only one possible password), maybe because the browser autofocuses on the password field and clears it*, so I've still got to do the right click thing to get everything. Wish they'd implemented that in a slightly less clunky way.

    *mahoosive guess

  • End of Lists. I welcome... :)
    You could still do lists, they're just inefficient...

  • Persona does not let me choose or edit any username, I can only add/remove e-mail addresses or reset my password?

    https://support.mozilla.org/en-US/kb/how-do-i-manage-my-persona-account

    I'm probably doing it wrong

  • You can edit your username from microcosm - click on your avatar image in the top right corner

  • Persona does not let me choose or edit any username, I can only add/remove e-mail addresses or reset my password?

    https://support.mozilla.org/en-US/kb/how-do-i-manage-my-persona-account

    I'm probably doing it wrong

    Persona is used for email + password authentication.

    Persona gives you the ability to use multiple email addresses, and then choose which one you want to share with a site.

    Persona does not do usernames or avatars.

    Once you've authenticated and are on Microcosm, we need to give you a username... and for now we just use whatever is before the @ symbol in your email address.

    You can change your username by clicking your avatar in the top right hand corner (we will make that more obvious... we just put the link there for now).

    You can change your avatar by going to http://en.gravatar.com/ and setting an avatar against your email.

    We are using Persona as it gives you far more security and does actually solve a lot of problems. With Persona, one really trusted party holds your password, and we never would. Which is a good thing. It also means that developers who make other clients will never have access to your password, also a good thing.

    We'd like to continue with Persona, as the benefits outweigh the cons.

    We use Gravatar because we're lazy and needed avatars but haven't prioritised building that bit... and using Gravatar is so easy for us as devs that we just put it in. But, it's a bit of a bad experience for you, signing up initially on Gravatar is a really bad user experience.

    Gravatar is convenient, but we're likely to roll our own avatars eventually as the benefits of us doing so outweight the negative (mostly in user experience, and as page speed is dependent on the performance of Gravatar we could probably best it by using CloudFlare).

  • What ver was just deployed? Was going to tag bugs which was fixed with that ver, to that ver...

    Also would be good to do this for future releases.

    That way we can generate release notes.

    That is a good idea, but I'm not sure how that would work really.

    We intend to always be releasing code many times a day... as in... continuously.

    We don't really do releases, unless you can class 10:37am on today's date as a release.

    We also don't do rollbacks... we prefer to roll forward fast. Which basically implies working with small changesets, and pushing them live fast, so that if something broke we can very quickly identify what did it.

    In effect, the commit log history and resolved bug list history is our changelog.

    With that in mind... what can we do that will help you, whilst we don't do the chunked release and incremented version number thing.

  • @bothwell & Velocio - cheers!

    looking good already, great job

  • Post a reply
    • Bold
    • Italics
    • Link
    • Image
    • List
    • Quote
    • code
    • Preview
About

Crowdfunding the creation of the next version of LFGSS

Posted by Avatar for Velocio @Velocio

Actions