Post AwXTy0n6CDpFTJZNOS by buttplugio@buttplug.zone
 (DIR) More posts by buttplugio@buttplug.zone
 (DIR) Post #AwXTxrCxpCZbkdatJw by buttplugio@buttplug.zone
       2025-07-26T20:44:33Z
       
       0 likes, 0 repeats
       
       it's happeninggggggg
       
 (DIR) Post #AwXTxsr3hcEurHMQSG by buttplugio@buttplug.zone
       2025-07-26T21:39:29Z
       
       0 likes, 0 repeats
       
       I haven't had to write a REST API for rando dev use in forever. Usually I'd build urls as referrers into data structures, commands as JSON bodies.Considering also exposing setting values (vibe speed, positions, etc) in URLs to be dead simple as possible.So: [url]/devices/1/features/1/outputs/vibrate/with a json body for the value, or just[url]/devices/1/features/1/outputs/vibrate/0.5Which kinda violates formal rest but also means full control via URL formation alone.Thoughts?
       
 (DIR) Post #AwXTxuDQdvjB4wpnxg by alex@feed.yopp.me
       2025-07-26T22:18:26Z
       
       1 likes, 0 repeats
       
       @buttplugio please-please-please pass parameters as url parameters PUT /devices/1/features/1?vibration=0.5&position=3&stuff=42Query parameters are much easier to work with than building huuuge url (and memorizing the order along the way)
       
 (DIR) Post #AwXTy0n6CDpFTJZNOS by buttplugio@buttplug.zone
       2025-07-26T21:48:24Z
       
       0 likes, 0 repeats
       
       I should point out: the goal here is not just ideological purity, it is SHITPOST ACCELERATION.We need devs to go from zero to vibration for whatever stupid reason they came up with ASAFuckingP.But there's two camps : bash script + curl, or actually knows how to use APIs.