The next major release, 1.3.0, is coming along nicely.

Most of the polish I wanted to add has been added, features tested, and things are going smoothly (after a few unexpected setbacks, naturally). Just a handful of items remain to be (re-) implemented before it will be ready for a beta and eventual release.

Note: 1.3.x will be the last version to support the 0.18.x API. Once development of 1.4.0 begins, 0.18.x support will be dropped.

Remaining Tasks

  • Complete redesign of remote instance community browser (currently at like 90%)
  • Replace the local community page with the updated version
  • Re-implement the custom feeds to pull more initially, store to local storage, and build the actual feed from that. Should allow a better mixture than the current implementation which only pulls 1 page at a time. This is most evident when the feed group is a mix of active and less-active communities.
  • Create a /instances route and page components to see the blocked/allowed and linked federated instances
  • Add additional moderator tools to community settings
    • Direct ban/unban user from community (similar to how adding/removing a mod works now)
    • In addition to the “community modlog” button, provide a simpler modlog just for that community
  • Refresh “Create post” page (wasn’t on the list until just now as I’m posting this)

Once those are done, I’ll test and fix bugs before releasing the beta to GHCR and launching that on my own instance to find/fix any last minute bugs that slipped through the cracks.

1.3.0 Resources

  • Admiral Patrick@dubvee.orgOPMEnglish
    2·
    6 months ago

    Thanks :)

    Two answers for the bugginess:

    I’m constantly redeploying that dev instance, and every time it’s rebuilt/redeployed the JavaScript assets change names. So it tries to load files that no longer exist.

    I’ll notice similar behavior if I try to use a stale tab after redeploying. AFAIK, that’s just a Sveltekit thing.

    OTOH, some things are actual bugs. Those are usually just the parts I’m actively working in, though.

    I’d be happy to help do some full testing. I don’t have a github account but can post bugs here if that would be helpful.

    That would be greatly appreciated. Might want to wait until I deploy the beta to the main frontend that way it’ll be easier to tell what’s a bug and what’s a side effect of constantly redeploying. Though if something is glaringly wrong in the dev version, feel free to point it out.

    • Jenny! [she/her]@dubvee.orgEnglish
      1·
      6 months ago

      Ah, that makes sense. Hope I didn’t sound too negative. I really am loving the new look 😎

      I’m definitely going to keep playing around with the dev one but will wait for the main one to be updated before putting in any bugs.