quisquous@discuss.tchncs.de to Technology@lemmy.worldEnglish · 1 year agoAdvice for Operating a Public-Facing APIjcs.orgexternal-linkmessage-square3fedilinkarrow-up135arrow-down11cross-posted to: hackernews@lemmy.smeargle.fanshackernews@derp.fooprogramming@programming.dev
arrow-up134arrow-down1external-linkAdvice for Operating a Public-Facing APIjcs.orgquisquous@discuss.tchncs.de to Technology@lemmy.worldEnglish · 1 year agomessage-square3fedilinkcross-posted to: hackernews@lemmy.smeargle.fanshackernews@derp.fooprogramming@programming.dev
minus-squared3Xt3r@lemmy.worldlinkfedilinkEnglisharrow-up6·1 year ago 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-squareAccidentalLemming@lemmy.worldlinkfedilinkEnglisharrow-up2·edit-21 year agodeleted by creator
minus-squareUcinorn@aussie.zonelinkfedilinkEnglisharrow-up1·1 year agoStatic 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.