Extiverse. Breaching the frontier in Flarum forum and community management

GreXXL

I also like Version A - there are so many subscriptions (non-flarum related) ongoing I think it will be hard to "sell it".

MikeJones

I vote A

Juba007

I also vote for A

almalino

I somehow think B is more manageable though A looks better for individual contributors. I vote for B.

almalino

Can both approaches be implemented? 🙂

askvortsov

almalino I think too many options at once might be confusing and dilute potential impact.

luceos

I think I'll stick to option A for now. I've also started with that implementation already and the consensus seems to point at that one too. I'll try to push forward with this feature during my couple of days off this week.

Darkle

I really like this idea, it's a way to formalise the crowdfunding of extensions, as right now it's quite complicated to give visibility to an idea and get it off the ground. I agree, option A is probably the best way to start and see how it works.

luceos

Darkle Iterative development is pretty much what I think is commercially and motivationally the best approach. That's also why I want to get a first version out as soon as I can and then hear the opinion from all sides about areas for improvement.

Justoverclock

@luceos i'm trying to validate my account on extiverse, but when i click on the validation email, it says "invalid signatures"

luceos

I've implemented a new design, which is much darker. This comes with an upgrade of tailwind and laravel mix. There are still a ton of issues while I patch things up the coming days. Feel free to report any layout or major styling issues you find.

Justoverclock Can you ping me on discord? I'm on holiday right now so I'll need to check when behind a PC.

GreXXL that's an older issue. I'm going over some rudimentary styling changes this week.

GreXXL

When viewed on mobile devices there are some styling issues making content unavailable to view. See screenshot:

rob006

Is there a chance to add to API actual constraint for flarum/core used by extension, instead of simple compatible-with-latest-flarum flag? I have different rules for detecting compatible extensions, and it is really hard to guess how exactly treat some premium extensions marked as incompatible at Extiverse.

luceos

rob006

in your api request add the include versions
retrieve the highest-version from the attributes
use the highest version to retrieve the versions from the included payload. The field flarum-version-required is the exact constraint.

luceos

I am considering building an Extiverse extension that:

shows one button in the dashboard stating "up to date" or "outdated"
has a new tab where you can see all your current extensions and whether they have updates
the ability to use a cronjob to send email notifications to admins when new updates

Would this appeal to you?

luceos

luceos release as extiverse/mercury

Extiverse no longer syncs extensions each hour from packagist. Their endpoint was cached and has been marked deprecated. So I decided to switch over to their endpoint that allows reading just changes. As a consequence Extiverse now sees changes to extensions within 10 minutes. A full sync happens each night to make sure nothing is missing.

Premium extensions are an exception as they still are synced only hourly. I don't want to push too much weight on the VCS providers by reducing that interval.

If you encounter any issues with missing data or delayed updates, please let me know.

Darkle

Am I the only one who is constantly being pulled out? For the last few days I have been getting logged out after a couple of hours even if I log in again with the remember tick.

luceos

Darkle will look at this as soon as I can. Sorry that this happens, must be frustrating.

GreXXL If you purchase an extension and get redirected back to extiverse after payment you land on the subscription page. The only downside the newly purchased extension is not shown - only after a page refresh

You should be redirected to the page that lists your active subscriptions, not the available subscriptions of the extension. Will look at that.

GreXXL The login/sign up is really badly visible especially on mobile (like iPad). It should be moved directly under the extiverse logo in the sidebar and not at the very bottom.

Okay. A redesign is planned, just not sure when I have the time or money to do that. Extiverse hasn't even surpassed break even yet.

GreXXL

I have made two observations - both non-critical - but wanted to mention still 🙂

If you purchase an extension and get redirected back to extiverse after payment you land on the subscription page. The only downside the newly purchased extension is not shown - only after a page refresh 🤐

The login/sign up is really badly visible especially on mobile (like iPad). It should be moved directly under the extiverse logo in the sidebar and not at the very bottom.

GreXXL

luceos You should be redirected to the page that lists your active subscriptions, not the available subscriptions of the extension. Will look at that.

I think you are redirected to your subscriptions, it just doesn't show the newly added one without refreshing 🙂

luceos Okay. A redesign is planned, just not sure when I have the time or money to do that. Extiverse hasn't even surpassed break even yet.

Do an Collective, I'm in?

Darkle

luceos will look at this as soon as I can. Sorry that this happens, must be frustrating.

About this I wanted to clarify, a few days ago I completely cleaned my browser and the error has not happened again.

So it was from my side, but maybe caused by this, when the problem started was the same day I deleted lots of "composer" tokens that I had been creating over time and by mistake I also deleted the "app" token, maybe this caused it and there is a bug that doesn't allow to restore the "app" token after deleting it (?)

« Previous Page Next Page »