quisquous@discuss.tchncs.de to Technology@lemmy.worldEnglish · 2 年前Advice for Operating a Public-Facing APIjcs.orgexternal-linkmessage-square3fedilinkarrow-up136arrow-down11cross-posted to: [email protected][email protected][email protected][email protected]
arrow-up135arrow-down1external-linkAdvice for Operating a Public-Facing APIjcs.orgquisquous@discuss.tchncs.de to Technology@lemmy.worldEnglish · 2 年前message-square3fedilinkcross-posted to: [email protected][email protected][email protected][email protected]
minus-squared3Xt3r@lemmy.worldlinkfedilinkEnglisharrow-up6·2 年前 Avoid OAuth But what’s the alternative? “Use static API tokens” doesn’t really say much. What’s an actual alternative that doesn’t require a custom solution/reinventing the wheel?
minus-squareUcinorn@aussie.zonelinkfedilinkEnglisharrow-up1·2 年前Static API tokens ARE the alternative. He’s saying oauth is not worth the complexity, and increase the barrier to entry to using his API. Static API keys are not a new or customer solution, they are the baseline. He’s saying stay at the baseline, oauth is not worth it.
But what’s the alternative? “Use static API tokens” doesn’t really say much. What’s an actual alternative that doesn’t require a custom solution/reinventing the wheel?
deleted by creator
Static API tokens ARE the alternative. He’s saying oauth is not worth the complexity, and increase the barrier to entry to using his API.
Static API keys are not a new or customer solution, they are the baseline. He’s saying stay at the baseline, oauth is not worth it.