In my mind it would make far more sense to require a general stroker/vibrator/estim tag (or whatever other concrete device types there are) and then autotag the topic with the scripts max speed rounded up to the nearest 100 (e.g 527mms peak → “max-speed-600”).
Since the script gets processed for the heatmap already, we already have access to the peak speed.
Functionally what is the point of differentiating for example launch and the-handy? They both have about the same speed, with the only real difference being that the launch is Bluetooth only, but a script shouldn’t be any different for it.
My main complaint is, the average user has one device, what value will they get from seeing that a script is for example tagged “sr6” if they most likely don’t even know what that is.
Personally i also now have the problem of not being able to choose a device to tag. I script with strokers in mind but use restim to turn that linear script into e-stim instructions. Tagging it as e-stim for example would just misrepresent the script in the eyes of anyone looking at tags before opening a topic.
Also a user might tag their script as the-handy, but script with a peak speed of 900mms, what good would the-handy tag have been in that situation?
I think at the end my main complaint, is that the device tag gives me no useful information aside from if this is intended for strokers or not.
(now that i think about it, it’d make sense to require a tag for single-axis/multi-axis as well but that’s a different discussion)
This doesn’t account for different capabilities like mmps or stroke length. Scripts are often tested on different devices and it would be beneficial to have a “This definitely works best on X” sort of tag.
This requires no small effort of a plugin. If you build it we’d be glad to implement that.
It’s no secret that H1 was for a long time the non-DIY king of strokers and dramatically out performed the launch, KEON, etc.
H2 makes that difference even more dramatic with it’s up to 1200-1600 mmps
Which is why they might want to find scripts made for their device.
That’s an interesting point. I don’t know enough about e-stim devices to know how much that would impact the tag’s usage.
The device tags are not for specific specs. It’s “This script was tested with” or “This script was made with this in mind” It’s a marker of user experience rather than specific specs.
I think this is a problem of UX rather than the logistics of the tag. I’m wondering if there’s a better solution here that resolves both issues.
An issue I had is when editing topics with scripts made for vibrators even when that tag is already applied I’m forced to add a stroker device to add other tags. The tag for vibrators/e-stim do not count as a device tag.
Heres a proof of concept, hooks into post_created and parses the first attached funscript to get and tag max-speed-xxx on the topic. I’ve never worked with ruby/discourse so this might be terrible ¯_(ツ)_/¯. (The whole skeleton can be kinda ignored, the code is only in plugin.rb i just couldn’t get my local discourse instance to recognize the plugin without the skeleton)
Curious, what stroke length is being used for the current heatmap speed calculation? I just assumed 11cm for the H1 for now.
I’m not against the tags per se, i just don’t think they should be required.
I just don’t think adding the device as a required tag is worth the extra hassle on the users side, length for example i can see the purpose behind and think it was a great addition. Device though? I don’t think the average user will ever care about that tag.
At the end of the day i don’t really care, I’ll just select something that roughly fits for when i post. I just think the implementation of it seemed a bit hasty from what I’ve seen.
In my mind any little bit of extra effort on a users side will result in less people uploading their scripts but that might just me being pessimistic.
I realize now, this is mostly about paid scripts isn’t it? You can go ahead and disregard like most of that paragraph in that case. I still don’t think it should be required on free-scripts because of the mentioned reasons. But i can’t comment on the paid scripts section at all, I found a few scripters i liked and basically never check paid-scripts on eroscripts. I just check from time to time to see if there are any new scripters that script what i want.
I feel like (from what i skimmed) people more so wanted a rating system for paid scripts, although i have no idea if Discourse supports up & downvoting.
i think instead of generic device names we should have tested-with/made-for-xyz tags then, I’ve already seen a free script that had e-stim as a tag because it was in the video.
Eh, I’d be fine just getting a generic device tag. I’m scripting like i’d script for the handy. I just don’t test it on one. (and have no speed limit, although i stay under the H2s limit of 800?)
To summarize:
I think required device tags should be paid-script only
maybe add a generic device tag for if the others don’t apply?
maybe rename/add the required tags with tested-with/made-for-xyz
autotag-speed-plugin (def needs someone who knows what they’re doing to look at it)
This discussion makes me thing perhaps we should revamp how the multi-axis tags work instead.
For ex. instead of a specific device, have the tags themselves be: #axis-vibration, #axis-twist, #axis-stroke, etc…
It’s more specific than just “more than 1 axis” and makes the same generic device expectations.
We can also still make the specific devices optional to include.
Or perhaps we just need a standard definition of Device vs Axis vs Device Type
like:
Device: Handy 2 pro (name)
Axis: Stroke (list of axis)
Type: Stroker (Generic device category)
idk about implementation though.
I don’t want to setup complicated names for tags. If a simple name doesn’t suffice with a descriptor, we’ll end up with mile-long tags that take up the whole screen. It would be best to have a system of simple names and a dedicated post to map out purpose like we (partially) have here. Obviously it could be expanded to not just the required tags.
I don’t see how paid scripts differ in this context. The requirement was added because of earlier discussion and I agreed.
Absolutely! I remember having this discussion on here and not everybody was a fan unfortunately. I for one would love to see this be done this way. Just be aware of the tag limit.
So part of my suggestion came from me getting a Keon, only to realize how hard it is to find technical information but also how the tech compares to feel isn’t a truly 1:1 comparison. I found out the hard way that my scripts were bad, hitching, having poor movements because the script player i was using at the time only supported linear interpolation and that they were going way too fast either because of the polling rate or the step rate, and i had to switch to MultiFunPlayer for its step interpolation mode. The issue i wanted to solve is basically so users (both makers and users) can share “hey this works best on this device” because by nature of being a porn site, most users are not going to be that active or talk or rate everything. So having at least the dev say “tested on this” can help give you a framework to look for, and also be something you can sort. As a keon owner, requiring more users to use the Keon tag for example means i immediately have more scripts i can search for that i know should be fine without me doing extra stuff.
Not totally wrong. While i think its good to have some sort of tag for free or paid, (my original post even mentioned an untested tag) as i stated in the thread, i do pay for some scripts and while i love OTEs both scripting style and content scripted, hardly any of them work for me without me going into something like funscript.io and doing some manual configurations. And while i am willing to do that much work even for something i pay for, i did have other creators that i stopped paying for because there scripts just wouldn’t work without me basically redoing the whole thing by hand.
I actually do agree that it shouldn’t be a “hard” requirement, hence the “untested” option or ability for user testing to get a tag or rating added per device (for example for older uploads). There is also the case that while a script might not work great on a particular device (say it goes to fast), maybe the combination of your sleeve + interpolation settings means it works well and feels good even if its not a great fit for the device. Me using step interpolation pretty much exclusively is a good example of this, as i assume most scripts are made using linear interpolation as that seems to be the default for some devices on a hardware/firmware level and is seemingly always the default in all players ive used. Thats why i suggested the idea of having the tag be a ranking like “Keon 6/10” that accumulates from user reviews in case those situations did occur for a lot of people. Plus any user ranking something on a per device metric, while often without context and must assume the default configs of that device, will encourage more users to give that context which can help in finding the right fit or making better scripts.