This is an open suggestion and call to discussion (and potential/eventual action) directed towards the site admin/moderators, the developers of software such as ScriptPlayer and MultiFunPlayer (@Liquid and @Yoooi) as well as any competent software developer who might be willing to contribute to those projects on GitHub or the forum’s back end functionality.
Feedback on script topics has always been plagued with issues of how/when scripts are used.
When browsing topics, a user might leave a like if the script is associated with a video the user enjoys regardless of the script’s quality. Or, the user might download the script and video to use later and never return to leave feedback.
Here’s my suggestion:
MFP and ScriptPlayer could feature some minor form of EroScripts account integration, allowing users to like a script while it’s playing. Like, just a “heart” button that’ll leave a like on the topic from the user.
This way, feedback is more likely to be provided based on experience of the script itself in the moment.
OFS has a dedicated metadata text box for the script’s topic URL, which I imagine would be used for this and scripters would be encouraged to include it in the metadata in order to enable this form of feedback on their topic.
I know this sounds far easier than it is to implement in practice, but I’d love it if the developers and staff might consider giving their thoughts on the idea and potentially explain what would be needed in terms of coding effort in case community contribution might help make this a reality.
Also sorry if I’m coming off as ignorant, I’m not a developer myself I just really want the forum to improve where it can uwu
The protocol for that is OIDC (Open ID Connect) which is an authentication standard built into the oauth2 standard. All of this is FIDO alliance webauthn/webauthz standards.
Correct implementation allows another application to make specific requests for designated information in the forum. It’s a way to give an application access to bits n pieces of your account without giving access to everything, and also allows permissions and dynamic behavior with JWTs (Json Web Tokens).
The only concern might be user privacy. Certain applications might ask for more information than a user is comfortable, like an email address for a user’s primary key. Things like that will need careful thoughtfulness.
It’ll take me a bit to learn how to do it properly with discourse (hopefully it’s supported) but there’s no reason why that isn’t possible.
I think the metadata would have to be generated by the forum on download. Otherwise you would have to first create a thread, then copy the url into OFS, save the funscripts and update the thread.
Also probably better to have some custom metadata field with just the thread id to be used with the api, instead of using the full thread url.
Tbh thread likes do not sound like a good feedback solution to me, but I’m not a scripter. Sometimes there are multiple scripts in a thread, what would a like mean in that case?
Ideally the likes would be per file, but then when a script is updated the likes would be lost.
Or maybe instead of likes, a system similar to fleshassist review/scoring but for scripts. Then you would be able to filter the forum for scripts that match your desired property/category.
Also users might not bother with enabling the integration if it only allows them to like a script, they would probably want something useful out if it too, but I don’t know what that is, just display the like count from the forum in the apps?
Another possibility is to just automatically send each script play in MFP to the forum, kinda like a video view count. Tho that is basically user tracking.
Dimava can likely build this into the heatmap generation theme component. That would also mean that users would have to upload scripts to the forum since scripts published outside the forum won’t get those benefits.
I agree on this point, work is being done to improve this, unfortunately the ratings plugin is too buggy for primetime use at the moment.
I think we should only care about posts that work to care about the template. Malformed metadata should just be discarded imo.
That data can easily be anonymised. Just send a play counter with no data attached. Even an anonymous play can be valid.
Sounds good you can also see how many people are using specifics everyday, week and month and you could potentially add something akin to youtubes most replayed part on a script/video showing on the timeline. The option to leave a heart could be changed into different options such as “script not in sync”, “script is jittery” and other general problems.