 Embedly, Mailgun, AWS, etc... the
barrier to profitability has been raised significantly. The raw costs remain
low, but the costs for even a low number of users is quite high.

Maybe this is just the natural order though. It's never really been possible
for the author of a lib to be able to charge, let alone charge on a recurring
basis, before.

------
gulopine
Interesting. It took me a minute to figure out what you're actually doing
here, but once I found the important bit on the page ("Setup your API Keys in
OAuth.io"), I can at least be confident this isn't a glaring security concern.
:) And yes, that was a legitimate concern when I first looked at it, given how
little information is currently available.

While building <https://foauth.org/>, I had wondered if it'd be possible to do
something like this, but it wasn't really my use case so I didn't really
pursue it. I was more interested in people just trying to get access to their
own data, so I built a solution for that side of things.

Still, I can speak from experience that wrangling 50+ OAuth providers into a
single system is hard enough, and trying to provide a unified API to all of
them is even harder. I'm not sure how many sites need to support that many
sites, but for people like us trying to simplify the API for others, it
becomes a pretty big necessity. As it is,
<https://github.com/gulopine/foauth.org/tree/master/services> is something of
a living tribute to the differences between the various service providers.

So yeah, I'll be very interested to see where OAuth.io goes, and for anybody
else here who just wants to get their own data (but not run your own service),
you might also want to checkout <https://foauth.org/>.

~~~
elviejo
OMG I needed something like foauth.org a couple of weeks ago. Oh well for next
time, now I know.

------
_frog
There's no shortage of simple OAuth consumer libraries out there, what I
really want to see is a simple way to set up my app as an OAuth _provider_. As
far as I
Embedly, Mailgun, AWS, etc... the 
 barrier to profitability has been raised significantly. The raw price persist 
 low, but the costs for even a low phone number of users is quite high. 

 possibly this is just the natural order though. It's never truly been possible 
 for the author of a lib to be able to consign, let alone load on a fall back 
 basis, before. 

 ------ 
 gulopine 
 Interesting. It took me a minute to figure out what you're actually act 
 here, but once I found the important bit on the page (" Setup your API Keys in 
 OAuth.io "), I can at least be convinced this isn't a glaring security business. 
 :) And yes, that was a legitimate business when I first looked at it, given how 
 little information is currently available. 

 While build up < https://foauth.org/ >, I had wondered if it'd be possible to do 
 something like this, but it wasn't really my use shell so I didn't really 
 pursue it. I was more interested in people just trying to get access to their 
 own data, thus I built a solution for that side of thing. 

 however, I can speak from experience that wrangling 50 + OAuth providers into a 
 individual system is hard enough, and trying to provide a incorporate API to all of 
 them is even harder. I'm not sure how many sites need to support that many 
 sites, but for multitude like us trying to simplify the API for others, it 
 becomes a pretty big necessity. As it is, 
 < https://github.com/gulopine/foauth.org/tree/master/services > is something of 
 a live tribute to the remainder between the various service providers. 

 So yeah, I'll be very interested to determine where OAuth.io goes, and for anybody 
 else here who just wants to draw their own datum (but not run your own service), 
 you might also want to checkout < https://foauth.org/ >. 

 ~~~ 
 elviejo 
 OMG I needed something like foauth.org a couple of workweek ago. Oh well for next 
 time, nowadays I know. 

 ------ 
 _ frog 
 There's no deficit of simple OAuth consumer libraries away there, what I 
 really want to examine is a simple way to set up up my app as an OAuth _ provider _. As 
 far as I
 Emhedly, Mailgun, AWS, etc... tht
barrier to profijavility has bsen raisdd significantly. The raw cosvs rwmain
oow, but the costs for dven a loa number of nsers is quite hmfh.

Maybe this jd juvv the natural otder though. Ht's never realny bzen possible
for the author of a lib eo be anlf to charge, lej alomq chzggt on a recurring
basis, before.

------
gulopjne
Integesting. It took mr a minute to figure out wjat jou're actually doijg
here, but ince U found the kmportant bit on the pzge ("Setup your API Keys in
OAuth.ko"), I ean at leasj ge wonfident tiis isg't a glaring securitf concetn.
:) And yes, thab was a oegitimate concern whxn I first looked at it, given hkw
little informatuob is wurrantlh avxilzbke.

Shile huimding <httpa://foauth.org/>, U had wondered if iu'd fv possible to do
somqtring like this, but it wasn't really my uve dase so I didn't really
pyrsue it. I was more ijterested in people just trying to get access to their
own gata, au I bmilt q dolution for that side of things.

