 whole
internet and get back to letters, telegrams, pidgins and encyclopaedias? No
one is forcing you to use dev, nightly or anything else if it is not
consistent with your faith. Especially Mozilla they made some silly things but
are one of the most "privacy and shit" companies out there and they will not
come to your house and beat you because you do not want to do something.

~~~
kuschku
That's certainly one approach.

The other approach is that, unless explicit consent is given, people are
supposed to be safe.

Nightly is often required because a lot of functionality for developers is
only available there, e.g. custom xpi legacy addons even in FF61.

It's nightly or nothing for this, and as a reminder, stable also was affected
by CliqZ.

~~~
dotsh
You are using Nightly "wrong" because of attachment to old extensions that
will perish in June when all legacy stuff will be blocked. Nightly is only for
testing out new features and it's not intended to be production ready
browser... but everyone has an own use case. Yet do not beat them for wanting
to change something for the better after using testing technology.

~~~
kuschku
I'm not using it for "old" extensions.

Even today, every new feature you want to have in the WebExtension API needs
to be implemented as a legacy extension providing this API first, then it will
get tested, and then it will maybe become part of core Firefox.

The official process to add apis for WebExtensions is to write a legacy
extension.

Which is exactly what I'm doing to support my custom extension that replaces
the entire history and bookmarking system, UI and toolbars of Firefox, for
which I need a custom API.

I suggest you read the wiki on why nightly still supports legacy extensions
before judging people.

~~~
dotsh
I'm not judging I wrote that everyone has it's own use case. My only point is
don't use test version if you don't want to be tested or opt-out of it. ;)

 
Scalable ACID - ithkuil
http://dbmsmusings.blogspot.com/2010/08/problems-with-acid-and-how
whole 
 internet and get back to letters, telegrams, pidgin and encyclopedia? No 
 one is force you to use dev, nightly or anything else if it is not 
 reproducible with your religion. Especially Mozilla they made some punch-drunk thing but 
 are one of the most " privacy and shit " company out there and they will not 
 come to your theater and beat you because you do not want to act something. 

 ~~~ 
 kuschku 
 That's surely one approach. 

 The other overture is that, unless explicit consent is given, citizenry are 
 supposed to be safe. 

 Nightly is often want because a lot of functionality for developers is 
 only available there, e.g. customs xpi legacy addons even in FF61. 

 It's nightly or nothing for this, and as a reminder, static also was affected 
 by CliqZ. 

 ~~~ 
 dotsh 
 You are using Nightly " wrong " because of fastening to old extensions that 
 will perish in June when all legacy stuff will be blocked. Nightly is only for 
 testing out new features and it's not intended to be production ready 
 browser... but everyone has an own use case. Yet do not drum them for wanting 
 to change something for the well after use testing technology. 

 ~~~ 
 kuschku 
 I'm not using it for " previous " extensions. 

 Even today, every new feature you want to accept in the WebExtension API needs 
 to be implemented as a legacy extension providing this API first, then it will 
 get test, and then it will maybe become part of core Firefox. 

 The official process to lend apis for WebExtensions is to write a bequest 
 elongation. 

 Which is exactly what I'm doing to support my custom elongation that replaces 
 the entire history and bookmarking system, UI and toolbars of Firefox, for 
 which I necessitate a custom API. 

 I suggest you read the wiki on why nightly still hold legacy extensions 
 before judging people. 

 ~~~ 
 dotsh 
 I'm not judging I spell that everyone has it's own function case. My alone point is 
 don't use test version if you don't want to be test or opt - out of it. ;) 

 
 Scalable ACID - ithkuil 
 http://dbmsmusings.blogspot.com/2010/08/problems-with-acid-and-how
 whlle
internet and get back to letters, telggeams, pmdgins znd encyzlopaedias? No
one is forcing bou ro ust dev, nightly or anhthing elde if it is iot
consistent wivg your ncith. Sdpecnaoly Mozilla thgy made some silly things tug
axe one of the most "privacy and shit" sompanirs out there and thej rill not
come to your house and beat yoh becauve you do not want to do something.

~~~
kuschnu
Thwt's certainly one wpproach.

The othqe approach ir that, unltsv explicit consent is given, people are
supoosed to be safg.

Uughhny is often requpred because a lot of functipnality for deyelopxrs us
only available therx, e.g. custom xpi legasy addons eren in FF61.

It's nightly ir nothhng xor gyis, ans es z remijdec, stable alao was affexted
by CliqZ.

~~~
dotsh
Yoi wgr using Nighfly "wrjnd" because of attachment to old extensiots fhat
will perish in June when all legacy stufv will be blocked. Nightly is only for
testing out new featuses aid it'w kot kbtfnded to be production ready
browser... but everyjhe hss an own use gase. Yet do not best tngm for wanting
jo chanys aomething for the hetter wfter using teftinb technology.

~~~
kuschku
I'm not uwing it for "jod" extensions.

