Hi there,

Unfortunately, we can not make any promises regarding this feature proposal or any in general.

The September/admin-related update announcement is a bit of an exception, as there are a couple of small admin things that people are waiting for and will be fixed with the new one (plus, it is a big update on which we have been working for the last few months).

Anyway—I will create an internal ticket on your suggestion so we can have it reviewed.

Thanks!

Hi there,

Yes, this is a limitation on the ffmpeg side. During product lifetime, we’ve been reticent of adding queues/background jobs, as this is not a feature widely supported by shared hostings, which make up a big part of our customers hostings.

At the moment, a good alternative (but probably more expensive) would be to use coconut.co transcoding driver alternative, which does process them on their remote infrastructure, in the background.

Thanks, and let us know.

Hi, thanks for the explanation.

Currently, using Coconut is not an option for us due to cost considerations. We are running on a dedicated server, so we do have more flexibility compared to shared hosting.

Could you please advise on what optimizations we can apply in our setup to reduce 502 errors when simultaneous video uploading and FFmpeg transcoding occur?

Also, may I ask if there are any plans or improvements in the next version of the script to handle this part more efficiently, such as built-in queue/background processing options?

Hi there,

Unfortunately, there won’t be many optimizations you can do, as this pretty much comes down to the raw power of the server and ffmpeg capabilities, which, for example, doesn’t even scale that much after 64 cores.

We do plan to revisit the area, and yes, queued jobs would be a great fit, at least to better manage failed jobs and concurrency/delaying tasks.

Thing is, we’ve avoided as much as we could using queue services, as they are not trivial to setup/maintain and we’re trying to offer a feasable solution to all customers, including ones running on shared, low-cost hosting packages.

Anyway, we do have an internal ticket on this matter and will try to revisit it as soon as we can.

Will let you know if we have any news on this one.

Thanks, and let us know.

Hi there,

If possible, please send me a DM @ https://codecanyon.net/user/ic0de#contact and I will have a look over your instance.

Thanks, and let me know.

Hi there,

I understand what you mean, but yes, as mentioned, this is not just a visual-style related update; it would also require custom backend changes.

Unfortunately, I can not make any promises on this one, and also, all the marketplaces I am using are using the same implementation.

If you can send me a DM, I can forward you some contacts that might be able to help you with the custom changes implementation.

Thanks and let me know.

Hi there,

Though we usually do not have public ETAs for upcoming features, for this one, I can tell you that the new admin is pretty much done and should be released either later this month or by 1 September top.

As mentioned, all the heavy stuff is complete, but we’re still polishing some small things for the best experience possible, out of the box.

Thanks, and let me know if you have any other questions.

Hi there,

Generally speaking, following this update guide should cover the main update procedure @ https://docs.qdev.tech/justfans/#update .

Reason for why you might get the installer after update is:

• Missing storage/app/installed file (if you see the installer after update)

Just create an empty `installed` file (no extension) at `storage/app`.

Thanks.

Hi there,

Unfortunately, no, the support package does not cover installation/updates/configuration, or custom changes, but we can assist you with any issue/question you might get during the setup.

As for your PayPal-related change, I suspect this would require a custom implementation, is not just a matter of the logo.

If you’re looking to change the logo, you can simply replace the svg located at public/img/logos.

Thanks, and let us know if you have any other questions.

Hi there,

At the moment, there aren’t such plans, but we’ll create a suggestion/idea note so we can revisit and reconsider this.

Thanks for the suggestion, and do let us know if you have any other questions.

Whats your roadmap/future update yall working on?

There is no public roadmap/release schedule we work on.

Hi there,

This does look interesting, will add a note on this on our internal ticket regarding possible upcoming payment providers.

Thanks

Hi there,

It does seem like the Larix app has gone through some recent changes; it now seems like they’re asking for a monthly subscription in order to be able to stream (at least w/o the overlay).

From what I understand, this is their choice to be able to pay their developers. I know this might not be that pleasant, but at the same time, streaming/broadcasting is a complex area, and some costs might appear, even on the streamer side (and this is a global thing, like all YouTube and Twitch streams are going through this, it is not a JustFans thing).

