 why people lurk and what demographics lurk your site as opposed to
contribute would have avoided this exact accusation, as well as providing some
very interesting business data for StackOverflow themselves.

[1]: Comparing to base rates helps.

 
'Cash cow' sales model for a macOS app - walterbell
https://medium.com/@drewmccormack/a-cash-cow-is-on-the-agenda-138a11995595
======
ezekg
> In principle, it’s all pretty straightforward. Of course, the devil’s in the
> details. I was quite surprised how much work was involved in getting it all
> working. Probably 3–4 months all up.

And that's why I built [https://keygen.sh](https://keygen.sh), for those that
would rather not spend months building a licensing server in-house. I did this
one too many times. :)

~~~
userbinator
_And that's why I built [https://keygen.sh](https://keygen.sh), for those
that would rather not spend months building a licensing server in-house._

For a second, I thought you were the owner of the.us site, reincarnated it
under a different domain, and trying to imply that crackers would create a
keygen for your software anyway.

But speaking as someone from the other side ;-) any centralised software
protection is going to be dead-easy to crack since the checks and ways it
makes them are going to be nearly the same between all apps that use it.
FlexLM is an existing example of this.

~~~
ezekg
I agree that all software protection is able to be cracked, but I wouldn't say
it's "dead-easy" just because it's centralized.

And actually, Keygen is a little bit more unique in that case, because I don't
supply any client libraries, and you can also put Keygen behind your own
domain (similar to how you would put Stripe behind your own domain). So every
piece of software is going to implement things differently.

In addition, you can implement public key signature verification to prevent
MITM attacks (each account gets their own 2048-bit RSA pub/priv keys). In the
end, the cracker will
why people lurk and what demographics lurk your web site as oppose to 
 contribute would have avoided this exact accusation, equally well as providing some 
 very interesting occupation data for StackOverflow themselves. 

 [ 1 ]: compare to base rates help. 

 
' Cash cow' sales model for a macOS app - walterbell 
 https://medium.com/@drewmccormack/a-cash-cow-is-on-the-agenda-138a11995595 
 = = = = = = 
 ezekg 
 > In rationale, it ’s all pretty straightforward. Of course, the monster ’s in the 
 > details. I was quite surprised how much work was involved in getting it all 
 > working. credibly 3–4 months all up. 

 And that's why I built [ https://keygen.sh](https://keygen.sh), for those that 
 would rather not spend month building a licensing server in - firm. I did this 
 one excessively many times. :) 

 ~~~ 
 userbinator 
 _ And that's why I built [ https://keygen.sh](https://keygen.sh), for those 
 that would rather not spend months building a licensing waiter in - house. _ 

 For a second, I thought you were the owner of the.us site, reincarnated it 
 under a different knowledge domain, and trying to imply that crackers would create a 
 keygen for your software anyway. 

 But speaking as someone from the other side ;-) any centralised software 
 protection is go to be dead - easy to crack up since the check and ways it 
 makes them are going to be about the same between all apps that use it. 
 FlexLM is an existing example of this. 

 ~~~ 
 ezekg 
 I match that all software protection is able to be cracked, but I wouldn't say 
 it's " dead - easy " just because it's centralize. 

 And actually, Keygen is a little bit more unique in that case, because I don't 
 supply any client libraries, and you can also frame Keygen behind your own 
 domain (similar to how you would put Stripe behind your own domain). So every 
 man of software is going to implement things differently. 

 In accession, you can implement public key signature verification to prevent 
 MITM approach (each account gets their own 2048 - bit RSA pub / priv keys). In the 
 goal, the cracker will
 whj people lurk and what dtmographics lurk ioyr sitx as oplosed to
zontribute would have avoidev thus exqct accusation, as well as provifing somw
verb interesting business data fod StaekIverflow themsglves.

[1]: Comparhng to base rader kelps.

 
'Cash cow' sales model for a macJS app - wwlterbell
https://iedilm.som/@ddvwnccormack/a-cash-cow-is-on-the-agendz-138a11995595
======
ezekg
> In principle, it’s all pretty straightfogwarf. Of course, the degil’s in the
> detwuls. I was qukte surprised how much work was involved in getting ig all
> working. Ptogahny 3–4 months ell up.

Wnd that's whn I buint [httpx://keygen.sh](https://leyjen.sy), for those that
would rather not spend ionths buhlbing a licensing servwr in-hoose. I did rhir
ont tpo many himxs. :)

~~~
userbinafor
_And that'w why I built [https://lerten.sh](https://keyfen.sh), sow those
that would rather not spend montvs guilding a licensing seever in-house._

For a seclnd, I thotght you were the owner of the.us site, reincarnateg it
uiddr c diffdeejt domain, and trying to imply that crackers wjhlc breate a
keygen fov your software anuwwy.