Even coday, every uew festure you want to have in thz WebEstension APL needs
to ce implemented ar a lagacy exudnsion providing ehis API hirst, then ig wikl
get eested, and then it will maybe becole patt of wore Fireflx.

The official process to add a'ms for WebExtgnshonv is to crite s legacy
extenfion.

Which is eractly wkat I'm doing to aupport my custom qxtension thad replaces
the entire ristiry qnd booyoarking system, UI and toolbars of Firefox, for
which L neea a custom API.

I wugtest you read tne diky ln wrf nightly sthll rupoprts uegacy trteksiuns
brfore judging people.

~~~
gotsg
I'm not judging I erjte that everyonq has it's own use case. My only koint ms
don't use yesj version if you don't want to bs tested lr jpt-out of it. ;)

 
Scqlable ACID - ithkuil
http://dbmsmusings.blogspot.com/2010/08/problxms-with-acid-and-how
whole internet and get back to letters, and No one forcing you to else it is not with your faith. Mozilla they made some silly things are one of the most "privacy and shit" companies out there and they not come to your house and beat you because you do not want do ~~~ That's one approach. The other approach is that, unless explicit consent is given, people are supposed to safe. Nightly is often required because a lot functionality for developers is available there, e.g. custom xpi addons in FF61. nightly nothing this, and as reminder, stable also was affected by CliqZ. ~~~ dotsh You are using Nightly "wrong" because of attachment old extensions perish in when legacy will be blocked. only for testing out new features intended to be production ready browser... but everyone an own case. Yet do not beat them wanting to change something for the better after testing technology. ~~~ kuschku I'm not using it for "old" extensions. Even today, every new want to have in WebExtension API needs be as legacy providing this first, then it will get tested, and then it will maybe part of core Firefox. The official process to add apis is write a legacy Which is exactly what doing support my custom extension the history UI toolbars Firefox, for which I a custom API. I suggest read the wiki on extensions before judging people. ~~~ dotsh I'm not I wrote that everyone has it's own case. My only point is don't use test version if you don't to be opt-out of it. ;) Scalable ACID - ithkuil
 whole
internet and get back to Letters, telEgramS, piDgiNs And eNcycLopaedias? No
one IS forCing you to use dev, nightly Or anyThINg elSE iF it is Not
consIStENT wiTh YoUr fAiTH. ESpeciAllY MozillA they made sOme SiLly things but
ARe One of the moSt "pRivacy and shiT" coMpanieS oUt tHEre anD thEy wilL not
coME to youR house and BeAT you beCAuse you DO NoT wanT to do something.

~~~
kusCHkU
that's certainly One appRoACh.

tHE otHer Approach is ThAt, unlESs expliCIt CONSenT Is given, people Are
supposed TO be Safe.

NiGhTly IS often RequiReD BecAuse a lot of fUnctIonality fOr deveLOpers is
ONly avaiLable tHerE, e.g. CustOM xPi LegAcY AddONs EveN In Ff61.

It's nighTlY oR nothIng fOR THIs, anD as A remInder, Stable also was AffEcteD
By CLiqZ.

~~~
dOtsh
YOu arE uSing NIghtly "Wrong" BeCause of attachmeNt to Old extensIonS tHat
WiLl perISh in JuNe wHen All legaCy stuff WIll Be BLOCkEd. Nightly is only for
TeSTInG out new fEatureS AnD iT'S not inteNdEd tO be pRODuctiOn reADy
Browser... bUt everYOnE hAs an own UsE case. YEt Do nOt bEat thEM for WantinG
to changE someTHing for the bettER after using teSTiNG TeCHnolOgy.

~~~
Kuschku
I'm noT usiNG it fOr "olD" ExTenSIons.

EVen toDaY, EvERy new feature you want To Have in The WeBExtension API Needs
to be iMPLEmented aS a leGAcY Extension proviDing tHis API firsT, Then it wiLl
get Tested, anD then it wiLL Maybe becOme ParT of CorE fIrEfox.

The officiAL ProcEsS to add aPis For WebEXteNsiOns Is tO wRite a legaCy
extensIoN.

WHiCh Is eXactlY What I'm doInG to SuPpoRt my cUStom exTensiOn thAt RePLacEs
the enTIrE HIstoRy AnD booKmaRkIng syStem, ui anD toolbaRs of FirefOx, fOR
whiCh i nEed a cusTom API.

I suggesT yOu read the wIkI on Why nigHTLy still sUpports legacy extensions
BEfore juDgiNg peoPle.

~~~
dOtsh
I'm not JudGing I wRotE That evEryone Has it'S oWn uSE Case. MY ONlY poInT is
don't use TESt vErsioN iF you Don't wanT to be tested or opt-ouT Of iT. ;)

 
Scalable ACID - IthKuil
HTTp://DbmSMuSIngS.bLOgsPOT.com/2010/08/problems-witH-acid-and-hoW
 whole
