2. Is it not possible to delete or archive notifications or messages? I’m concerned that they will accumulate over time and may affect loading performance.

Hi there,

Regarding the soketi issues you’ve encountered, these does sounds like a connection issue. Have you been able to launch soketi in debug mode and see if the failed connections logs any errors?

PS: I’ve recently become aware of some small socket-related issues/implementations on some pages (streams), where they are partially broken, so until that is fixed I’d actually recommend using pusher. Anyway, you should still be able to setup soketi either way.

2. There is not archive feature out of the box, but yeah, that could be done with a simple set of sql queries w/o any repercussions on the app side.

However, even on basic mysql, that table should be quite scalable, as we never fetch whole of it’s data, but only small sectors.

Also, other tricks could be done, like partitioning the table or even experimenting with moving it to a non-relational DB.

Overall, so far, there are no performance issues as far as I know.

Thanks, and let me know.

Ok, about the wesocket, I solved it, thanks. As for the translation of that sentence, inserting it like this into my file gives me a 503.

Other problems: When I try to upload a video, I have this error: https://i.postimg.cc/zBw7kgwC/videoerror.png The video can then be seen in the feed, but in this section the preview is not working

Hi there,

Regarding the translation, you need to make sure to enter it as valid json. EG: If adding that as the last line, delete the comma ”,”), as last line shouldn’t have it.

As for the video uploading issue—I think the preview fails to load due to the specific media file (EG: some weirder encoders for that respective media sample), or is this happening for all media files?

The transcoding driver might also play a role in this.

Thanks, and let me know.

Hi there,

No, at the moment there is not.

The blurring function has been tweaked a lot, and the main issue is that we’re using GD, the default image library that comes with all PHP installations.

We could have obtained a better blurring algorithm with other 3rd party libraries like ImageMagick, but the issue is that those are not really widely available on most of the servers.

We do plan to revisit this in the future—but in the meantime, feel free to send me a private message w/ sample/screenshots of your blurred previews, maybe there is something we can do about it.

Thanks and let me know.

Hi there,

There should already be a “Verified” badge that will show up on the user profile or different other places, like post comments.

We have some plans to actually replace that icon and check if it should added in any other places.

Thanks and let us know.

Hi there,

We will include more payment providers over time. A new one has been prepped for the next update already.

Can’t make any promises CoinPayments.net net yet, but I have added it to our internal list of possible upcoming payment providers.

Thanks & let us know.

Hi there,

Regarding referrals, the way it works is described over this docs link @ https://docs.qdev.tech/justfans/documentation.html#referrals .

The main takeaway is that users will only earn money if the user they refer is a creator and sells content. The user who initially referred it, will then receive a percentage of their sales.

This money is considered “advertising” money, and the platform owner ultimately ends up paying for if that makes sense.

Regarding withdrawals, no, there is no deduction, but the costs could be calculated based on the available data.

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

Thanks!

Hi there,

There are no known errors regarding the email verification system.

Q: What error are you getting exactly?

You might get an error if for example, you attempt to verify an email/account, while being already logged in on the platfrom, on a different account (this is a quite common false-positive).

Thanks and let me know.

I see my bad for not noticing it. By the way when it the next update?

No problem.

Regarding updates, we do not have an exact ETA but we do got some updates ready to go, will most likely be done in the following few days.

Thanks.

Hi there,

Thanks for the suggestion. We do plan to add more storage providers in the upcoming updates.

Thanks.

Hi there,

To be honest, I am unsure if Envato allows payments from Russia.

At one point, they allowed Skrill, which could have worked, but not sure at the moment.

Best would be to check this with Envato support if needed.

Thanks.

Hi there,

No, at the moment, such trial plans are not available, but we do plan to look into this possibility in the future—will let you know if I have any news on this one.

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

Hi there,

Unfortunately, there is no MetaMask implementation at the moment.

We do have some notes on it regarding a possible payment provider implementation, so this will be re-visited.

Thanks.

Hi there,

Unfortunately, there is no MetaMask implementation at the moment.

However, this is something we’d like to research in the future.

Will let you know if we have any news on it.

Thanks.

Hi there,

Replied with additional info over your DM/email message.

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

Hi there,

I’ve replied to your email thread. Let’s use that one for communication, so we can can the conversation context in sight.