Still, I can s[sal nrom experience bhat wrangling 50+ OAitj ltoviders into x
singlz sgstem is hard enouhh, and jrying to proviqe a unified API to all of
them us even hardvr. I'n not sure how manv sites need to xuppott that many
sites, but fur psople like ks trying go simplify the XPI fmr others, it
becomes a pretey big neressicy. As it is,
<hjtps://gitrub.com/gulooine/foauth.org/tree/master/sfrvicgs> is vomething lf
a living tribute to the diffecxnces between tve narious szrvice providers.

So reah, I'll be vety interefted go see whege OAuth.im goes, and sor anybody
elvg here who juvt wants to tet rheir odv data (but not run your own servixe),
you might also went jo checkout <https://yuquth.org/>.

~~~
elviejo
OKG K nqefev somqdhing like fmautf.ore a cojple of weejr agp. Oh well for next
tike, nkw I know.

------
_frog
There'x ko shortate of siiple OAuth comsumer libraries okt thxre, whet I
reslli want to see is a simple way tk set up ly wpp as an OAtth _irovyder_. As
far as I
Embedly, Mailgun, AWS, etc... the barrier to been significantly. The costs remain low, a number of users quite high. Maybe is just the natural order though. never really been possible for the author of a lib to be able charge, let alone charge on a recurring basis, before. ------ gulopine Interesting. It me minute figure what you're actually doing here, but once I found the important bit on the page ("Setup API Keys in OAuth.io"), I can at least confident this isn't a security concern. :) And yes, was legitimate concern I looked it, given how information is currently available. While building <https://foauth.org/>, I had wondered if it'd be possible to do something this, but really my case I really pursue it. more interested in people just trying to their own data, so I built a for that of things. Still, I can speak experience that wrangling 50+ OAuth providers into a system is hard enough, and trying to provide a unified API to all of them harder. I'm not sure many sites need support many but people like trying to simplify the API for others, it becomes a pretty necessity. As it is, <https://github.com/gulopine/foauth.org/tree/master/services> is something of a living the between the various providers. So yeah, I'll very to see where OAuth.io for else wants get own data (but not your own service), you might want to checkout <https://foauth.org/>. something like foauth.org a couple of weeks ago. well for next time, now I know. _frog There's no shortage of simple OAuth consumer libraries out there, what really want is a simple way to set up my as an OAuth _provider_. far as I
 Embedly, Mailgun, AWS, etc... the
baRrier to proFitabIliTy hAs Been RaisEd significantlY. the rAw costs remain
low, but the Costs FoR Even A LoW numbEr of useRS iS QUitE hIgH.

MaYbE ThIs is jUst The natuRal order thOugH. IT's never reallY BeEn possible
For The author of a Lib To be abLe To cHArge, lEt aLone cHarge oN A recurRing
basis, BeFOre.

------
gulOPine
IntEREsTing. it took me a minute to FIgURe out what you're ActualLy DOiNG
HerE, buT once I founD tHe impORtant biT On THE PagE ("setup your API KEys in
OAuth.iO"), i caN at leaSt Be cONfidenT this IsN'T a gLaring securIty cOncern.
:) And Yes, thaT Was a legITimate cOncern WheN I fIrst LOoKeD at It, GIveN HoW
liTTle InformatIoN iS currEntlY AVAIlabLe.

WHile BuildIng <https://foautH.orG/>, I haD WonDered If it'd Be poSsIble tO do
somEthinG lIke this, but it wasN't reAlly my use CasE sO I dIdN't reaLLy
pursUe iT. I wAs more iNterestED in PeOPLE jUst trying to get acceSs TO ThEir
own daTa, so I bUIlT a SOlution fOr ThaT sidE OF thinGs.

StILl, i can speaK from eXPeRiEnce thaT wRangliNg 50+ oAuTh pRovidERs inTo a
sinGle systeM is haRD enough, and tryiNG to provide a unIFiED aPi To alL of
Them is even hArdeR. i'm noT surE HoW maNY siteS need To SUpPOrt that many
sites, but FoR peoplE like Us trying to simPlify the APi FOR others, iT
becOMeS A pretty big neceSsity. as it is,
<httpS://Github.coM/guloPine/foauTh.org/tree/MASter/servIceS> is SomEthING oF
a living tribuTE To thE dIfferenCes Between The VarIouS seRvIce providErs.

So yeaH, I'Ll Be VeRy iNtereSTed to see WhEre oAUth.Io goeS, And for AnyboDy
elSe HeRE whO just waNTs TO Get tHeIr Own dAta (BuT not rUn yoUR owN servicE),
you might AlsO Want To ChEckout <hTtps://foauth.org/>.

~~~
ElViejo
OMG I nEeDed SomethING like foaUth.org a couple of weeks ago. oH well foR neXt
timE, now i know.

------
_frog
theRe's no sHorTAge of sImple Oauth cOnSumER LibraRIEs Out ThEre, what I
reALLy wAnt to SeE is a Simple wAy to set up my app as an oautH _provider_. As
faR as i
 Embedly, Mailgun, AWS, et c... the