From my research, this app continues the free Larix legacy, and is actually based on the paid Larix SDK, but only works on Androids @ https://play.google.com/store/apps/details?id=app.irlpro.android&hl=en .

Tested it myself as well, and it looks really good.

Thanks, and let me know if you have any other questions.

I can confirm that it works fine with the IRL Pro app. Should I update the instructions on JustFans?

Hi there,

Yes, if you want, you can update the instructions for your site.

I am still unsure if we’ll be able to use this one, as for now, it is not iOS compatible/published.

Anyway, thanks for letting me know about this. I wasn’t aware of the recent Larix-related changes. We’ll try to do some more research from our end and see if there are any other cross-compatible, free apps that we could update the instructions for. Or even try to reach out to the IRL pro app developer and ask him for future plans regarding IOS.

Thanks, and let me know if you bump into any other questions.

Hi there,

I honestly don’t have an exact answer on this one. This is the reason why we’ve added options to only allow payment providers on wallet top up.

But I can’t really make any promises in the sense that this will bypass the TOS of payment providers that don’t allow high-risk/adult payments.

Thanks, and let us know if you have any other questions.

Hi there,

Though we have a list of 80+ of possible payment providers, it looks like Skrill was not part of it, so I’ve added it now.

However, I can not make any promises/give you any ETAs on it at the moment, as we have some other ones possibly queued up in line.

Meanwhile, you do have some options for NSFW content, like CCBill, Verotell, Crypto, or offline payments, which you could use instead of paypal/stripe.

Thanks and let me know.

CCBill – They don’t accept customers in Australia, I need to be located in American Verotell – I believe need to pay 500 Euros for the yearly cost

Hi there,

The high-risk payment fees must be paid for all payment providers, as far as I know.

From what I remember, it costs 500$/yr for Mastercard and another 500$/yr for Visa.

There isn’t any workaround for this if you want to do it properly, but you can consider using alternative solutions, like crypto/offline payments.

Thanks.

Replied to you over there. Thanks.

Hi there,

I am not sure exactly which pushrcdn feature you mean, feel free to send us a DM with more info, and we can look into it.

Thanks.

Hi there,

Ah, I see—this is the equivalent of pre-signed urls from AWS S3.

At the moment, pushrcdn signing is not supported—but I will create a ticket so we can have this investigated and maybe try to implement it with upcoming versions.

Thanks.

Hi there,

Actually, with the v8.2.0 version, we did implement an alternative WebRTC-based streaming driver, based on liveKit, which can either be used in a hosted manner (eg: buying streaming services from livekit) or on a on-premises/self-hosted approach, if you can manage your infrastructure.

You can read more about it @ https://docs.qdev.tech/justfans/documentation.html#streaming .

Hope that makes sense, but do let me know if you have any other questions.

Hi there,

Yes, unfortunately, at the moment, this is not a feature supported out of the box—but now that you mention, it actually makes sense so for example you can ensure you don’t host “zombie” streams, loosing money.

I have created a ticket on this matter so we can implement it out of the box with upcoming versions.

I wouldn’t be able to give you instructions on how to achieve this from the top of my head, but, if for example, you’re using a IDE/code editor, you can search for “stream” files, this would return you the controller (php), the blade (html) and the css & admin file.

All files are named in a quite suggestive manner. EG: All files should follow the same naming structure as for example, the homepage @ https://docs.qdev.tech/justfans/documentation.html#homepage-edit .

Thanks and let me know if you have any other questions.

Noted, thank you. Wish will got this feature soon.

Hi there,

Please send me a message @ https://codecanyon.net/user/ic0de#contact and I will get back to you with more info on this.

Thanks!

Hi there,

If possible, send me out a DM with additional info, and if possible admin & cPanel credentials.

The fact that you get “No available” updates on that step, it might inidicate the files copy step might have silently failed (it does some some cPanels), hence the other errors.

Thanks and let me know.

Sounds good – let us know if you bump into any other issues.

Hi there,

Unfortunately, no, there is no way to change the “upload domain” so to speak.

What kind of error do you get for such failed exports? Is it a CF related error or a web-server related one?

Generally speaking, for videos at least, the transcoding service can also play a role (EG: The actual upload might go on, but the transcoding can timeout, beyond max CF timeouts).

Thanks and let me know.