Standard Grant: Lume Web 2025

Grants Inactive
11

Progress Report for January

What progress was made on your grant this month?

  • Had to handle weird issues with TUS uploading on the pinner.xyz portal and double check uploading was working properly in general
  • renterd took a lot longer to sync then expected
  • Rest of the month has been spent on rebuilding the billing support.
    • The existing implementation after reviewing things turned out to be badly designed without a full understanding of killbills state machine system.
    • The justpay-written plugin needed a lot of changes to properly use the killbill apis.
    • This included significant rewrites to the hyperswitch java plugin, and dealing with upstream library issues. Most of these updates are still in WIP branches, but the hard parts of the billing backend systems should be done.
    • The billing plugin also has had significant changes and will have more in the future.
  • A design for the abuse report webapp has been created and ready to be ported for the Q1 anti-abuse priority.

Summarize any problems that you ran into this month and how you’ll be solving them.

While I currently consider the billing in a 90-95% ready state, I am intending to do another refactor of the webapp code base and create a frontend framework/foundation with module federation. Due to this, I am punting the billing support until after this is done with the goal of it being finished by the end of Q1.

This will also be used as a basis for the admin webapp/plugin as well.

I don’t wish to put effort into the web part of the billing further and need to scrap it. This also means further UX work will be punted until there is a better webapp foundation.

As a secondary concern, hyperswitch’s cloud pricing has changed, and went to target enterprise, which means I will have to self host a card vault and go through required compliance measures to bring billing online. I was considering it as a temporarily way to deploy faster, but thats no longer in the cards, it seems.

Links to repos worked on this month:

What will you be working on next?

  • I will be bringing the free portal online and doing any required devops work along the way.
    • I am also intend to be doing some server migration efforts and restructure things. Looking to adopt proxmox and put infra inside virtualization, which would allow use of another layer of redundancy/safety as well as using the proxmox sia plugin with an outside renterd instance.
  • Will work on the webapp foundation priority
  • Will work on S5 support assuming no blocking issues from redsolver. I have also made the decision that S5 will be an API-first service upfront with no UI support in the webapp given most planned app use cases will use the API. a UI will be added based on feedback. This is to reduce the eng time needed to bring S5 demand online while balancing other Q1 priorities.
  • Will do needed research on the anti-abuse and create a game plan for it. Will start those efforts if I have the time.
    • Know that anti-abuse will be a subsystem of the admin panel… which will require the new web foundation, so all of this is being prioritized on importance and is very inner-connected.
  • Will likely be doing some portal core design updates and possible plugin API changes, As stated in the past, these will continue as deemed needed for the evolution of the system, and is a large reason why no v1 in semver exists yet.