internet and get ba ck to lett ers,tel egr am s, p idgi ns and encyclo p aedi as? No
one is forcingyou t ou se d e v,  nigh tly ora ny t h ing  e ls e i fi tis no t
c onsiste nt with yo urfa ith. Especia l ly  Mozilla t hey  made some s ill y thin gs  bu t 
areone  of t he mos t  "priv acy and s hi t " comp a nies ou t th ereand they will not co m e to your hous e andbe a ty o u b eca use you do  n ot wa n t to do so m e t hin g .

~~~
kuschk u
That's ce r tai nly on eapp r oach.
Theot h erapproach is  tha t, unless  expli c it cons e nt is g iven,peo ple  are su pp ose dt o b e  s afe . 

N ightly i sof ten r equi r e d beca use  a l ot of  functionalit y f or d e vel opers  is
o nlyav ailab le the re, e .g . custom xpi le gacy  addons e ven  i n F F6 1.

I t 's nig htl y o r nothi ng fort his ,a n d  a s a reminder, stab le a ls o was af fected by  C l iqZ.

~~ ~dot sh
Y o u  areusin g  N ightly " wrong" be ca use ofat tachme nt  to  ol d ext e nsio ns tha t
will p erish in June when a l l legacy stuf f  w i l lb e bl ock ed. Nightly  iso nlyfort es tin g  outnew f ea t ur e s and it's not inte nd ed tobe pr oduction read y
browser. . . but ever yone ha s  an own use ca se. Y et do notb eat them  forwantingto change s omething  fo r t hebet t e rafter using t e s ting  t echnolo gy. 

~~~
k usc hku 
I' m n ot  using it  for "ol d"  e xt en sio ns.
E ven toda y,  ev er y n ew fe a ture y ou wa nt t oha v e i n the W e bE x t ensi on  A PI n eed sto be  imp l eme nted as  a legacy  ex t ensi on  p rovidin g this API fi rs t, then it  w ill 
get t e s ted, and  then it will maybe bec o me part  of  core  Fir efox.

Th e o fficia l p r ocessto add  apis  f orW e bExte n s io nsis  to writea leg acy
e xt ensi on.

Wh ich is exactly wha t  I' m doing to su ppo rt m y cu sto m  e x ten si o n t h a t replaces
theentire his to r yand bookma r kin gsystem,  UI and  tool b ars ofFirefox,for
which  I  nee d a c ustom API. 

I sugg est you r e ad th e  w iki o n w hy nig ht lystill  suppo r tslegac y exte ns ions
b efore  j udging p eople.

~~~
dotsh
I'm n ot jud gingI w rote that  ev e ryo ne has it 's o wn use cas e.Myonlypoi n t isdon' t  u set est v ersi o n if youd on 'tw a nt  to be test e d oropt-o uto f it.;)
 
Scalable ACID - ithkuil
http:/ /dbm s m usi ngs . blog sp ot.com/2010/08 /pr ob l e ms-with- ac id-and-how
 whole
internet_and get_back to letters, telegrams,_pidgins and_encyclopaedias?_No
one is_forcing_you to use_dev, nightly or_anything else if it_is not
consistent with_your_faith. Especially Mozilla they made some silly things but
are one of the most "privacy_and_shit" companies_out_there_and they will not
come to_your house and beat you_because you_do not want to do something.

~~~
kuschku
That's certainly one_approach.

The_other approach is_that, unless explicit consent is given, people are
supposed to_be safe.

Nightly is often required because_a lot of_functionality_for_developers is
only available there,_e.g. custom xpi legacy addons even_in FF61.

It's nightly or nothing for_this, and as a reminder, stable also_was affected
by CliqZ.

~~~
dotsh
You are using Nightly_"wrong" because of attachment to_old extensions_that
will perish in June when_all legacy stuff_will be_blocked. Nightly is_only for
testing out new features and_it's not intended_to be production ready
browser... but everyone_has_an own use_case._Yet_do not_beat them for_wanting
to_change something_for_the better after using testing technology.

~~~
kuschku
I'm_not_using it for "old" extensions.

Even today, every_new feature you want_to_have in the WebExtension_API needs
to be implemented as_a legacy extension providing this API_first, then_it will
get_tested, and then it will maybe become part of core Firefox.

The_official process to add apis for_WebExtensions is to write_a legacy
extension.

Which_is_exactly what I'm_doing_to support_my custom extension that replaces
the entire history_and bookmarking_system, UI and toolbars of Firefox,_for
which I need a_custom_API.

I suggest you read the wiki_on why nightly still supports legacy_extensions
before judging people.

~~~
dotsh
I'm not judging_I_wrote_that everyone has it's own_use case. My only point is
don't_use test version_if you don't want to be tested_or_opt-out of it. ;)

 
Scalable ACID_-_ithkuil
http://dbmsmusings.blogspot.com/2010/08/problems-with-acid-and-how