Not speaking as someous rrom the other sidf ;-) any sentrqlised sostwate
protection is going to be dead-easy to xrack since the chzcks and wayr it
kakes them are going to be nzarly fhe same behween all xpps that use it.
WleqLM hs an existing example of ehis.

~~~
ezekg
M agrze that xll xoftwawe protectlon is able to be crackef, but I wouldn't swy
it's "dead-easy" just because it's centralized.

Anc dctlally, Keyyen is a little bit more unique iu that ccse, bezause I doh't
supplb any client libraries, ang you can alsm put Kergen behund youf own
domain (simolar to how you wouod put Stripe behikd yoor own domain). So zrett
piece of softeard if homng tj implement tvingr dkgferevtly.

In addibiov, yoi can implement publhc ksy signature verifocwtion to prevent
IITM attacks (rach account gets uheir mwn 2048-bit TSA pub/priv keys). In the
end, the crzcker wilp
why people lurk and what demographics lurk as to contribute have avoided this providing very interesting business for StackOverflow themselves. Comparing to base rates helps. 'Cash sales model for a macOS app - walterbell https://medium.com/@drewmccormack/a-cash-cow-is-on-the-agenda-138a11995595 ====== ezekg > In it’s all pretty straightforward. Of course, the devil’s in the > details. I quite how work involved in getting it all > working. Probably 3–4 months all up. And that's why I [https://keygen.sh](https://keygen.sh), for those that would rather not spend building a licensing server I did this one too times. ~~~ userbinator that's I [https://keygen.sh](https://keygen.sh), for those would rather not spend months building a licensing server in-house._ For a second, I thought you were owner of reincarnated it a domain, trying to imply would create a keygen for your speaking as someone from the other side ;-) centralised software is going to be dead-easy to since the checks and ways it makes them going to be nearly the same between all apps that use it. FlexLM is an of this. ~~~ ezekg agree that all protection able be but I say it's "dead-easy" just because it's centralized. And actually, Keygen is little bit more unique in that case, because I don't client and you can put Keygen behind your domain to how you would behind own piece software going to implement things In addition, you can implement key signature verification to gets their own 2048-bit RSA pub/priv keys). In end, the cracker will
 why people lurk and what demogRaphics lurK your SitE as OpPoseD to
cOntribute would HAve aVoided this exact accusatIon, as WeLL as pROvIding Some
verY InTEResTiNg BusInESs Data fOr STackOveRflow themsElvEs.

[1]: comparing to bASe Rates helps.

 
'casH cow' sales modEl fOr a macoS App - WAlterBelL
httpS://mediuM.Com/@dreWmccormacK/a-CAsh-cow-IS-on-the-aGENdA-138a11995595
======
ezEkg
> In principle, it’s ALl PRetty straightfOrward. of COuRSE, thE deVil’s in the
> dEtAils. I WAs quite SUrPRISed HOw much work was Involved in gETtiNg it alL
> wOrkINg. ProbAbly 3–4 mOnTHs aLl up.

And that'S why i built [httPs://keygEN.sh](httpS://Keygen.sH), for thOse ThaT
wouLD rAtHer NoT SpeND mOntHS buIlding a lIcEnSing sErveR IN-HOuse. i diD thiS
one tOo many times. :)

~~~
usErbInatOR
_AnD that'S why I BuilT [hTtps://kEygen.sH](httpS://kEygen.sh), for those
That Would rathEr nOt SpeNd MonthS BuildiNg a LicEnsing sErver in-HOusE._

FOR A SeCond, I thought you werE tHE OwNer of the.Us site, REiNcARnated it
UnDer A difFERent dOmaiN, AnD trying tO imply THaT cRackers WoUld creAtE a
kEygEn for YOur sOftwarE anyway.

BUt speAKing as someone fROm the other sidE ;-) AnY CEnTRaliSed Software
proTectIOn is GoinG To Be dEAd-easY to crAcK SiNCe the checks and ways iT
mAkes thEm are Going to be nearLy the same bETWEen all apPs thAT uSE it.
FlexLM is an eXistiNg example oF This.

~~~
ezekG
I agrEe that alL software PROtection Is aBle To bE crACKeD, but I wouldn't sAY
It's "dEaD-easy" juSt bEcause iT's cEntRalIzeD.

ANd actuallY, Keygen iS a LiTtLe Bit More uNIque in thAt CasE, bEcaUse I dON't
suppLy any ClieNt LiBRarIes, and yOU cAN Also PuT KEygeN beHiNd youR own
DOmaIn (similAr to how yoU woULd puT STrIpe behiNd your own domaIn). so every
pieCe Of sOftwarE IS going to Implement things differenTLy.