Thanks.

Hi there,

That seems to be to true.

I’ve created an internal ticket to have this checked.

It seems like, at a glance, that the (user) field might not actually be used at all, so might be removed in the next versions entirely.

Will keep you posted, but overall, this shouldn’t cause any side-effects.

Thanks for letting us know!

It’s a rather straightforward fix instead of removing the feature altogether: 1. ‘identity_verified_at’ needs to be added in the $fillable and $casts array in User.php

2. Add in UserVerifyObserver.php: $user = User::find($userVerify->user_id); $user->identity_verified_at = now(); $user->save();

in the if-else statement where it’s $userVerify->status == ‘verified’

I see, thanks for the tips.

I think the only reason we added it is because no matter the ID-verify DB row, you can’t tell exactly when (datetime) the user got ID-approved.

Thanks again, will have this fixed in the next version.

Okay, okay. This is a suggestion, not an operational requirement. It will simply be useful if our new business model catches on and we need more licenses to build platforms for different clients. But I think it will also be useful for other owners of platforms built on JustFans.

You’re doing a great job.)

(Sorry, I deleted the above comment because Because by accident it changed to Polish while editing.

No prob.

Will also go over your DM bit later.

Thanks!

I didn’t quite understand what was going on.

Hi there,

Haven’t heard/seen this scenario until now.

If possible, can you send us a DM with your site link so we can check a couple of things as well?

Thanks.

Hi, I have sent you direct message ✌

Replied you over there. Thanks.

Hi there,

Indeed, there are no vaults, either for creators or customers at the moment.

A vault for creators makes sense, as it would save transcoding resources when, for example, sending media via messages.

But forthe customer’s end, they can preview the purchased media via feed/profile preview/bookmarks/lists.

Will let you know when we have news on this one.

Thanks.

How long do you think it will take until you have it ready? Maybe I try to add it as a feature on my own otherwise. Thanks

Hi there,

I don’t really have an ETA on it at the moment, but currently we’re quite queued up right now on the development side, so I’ll avoid making any promises.

If you do have the resources for it (money and developers), this is something that could be implemented as a custom change.

I will let you know if I have any news on this one.

Hi there,

For support inquiries, please write us a comment or send us a DM from the account you’ve used to purchase the product from, so we can verify the purchase.

Thanks.

Hi there,

I’ve went over your requirements, and I’ll try to let you know what’s supported and what is not, at least at the moment:

Creators can register, build a public profile with bio, links, tags, and upload photos/videos.

Visitors can browse creators’ profiles and galleries freely.

There is no subscription, tip, or purchase system enabled between users.

Can we disable subscriptions, tips, and private messaging without breaking the core functionality (feed, uploads, public profiles)?

So far, tags are not supported but planned for future updates. Then for the free use scenario. You can enforce free/open profiles, which require a follow, then the content is free (as on instagram per see).

But unfortunately, at the moment, tips/subscriptions can’t be fully turned off.

Can Stripe/PayPal be used only for platform-level payments, not for individual payouts to users?

Yes, payouts/withdrawals are manual/offline payments by default.

Overall, to be honest, it doesn’t sound like a great match for your use case, but could be worth an experiment. We will try to optimize free use case scenarios further more in the future, but for the forseable future, we’re already bottlenecked with ongoing releases.

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

Hi again,

Thank you for the detailed response earlier it helped clarify a lot.

I have one more important question before purchasing:

If I assign my own Laravel developer to work on the platform, will they have full access to the source code (Blade views, controllers, routes, etc.) so that we can:

Remove or hide subscription/tipping/messaging features

Keep only the profile system and public media uploads

Adjust the homepage and UI to match our use case

In other words: Is the code base fully open and customizable from our side (not encrypted or locked in any way)?

This would allow us to adapt the platform for our directory-style project, even if it’s not officially supported.

Thanks again for your help!

Hi there,

Yes, you do gain access to a copy of the source code, licensed under an Envato license.

Primarily, this enables you to customize the code as needed for the scope of your instance.

And yes, if you do have access to a laravel developer, all these sounds feasible.

If going this route, checking this guide will also be helpful @ https://docs.qdev.tech/justfans/documentation.html#custom-maintenance, so you can maintain your custom version against our master builds.

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