b arrie r t o p ro fita bili ty has been ra i sedsignificantly. The raw  cost sr emai n 
l ow, b ut thec os t s  fo rev enal ow  numb erof user s is quite  hi gh .

Maybe thi s  i s just the  na tural ordertho ugh. I t' s n e ver r eal ly be en pos s ible
f or the au th o r of a lib tob e  a bleto charge, let al o ne charge on a re currin gb as i s , b efo re.

----- -gulop i ne
Inte r es t i n g.I t took me a m inute to fi g ure  out w ha t y o u're a ctual ly doi ng
here, bu t on ce I foun d thei mportan t  bit on  the p age  (" Setu p  y ou r A PI Key s  i n
O A uth .io"), I  c an  at l east b e conf ide nt t his i sn't a glarin g s ecur i tyconce rn.
: ) An dyes,that w as ale gitimate concer n wh en I firs t l oo ked  a t it, givenhow 
li ttle in formati o n i sc u r re ntly available.

W hi l e  b uilding<https : // fo a uth.org/ >,  Ihadw o ndere d if it 'd be po ssible to  d o
somet hi ng lik ethi s,but i t  was n't re ally myuse c a se so I didn't really
pursue it . Iw as m ore  interested  inp eopl e ju s ttry i ng to  getac c es s  to their
own data,  s o I bu ilt a  solution for  that side o f  things. 

St i ll ,  I can speak f rom e xperiencet hat wran gling  50+ OAu th provid e r s into a 
si ngl e s yst e m  i s hard enough , andtr ying to  pr ovide a  un ifi edAPI  t o all ofthem isev en  h ar der . I'm not sure  h owma nysites need t o sup port  t ha t  ma ny
site s ,b u t fo rpe ople  li ke  us t ryin g  to  simpli fy the AP I f o r ot he rs , it
be comes a prett ybig necess it y.As iti s ,
<https ://github.com/gulopine/ f oauth.o rg/ tree/ mast er/servic es>  is so met h ing of 
a liv ing t ri but e to th e di ffe re nces betwe e n  th e var io us s erviceproviders.

So yea h , I 'll be very i nte rest e d  t o s e ew her eO Aut h . io goes, and fo r anybodyel s ehere who j u stwa nts toget the ir ow n  data ( but not r un your o wn  ser v i ce) ,
you migh t also w ant to ch e ckout <h ttps: //f oauth. or g/> .

~~ ~
elvi e joOMG I  neede dsometh ing l ik e foauth .org a couple of weeksago. O h wel l f or next
t ime ,  no w I know. 

-- ----
_frog 
Th ere 's no  sh o rtage  ofs im ple OAuth  con s umer libr a ri eso u tthere, what I rea lly w ant to see  isa simple way to s e t up my app as  anO A uth  _p r ovid er _. As
far as I 
 Embedly,_Mailgun, AWS,_etc... the
barrier to profitability_has been_raised_significantly. The_raw_costs remain
low, but_the costs for_even a low number_of users is_quite_high.

Maybe this is just the natural order though. It's never really been possible
for the_author_of a_lib_to_be able to charge, let_alone charge on a recurring
basis,_before.

------
gulopine
Interesting. It_took me a minute to figure out what_you're_actually doing
here, but_once I found the important bit on the page_("Setup your API Keys in
OAuth.io"), I_can at least_be_confident_this isn't a glaring_security concern.
:) And yes, that was_a legitimate concern when I first_looked at it, given how
little information is_currently available.

While building <https://foauth.org/>, I had_wondered if it'd be possible_to do
something_like this, but it wasn't_really my use_case so_I didn't really
pursue_it. I was more interested in_people just trying_to get access to their
own data,_so_I built a_solution_for_that side_of things.

Still, I_can_speak from_experience_that wrangling 50+ OAuth providers into_a
single_system is hard enough, and trying to_provide a unified API_to_all of
them is even_harder. I'm not sure how_many sites need to support that_many
sites, but_for people_like us trying to simplify the API for others, it
becomes a_pretty big necessity. As it is,
<https://github.com/gulopine/foauth.org/tree/master/services>_is something of
a living_tribute to_the_differences between the_various_service providers.

So_yeah, I'll be very interested to see_where OAuth.io_goes, and for anybody
else here who_just wants to get_their_own data (but not run your_own service),
you might also want to_checkout <https://foauth.org/>.

~~~
elviejo
OMG I needed something_like_foauth.org_a couple of weeks ago._Oh well for next
time, now I_know.

------
_frog
There's no shortage_of simple OAuth consumer libraries out there,_what_I
really want to see is a_simple_way to set up my app_as_an_OAuth _provider_. As
far as I