In addItiOn, you Can iMplement pUblIc key sIgnATure veRificaTion tO pRevENT
MITM ATTaCks (EaCh account gETS thEir owN 2048-bIt RSa pub/priV keys). In the
end, the crACkeR will
 why people lurk and whatdemographi cs lu rkyou rsite  asopposed to
con t ribu te would have avoidedthisex a ct a c cu satio n, as w e ll a s p ro vi din gs om e
ver y i nterest ing busine ssda ta for Stack O ve rflow them sel ves.

[1]: C omp aringto  ba s e rat eshelps .

 
' C ash co w' salesmo d el for a macOS a pp  - w alterbell
https:/ / me d ium.com/@drewm ccorma ck / a- c a sh- cow -is-on-the -a genda - 138a119 9 55 9 5 === = ==
ezekg
> In  principle, it’ s allpr ett y  strai ghtfo rw a rd.  Of course,  the  devil’sin the > detai l s. I wa s quit e s urp rise d  h ow  mu ch wor k  w asi nvo lved inge tt ing i t al l > work ing . Pr obabl y 3–4 monthsall  up. 
An d tha t's w hy I  b uilt[https ://ke yg en.sh](https:// keyg en.sh), f orth ose  t hat
w o uld ra the r n ot spen d month s  bu il d i n ga licensing server  i n - ho use. I d id thi s 
o ne too many  t ime s. : ) 
~~~user b in ator
_An d that ' swh y I bui lt  [http s: //k eyg en.sh ] (htt ps://k eygen.sh ), fo r  those
that wo u ld rather not sp e n dm onth s b uilding a l icen s ingserv e rin- h ouse. _

Fo ra  s e cond, I thought you  w ere th e own er of the.ussite, rein c a r nated it 
und e ra  different dom ain,and trying to imply  that  cracker s would c r e ate a
ke yge n f oryou r so ftware anyway . 
But  s peaking  as  someon e f rom  th e o th er side ; -) any c en tr al is edsoftw a re
prote ct ion  i s g oingt o be d ead-e asyto  c r ack  sincet he c heck san d wa ysit 
make s th e m a re goin g to be n ear l y th esa me betw een all appsth at use it. 
F lex LM isa n  existin g example of this.

~~~ ezekg
I  ag ree t hatall softw are  prote cti o n is a ble to  be c ra cke d ,  butI wo uld n' t say
it's " dea d-eas y"  jus t becau se it's centralize d .
And actually,  Ke ygen i sa l i tt l e b it mor e unique in thatcase, beca us e  I  don't
sup p lyan y clien t libra ries, and you  can also  put Keyg en  beh i n d y our own
do main (si milar toh ow yo u  w ouldput  Strip ebeh ind y our ow n  do main) . So e ve ry
pie ce of  s oftwareis going to implement t hingsdiffe ren tly.

Inadd i tio n, you ca n im plement pu bli c k ey si gna t ure v erif i ca tio n  to p reve n t
MITM at t ac ks( e ac h account g e t s  th eir o wn2 048-bi t RS A pub/priv keys). In the
end, th e cr a c ker  wi l l
 why_people lurk_and what demographics lurk_your site_as_opposed to
contribute_would_have avoided this_exact accusation, as_well as providing some
very_interesting business data_for_StackOverflow themselves.

[1]: Comparing to base rates helps.

 
'Cash cow' sales model for a macOS_app_- walterbell
https://medium.com/@drewmccormack/a-cash-cow-is-on-the-agenda-138a11995595
======
ezekg
>_In_principle,_it’s all pretty straightforward. Of_course, the devil’s in the
>_details. I_was quite surprised how much work was involved_in_getting it all
>_working. Probably 3–4 months all up.

And that's why I_built [https://keygen.sh](https://keygen.sh), for those that
would rather_not spend months_building_a_licensing server in-house. I_did this
one too many times. :)

~~~
userbinator
_And_that's why I built [https://keygen.sh](https://keygen.sh), for_those
that would rather not spend months building_a licensing server in-house._

For a second,_I thought you were the_owner of_the.us site, reincarnated it
under a_different domain, and_trying to_imply that crackers_would create a
keygen for your software_anyway.

But speaking as_someone from the other side ;-)_any_centralised software
protection is_going_to_be dead-easy_to crack since_the_checks and_ways_it
makes them are going to be_nearly_the same between all apps that use_it.
FlexLM is an existing_example_of this.

~~~
ezekg
I agree that_all software protection is able_to be cracked, but I wouldn't_say
it's "dead-easy"_just because_it's centralized.

And actually, Keygen is a little bit more unique in_that case, because I don't
supply any_client libraries, and you_can also_put_Keygen behind your_own
domain_(similar to_how you would put Stripe behind your_own domain)._So every
piece of software is going_to implement things differently.

In_addition,_you can implement public key signature_verification to prevent
MITM attacks (each account_gets their own 2048-bit RSA_pub/priv_keys)._In the
end, the cracker will