Как быстро скачать современный браузер для "свежего" Windows xp

У, первый пост на русском :-)

Тут более-или-менее копия реплая

Итак, на этом видео видно, что у автора SuperGTOR не удалось сразу скачать Google Chrome с браузером Internet Explorer 6.0, версия которая уже очень устарела (скоро 20 лет будет), и ему надо было сначала скачать обновления для операционной системы, чтоб скачать Internet Explorer 8.0, а тем уже Chrome.

Вместо Chrome возможно так быстро (без обновлений) с браузером Internet Explorer 6.0 скачать Firefox, аж с официального FTP-сайта Мозиллы, так как тот сайт доступен и без https протокола, с простым протоколом http — http://ftp.mozilla.org/pub/firefox/releases/ — и скачать версию 52.9.0esr.

Тем же методом возможно скачать на старые версии Андройда APK-пакеты браузера Firefox для Android, из папки /pub/mobile/releases/ (пакеты под именем Fennec): Firefox 31.0 последний для Android 2.2, Firefox 47.0 для Android 2.3 (Android API 9), Firefox 55.0.2 для Android 4.0 (но Firefox 31.3.0esr, если архитектура процессора ARMv6). Расширение NoScript Anywhere, скачаемый с официалного сайта NoScript, очень поможет.

52.9.0 самая последняя версия Firefox для Windows XP, и та поддерживает криптографический протокол TLS 1.2. Существует и поддержка TLS версии 1.3, но та по умолчению не вклюычена. Чтоб влкючить (а надо), тогда на странице настроек about:config у настройки security.tls.version.max ставить цифру 4 (вместо 3).

Ещё надо (т.е. очень рекомендую) скачать расширение NoScript для защиты от скриптов, тракеров, рекламы, фонтов, и подобного хлама. Для классического Firefoxa подходит и классическая версия расширения NoScript 5.1.9. Чтоб инсталлировать эту версию, надо на странице настроек about:config менять настройку xpinstall.signatures.required на false (неверен / неверный), чтоб Firefox на заблокировал бы инсталляцию расширения из-за отсутсвия цифровой сигнатуры. Вот и всё.

А оттуда с Firefox-ом возможно скачать другие браузеры: New Moon или MyPal и/или что угодно.

Отдельно, в настройках Internet Explorer надо выключить SSL 2.0, SSL 3.0, и включить TLS 1.0. Иначе все сайты с протоколом https с браузера IE совсем недостижимы.

Eesti ID-kaart ja Knoppix 7.2

Algupäraselt on blogipostitus kirjutatud käigupealt, mistõttu on seesinane küljendamata kujul. Artikkel on mõeldud kõigile, kes oskavad natuke terminali (käsurida) kasutada.

Kindlasti võis midagi kahe silma vahele jääda, kuid suures osas peaks andmed paika pidama.

Intro

Ehk kuidas saada tööle panka sisselogimiseks vajalik ID-kaardi tarkvara Knoppixi 7.2 Live-CD-le, ja millised on selleks vajalikud .deb-paketid. Kuna Knoppix on Debiani-põhine, on artiklis väljatoodud pakettide arv minimaalne ja vaid antud Knoppixi-versiooni jaoks, kuid võib kasuks tulla ka teiste Debiani- kui ka mitte-Debiani-põhiste distrodega opereerimisel.

Sissejuhatus

Niisiis tekkis mullegi lõpuks permanentne ID-kaardilugeja (OmniKey CardMan 1021) ja võib-olla ka võimalus seda kasutada, et sisse logida panka. Nimelt otsustas minu pank koodikaardi võimaluse (need, mis numbritega) ära kaotada. Ainult et mul on Windows XP, ning see pole ID-kaardi tarkvara poolt enam toetatud.

Estobuntu plaadile keevitamine ei aidanud, sest selle versioon on samuti aegunud ja uut pole välja lastud. Kui seda reklaamitakse kui eestikeelset distrot, mis "toetab ID-kaarti", peaks see pidevalt kaasaegne olema.

Estobuntu põhineb Lubuntu 14.04-l, mis lasti välja 17.04.2014. Estobuntu DVD-tõmmise juures on kuupäev 02.05.2014.

Lisaks: Estobuntu 14.04 DVD Live-versiooni puhul sai värskeima Firefoxi installimisel miskipärast mäluruum otsa, sest minu masinal on vaid 1 Gb RAM-mälu (muutmälu). Kõvakettale ma tõmmise sisu ei salvestanud, sest kõvakettal on teine opsüsteem; seetõttu läks käiku vaid Live-variant, mille puhul kasutatakse ramdisk-i.

Seevastu Knoppix Live-CD puhul mälu kohese otsasaamise kartust gigabaidise RAM-mahuga pole. Etteruttavalt võib juba nentida, et Knoppixist oli kasu.

• Knoppix Live-CD (mitte DVD!) ja värske Firefoxi käitamiseks on vaja vähemalt 1 Gb RAM-mälu.
• Estobuntu töötab rahuldavalt, kui arvutis on vähemalt 2 Gb RAM-mälu.

Kaalukausile jäigi Knoppix 7.2 Live-CD, mis on Estobuntust vanemgi, aga ka viimane Knoppixi CD-versioon (24.06.2013. väljalase). Sellel on näiteks Firefoxil põhinev Iceweasel 29.0 21.0.

Iceweasel 21.0 ei toeta TLS turvaprotokolli versiooni 1.1 (järgmist) ja uuemaid. Toetatud on ainult TLS 1.0. See tähendab seda, et arvestatav osa turvatud https: veebisaite ei ole kättesaadavad, kuna: nad kasutavad TLS 1.1 protokolli, nad kasutavad TLS 1.2 protokolli, ning vähesed juba TLS 1.3 protokolli. Google, GMail ja Blogger töötavad, samuti DuckDuckGo otsing. YouTube ei tööta.

19.11.2018. Üks hea uudis ka: Firefoxi ei pea eraldi all tõmbama, sest Iceweaseliga sai panka ilusti sisse. Allpool olev pakettide installimise kadalipp tuleb ikkagi läbida, misjärel Iceweaselis digiallkirjastamise mehhanism pangaülekane (PIN2) tegemiseks erinevalt allatõmmatud Firefoxist isegi kuidagimoodi eksisteerib, kuid ei tööta, ning ma kaldun arvama, et siin on tegemist lihtsalt vananenud lehitsejaga. Üks võimalik lahendus oleks installida Iceweaseli uuendus koos vajalike sõltuvustega ja siis võimaluse tekkides proovida, kas pangaülekande tegemine õnnestub.

Et Knoppix 7.2 on veidi üle aasta vanem kui Estobuntu, ning kuna Knoppix ei ole varustatud ID-kaardi kasutamise jaoks vajalike teekidega, tuleb Knoppixile peale panna terve posu pakette ja omakorda nendest sõltuvaid pakette. (Mitte, et Estobuntuga oleks vähem vaeva, aga Knoppix ei võta kõike mälu endale.)

• Knoppix 7.x versioonidel on probleeme Synaptics puutepatjadega, millest olen ma varem inglise keeles kirjutanud. Ajutine lahendus on kasutada välimist osutusseadet (USB-põhine hiir);
• Tähtsamad käsud Knoppix 6.x ja uuemate käitamiseks, sh. sõrmistiku keele valik ja kasutajakeskkonna välimus (samuti inglise keeles).

Paketid

Synaptic paketihaldurit ei soovita ma praegu üldse, sest pakettide vaikimisi aktiivseks seatud allikatega andmebaasi uuendamisel tuleb Firefoxi (või sellel põhineva Iceweaseli) uuendamist valides ette sisuliselt kogu opsüsteemi uuendamise protsess, sest välja vahetada tuleks liigagi suur arv pakette. Firefox koos vajalike lisadega tuleb installida eraldi, aga sellest jutu lõpupoole.

Osad tarkvarapaketid on Knoppixil juba olemas; siin artiklis tõin välja vaid puuduvad või uuendatavad.

Valikupõhimõtted

Pakettide valikul osutus määravaks versiooniühilduvus, lähtudes printsiibist, et kui süsteemis on juba vajaliku paketi ühilduv versioon olemas, siis ei pea sellele uuendust tõmbama.

Näiteks mida vanem Linuxi-distributsooni versioon, seda rohkem uuemaid ja puuduvaid pakette ja nende sõltuvusi (omakorda pakette) peab peale panema.

Sellest johtuvalt osutus valik vähemas osas Ubuntu 14.04 LTS Trusty Tahr (edaspidi Trusty) ja suuremas osas Debian 8 Jessie (25–26.04.2015) distrodele kompileeritud ühilduvatele pakettidele — põhimõttel, et mida vanemale distrole tehtud ühilduv pakett, seda vähem tuleks selle jaoks sõltuvusi tõmmata.

Kompromissi ei saanud teha konkreetselt ID-kaarti puudutavate pakettidega, nagu opensc jt., mis tähendas, et osa vajaliku versiooniga pakette on Debian 10 Buster-nimelisest kõige värskemast enam-vähem stabiilsest distro-versioonist.

Kui mõni muu ühilduv pakett oli vanemas distros olemas, langes valik selle kasuks.

Installimisjuhis ja versioonide kontrollimine

Esialgu on targem tõmmata individuaalseid pakette, jälgida nende sõltuvusi ja alles siis need vaid dpkg kaudu installida nii:

$ sudo dpkg -i paketi_failinimi_koos_versiooniga

dpkg siis vastavalt annab teada, kas install õnnestus või mitte ja mis lisapaketti täiendavalt vaja on.

Ennetavalt on võimalik kasutada dpkg-query võimalust, et teada saada, millise paketi versioon installitud on:

dpkg-query -W paketi_nimi_suurversioon

Esmapilgul vajalike teekide paketid (info sain siit) —

Tsitaat:

* openssl (1.1.0h)
* libpcsclite1 (1.8.23)
* pcsc-lite (1.8.23)
* QT (5.9.4) (Miks küll?) — See muuseas jäigi installimata.

Et hoida kokku vaba RAM-mälu, võib tarkvarapaketid tõmmata ja salvestada mitte tingimata Knoppixi Downloads või Desktop (töölaua) kataloogi, vaid kõvakettale või mälupulgale konkreetsesse kataloogi, mis tuleb ise luua.

Pakettide nimekirja loomine

Terminalis koostatud mittetäielik nimekiri tõmmatud pakettidest koos sõltuvustega, kõige varasemast kõige hilisemani:

08:51 pcsc-lite-1.8.24.tar.bz2 — Selgus, et polnud vaja
09:08 libsigsegv2_2.10-4+b1_i386.deb — Polnud ka vaja

09:14 libpcsclite1_1.8.24-1_i386.deb
09:24 dpkg_1.17.5ubuntu5.8_i386.deb
09:37 libreadline7_7.0-3_i386.deb
09:42 libtinfo5_6.0+20161126-1+deb9u2_i386.deb
09:47 libssl1.1_1.1.0f-3+deb9u2_i386.deb
09:50 opensc-pkcs11_0.19.0-1_i386.deb
14:49 libglib2.0-0_2.40.2-0ubuntu1.1_i386.deb

Kataloogis olevate failide ajaliselt sorteeritud järjekord ls käsuga:

Kui käsurea käsklus ls -l näitab nimekirja failidest ja nende atribuutidest, siis -ltr parameetrid näitavad detailset nimekirja ajalises järjekorras vanimast uuemani ("modifitseeritud" ehk salvestamise aja järgi) —

l — list — detailne nimekiri
t — time and date — kellaaeg ja kuupäev
r — reverse order — "taguridi järjestus", ehk vanima salvestusajaga fail on kõige üleval

Kuna ma aga tahtsin vaid kellaaega ja failinime, tuli käskluse väljund lasta toru abil ("piibu", i.k. pipe) läbi awk-i:

$ ls -ltr | awk '{print $8, $9}'

print käseb trükkida, ning $8 ja $9 määravad vajalike veergude numbrid. Veerude number tuleb mõistatada ls -l käsuga tehtud nimekirjast. Koma veerunumbrite parameetrite vahel on tähtis. Ilma komata võib ka, aga siis ei tule kellaaja ja failinime või muude esemete vahele tühikut.

Võib kasutada ka lihtsamat varianti

$ ls -tr

— See koostab pakettide lihtsa nimekirja ajalises järjekorras vanimast salvestatust kõige uuemani suunaga ülevalt alla.

Pakettide asukohad ja nende installimine

Tuleb tähele panna, et antud Knoppix 7.2 on 32-bitine, ning pakettide tõmbamisel tuleb valida i386 arhitektuur. Arhitektuurinimetuse puudumisel on arhitektuuri asemel kirjas all (i.k. kõik).

Vajadus on seega järgmiste pakettide järele (tabel on veel pooleli) —

	Link kirjeldusele			Link paketile
#	Pakett	Vajaminev versioon	Knoppix 7.2-s?	Paketi versoon	distro	distro ver.	Sõltuja
	libpcsclite1 1.8.24-1 — paketis olev üks või enam faile sai pakendatud xz formaadis. Sellest ka vajadus uuema dpkg versiooni järele. Jäi meelde, et see dpkg versioon pidi olema just see konkreetne ja mitte mingi muu. Võimalik, et Ubuntu või Debiani ametlikel lehtedel olevad dpkg versioonid kas (veel) ei sisaldanud xz formaadi toetust, või olid pakettide sõltuvusversioonid liiga suured.
1.	dpkg 1.17.5ubuntu5.8	1.17.5	1.16.10	1.17.5ubuntu5.8	ubuntu	trusty	libpcsclite1
2.	libpcsclite1 1.8.24-1	uusim	1.8.8-3	1.8.24-1	debian	buster
*	opensc-pkcs11 0.19.0-1	uusim	Puudub	0.19.0-1	debian	buster
#

opensc-pkcs11 paketil on omad sõltuvused:

* libglib2.0 >= 2.39.4 (Knoppix 7.2-s: libglib2.0-0:i386 2.36.3-1)
* libssl1.1 >= 1.1.0 (Knoppix: Puudub; on libssl1.0.0:i386 1.0.1e-2)

libglib2.0-0_2.40.2-0ubuntu1.1_i386.deb ubuntu trusty

4. Mingi hetk tekkis tahtmine tõmmata peale ka uusim opensc:

opensc (0.19.0-1) debian buster

Sõltuvused:
* libglib2.0-0 >= 2.16.0 — esmapilgul polnud vaja, aga siis opensclite1 (üleval) tahtis ikkagi uuemat.
* libreadline7 >= 6.0 (Knoppix: Puudub; kõige hiljutisem on libreadline6:i386 6.2+dfsg-0.1)

libreadline7_7.0-3_i386.deb debian stretch (i386)

** Omakorda sõltuvus: libtinfo6 >= 6 (Knoppix: puudub; on libtinfo5:i386 5.9-10)

** libtinfo5_6.0+20161126-1+deb9u2_i386.deb debian stretch (i386)

* libssl1.1 >= 1.1.0 (Knoppix: puudub, on libssl1.0.0 1.0.1e-2)

libssl1.1_1.1.0f-3+deb9u2_i386.deb — ilmselt stretch; i386

* opensc-pkcs11 = 0.19.0-1 (Knoppix: puudub täielikult)

opensc-pkcs11_0.19.0-1_i386.deb debian buster i386

Edasi tuli installida opensc pakett:

opensc (0.19.0-1) buster i386 (Knoppix: Puudub täielikult)

Edasi: pcsd
pcscd (1.8.24-1) buster i386 (Knoppix: puudub täielikult)

aga sellel on õige mitu sõltuvust:

* libccid >= 1.4.1~ (Knoppix 7.2-s libccid justkui eksisteerib, aga uuendust sellele on ikka vaja)

libccid (1.4.18-1) jessie i386

* libsystemd0 (215-17+deb8u7) jessie i386 (Puudub täielikult)
Sõltuvused:

** libgcrypt20 (>= 1.6.1) 1.6.3-2+deb8u5 jessie dl (Knoppix: Antud versioon puudub, on libgcrypt11 1.5.0-5 )

Sõltuvused:

*** libgpg-error0 (>= 1.14), Knoppix 7.2-s 1.10-3.1 1.17.3

debian jessie i386

* libudev1 (>= 183) (Knoppixis puudub) 215-17+deb8u7 jessie i386

Kokku on pakette umbes kuue megabaidi jagu.

Firefoxi tõmbamine ja installimine

Nagu ülevalpool mainitud, siis eraldi Firefoxi tõmbamine ei ole tingimata kohustuslik. Seda kahel põhjusel:
*Minu panka sai Iceweasel 21.0 lehitsejaga sisse logitud;
*Eraldi tõmmatud Firefox ei toeta PIN2 koodi mehhanismi üldse. Iceweaseliga oli ka võimatu PIN2 koodi kasutada, kuid peale esmaselt vajalike pakettide installimist esitatakse päring selle järele, kui katsetasin ülekande tegemist. Iceweaseli uuendamisel versioonile 38.0 erilist abi kahjuks ei olnud, kuid asja tasub veel uurida.

Mozilla "FTP"-sait sidaldaaab (jutumärkides, sest see on http) Mozilla Firefoxi ja teiste programmide kõiki versioonie. Postituse tegemise kuupäeval on uusima eestikeelse Firefoxi asukoht see:

https://ftp.mozilla.org/pub/firefox/releases/62.0.3/linux-i686/et/firefox-62.0.3.tar.bz2

Kui Firefoxi pakitud fail on näiteks Iceweasel lehitsejaga salvestatud, avada faili kataloog pcmanfm failihalduris.

* firefox-62.0.3.tar.bz2 peale saab ühe korra peale klikkida, ja siis avaneb see XArchiver programmis.
* Alternatiiv on failile parema osutinupuga vajutada ja valida Extract To... käsk, mis aktiveerib XArchiver programmi lahtipakkimise mooduli. Selles tuleb valida Firefoxi installatsiooni asukoht. Kuna tegemist on Knoppixiga, võib Firefoxi rahumeeli pakkida lahti /home/knoppix kataloogi. Seal jääb see omakorda firefox/ kataloogi.

Firefoxi saab edasi käivitada terminalist:

$ cd /home/knoppix/firefox

Minna Firefoxi lahtipakitud kataloogi

$ ./firefox -P &

* -P avab Firefoxi profiilihalduri, sest Iceweasel ja Firefox kasutavad sama profiiliarhitektuuri. Seepärast on parem Firefoxis luua uus kasutajaprofiil.
* & tõstab graafilise programmi eraldi terminaliaknast.

Kuna Firefoxi uuendatakse tihti, siis Mozilla "ftp" releases kataloogis on kõige uuem versioon, aga mitte päris alguses. Otsida tuleb 62.0.3-st edasi.

(Synapticut või muud paketihaldurit ära kasuta, sest see tõmbab kaasa liiga suure arvu muid pakette).

Alles siis tuleb Firefoxi laadida onepin moodul.

Firefoxi ingliskeelses variandis:

1. Mine seadistustesse (about:preferences) >
2. Privacy & Security (ülevaltpoolt paremalt) >
3. alaosa Certificates (lehekülje kõige all) >
4. nupp [ Security Devices...] >
5. uuel aknal vajuta [ Load... ] nupule >
6. tekkinud kastis kirjuta ülemisele reale Module Name juurde mooduli nimi (mul on lihtsalt onepin)
7. Ning siis failikorjajast leia see fail:
   
   /usr/lib/i386-linux-gnu/onepin-opensc-pkcs11.so
   
   — opensc deb-faili järgi pistab dpkg programm onepin-mooduli installimisel sinna.

Tuleb sellega siiski arvestada, et mooduli laadimise aken (kast) võib kaduda lehitseja-akna taha, kui aktiveerida samas aknas olnud muu vahekaart mõne teise leheküljega. Lahendus on siin Firefoxi aken tõsta allapoole senimaani kuni mooduli laadimise aken nähtavale tuleb.

dpkg-põhise installiprotseduuri kõige lõppeks panin peale ka esteidfirefoxplugin_3.12.2.1145beta-1404_i386.deb paketi, mille tõmbasin Ubuntu Trustyle mõeldud RIA varamust.

Kas sellest ka mingit kasu oli, ei ole selge.

esteidpks11loader paketi unustasingi peale panna, aga tuleb välja, et ülejäänust ja allolevast piisas, et sisse logida.

Selle saab kätte samuti RIA poolt Ubuntu Trustyle koostatud varamust.

Küll panin Firefoxile peale Open-eID lehitsejalisa. Kätte saab selle Firefoxis aadressilt
https://addons.mozilla.org/firefox/addon/open-eid/

Edasi tuleb Firefox sulgeda, alles siis kaart sisestada kaardilugejasse, ning lehitseja siis taaskäivitada.

Kui kaarti parasjagu enam vaja pole, siis sulgeda terve Firefox ja kaart lugejast välja võtta. Kui kaart on kaardilugejas ja lugeja indikaator vilgub, siis kaarti välja võtta ei maksa. (Kui lamp jääb pikaks ajaks vilkuma, siis tasuks proovida süsteemi kinnipanekut või restarti.)

Vähemalt eesti.ee-sse ja panka sisselogimiseks kõlbab küll, kuigi allkirjastamist pole ma proovinud (näiteks ülekande tegemiseks).

Delfi Flash-põhine video, Firefox ja privaatne lehitsemine

Niisiis tekkis hiljuti vajadus vaadata Delfis artikli juurde käivat videot, aga video kohe tööle ei läinud.

Tingimused olid järgmised:
* Inteli integreeritud videoadapteriga (videokaardiga) sülearvuti, mis ei toeta OpenGL-i seda versiooni, kus Firefoxis mängiks HTML5 video;
* Windows XP SP3;
* Mozilla Firefox 38.8 (eestikeelne);
* VLC Media Player (see osutub hiljem oluliseks);
* Flash Player, mida selle vanema versiooni tõttu automaatselt ei aktiveerita;
* Firefoxi privaatse lehitsemise režiim;
* Samuti annab Firefox veebilehtedele teada, et jälitamist ei soovita (küpsised jne.).

Video mitte-esinemisel osutusid peamisteks põhjusteks teatud Delfi jt. domeenidel pluginate ja küpsiste õigused, ehk nende puudumine.

Protsessi kirjeldus

Kuna HTML5 video mängimine ei tööta videoadapteri draiveris OpenGL 2.0 toetuse puudumisel, langeb Delfi pleier tagasi Flashile, mille põhjal hakkab tööle JWPlayer.

Firefox kuni versioonini 43.x (k.a.) toetab küpsiste salvestamise kohta küsimist, kuid see süsteem ei tööta privaatse veebilehitsemise režiimis, ning eeldatavasti ka siis, kui Firefox annab veebilehtedele teada, et jälitamist ei soovita. Viimane võib tähendada, et ei võeta vastu küpsiseid, aga selle protsessi hingeelu ma täpselt ei tunne.

Lahendus

Kuna aga videomängijat ei tulnud ette, selgus lähemal uurimisel, et Flash ja küpsised oleksid teatud domeenidel lubatud.

Muuhulgas asub Flashil põhinev JWPlayer näiteks g3.nh.ee domeenil.

Küpsiste ja pluginate õiguste muutmiseks tuleb teha järgmist:

• Mine aadressile
  
  http://g1.nh.ee/ct/ej/arrow_250.png
  
  Ette tuleb PNG-formaadis olev noolepilt, ning väljaspoolt pilti tee lehitseja (musta värvi) vaatealale paremklikk ja vali hüpikmenüüst "Vaata veebilehe teavet".
• Uues aknas "Veebilehe teave" mine vahekaardile Õigused, ning erinevate õiguste nimekirjas tee järgmised muudatused:
  
  • Sektsioonis Pluginate aktiveerimine vali raadionupp "Lubatud" igal real, kus on "VLC Web", sh. ka see VLC rida, kus võib olla kirjas "Plugin võib sisaldada turvaauku!" Seletuseks niipalju, et peale VLC installimist on Flash-plugin märgitud mingil põhjusel VLC-ks.
  • Keri nimekirjas alla, kuni jõuad eraldiseni Küpsiste salvestamine.
    Seal vali "Lubatud" või "Lubatud selleks seansiks".
  • Korda sama asja järgmistel aadressidel:
    
    • Delfi koduleht (www.delfi.ee) või vajadusel mõni muu Delfi alamleht, mille artiklis näidatakse videot, nagu näiteks Delfi Publik (publik.delfi.ee)
    • Delfit toetavad domeenid:
      
      • http://g1.nh.ee/ct/ej/arrow_250.png
      • http://g3.nh.ee/m/dd/nupp.png
    • JWPlayeri domeen:
      https://ssl.p.jwpcdn.com/6/12/logo.png
    • Video lähtedomeen aadressil eeds.babahhcdn.com või mõni muu babahhcdn.com alamdomeen:
      http://eeds.babahhcdn.com/crossdomain.xml
• Videot sisaldav artikli lehekülg tuli uuesti laadida.

Suurema osa näitefailide asukohad sain kätte klikkides näiteks Delfi artiklil "Vaata veebilehe teavet" ja siis selle akna sektsioonist "Meedia". Ülejäänud asukohad sain teada Firefoxi veebiarendaja Network tööriista ja Internetiotsinguga. (Nii või teisiti olid failide asukohtad avalikult kättesaadavad.)

Remedying high CPU usage in Firefox when visiting the Esquire site

I recently visted the Esquire site, and Firefox hung for many long minutes, with Process Explorer (a Task Manager alternative) showing very high CPU usage. To stop this, I had to end the Firefox process.

I experienced this with Firefox 38.8 and 39.0.3, both on Windows XP SP3. These two browser versions are relatively close to one another, but in different computers, which led me to conclude, that the issue is server-side.

The culprit is a possibly malformed font file with the .css extension:

assets.hearstapps.com/sites/esquire/assets/css/fonts-deferred.afa78bb.css

This is the file that you have to block.

If you use NoScript already, don't visit the Esquire site yet, and go instead to NoScript Options.
• In the Other tab, there is the ABE subtab;
• Click the USER rule/set in the left pane, and paste the following code into the right pane:

#ESQUIRE HIGH RESOURCE USAGE
Site .assets.hearstapps.com/sites/esquire/assets/css/fonts-deferred*
Deny INCLUSION(FONT,CSS)

#This is a widespread tracker or ad service of some kind.
#Used by Esquire, too.
Site .nexus.ensighten.com
Deny

Click OK.

You can now try out the Esquire website. Works for me.

05.10.2018 Update: I've shortened the Site line to end with fonts-deferred*. NoScript's ABE should still match the pattern. The reason was, that the original file was fonts-deferred.afa78bb.css, which contains alphanumeric content that may be used for version tracking server-side. Removing those numbers and including a wildcard makes the line relatively future-proof from newer versions of the same file.

Postimehe otseblogi ja NoScript

Firefoxis on NoScript laiendus kasulik selleks, et blokeerida skripte ning säästa arvutiressursse — et arvuti oleks kiirem. See sobib olukorras, kus masin pole kõige uuem, kuid ajab asja ära.

Probleem seisnes selles, et Postimehe otseblogi miskipärast ei näidanud, ehkki NoScriptis olid kõik Postimehe/PMO domeenid lubatud.

Tegemist oli konkreetselt töölaua-Firefoxiga, kuid sama asi kehtib teiste Firefoxi- ja Gecko-põhiste lehitsejatega, sh SeaMonkey, GNU IceCat, Debian Iceweasel jt.

Selgus, et otseblogi laaditav failitüüp ei olnud Firefoxile sobilik (failitüübi kontroll ei lasknud faili läbi), ning otseblogi ei laadinud enam. See paistis silma lehitsejakonsoolis (Tööriistad > Veebiarendajale > Browser Console).

Lahendus:

• Minna about:config lehele, otsida parameeter nimega
  noscript.inclusionTypeChecking.exceptions
  
• Väärtusele lisada järgmine tekstiosa koos tühikuga alguses:
  http://f.pmo.ee/s/failid/live/*.liv

Otseblogiga artikkel tuleb uuesti laadida, ning nüüd peaks otseblogi töötama.

Väike ääremärkus, et Androidi-Firefoxi ja IceCatMobile lehitsejatega, kus ka NoScript peal, selliseid probleeme pole, sest nendes on NoScripti mobiiliversioon vähemfunktsionaalne.

Lahendus oli NoScripti foorumis.

Can't see Instagram in Firefox?

Trouble was, that Instagram and embedded Instagram pictures recently stopped loading in Firefox.
This also affects other Gecko-based browsers.
> If you want to skip the story, jump to solution.

While I also use NoScript on desktop Firefox, and on Firefox for Android, all the necessary instagram domains were allowed.

On the desktop, I'm mostly using Firefox 39.0.3, because it plays well with Flash. (There were no issues like that with other browsers.) First I thought, that this was because I wasn't using the latest Firefox. As this Firefox version plays well with Flash, I didn't want to upgrade to the latest version, because with the latest Firefox, Flash playback on YouTube is jerky since Firefox 40.

But the Instagram issue repeated, when I was also using the latest Firefox for Android. Initially I thought, that this was the fault of Instagram, and since I don't use Instagram or Facebook, I didn't think much beyond that. And for a month or so, I couln't resolve it.

But when Instagram showed in a different computer in the latest desktop Firefox (43.0.4) with the same extensions installed, I began to investigate again.

When reloading a random Instagram page while also watching the Firefox Browser Console, I found an error, which, in pasted form, looks like this:

05:16:59.308 An error occurred during a connection to instagramstatic-a.akamaihd.net:443.

Peer attempted old style (potentially vulnerable) handshake.

(Error code: ssl_error_unsafe_negotiation)
1

After some searching, I found the solution in a game forum.

SSL safe negotiation setting

Turned out, that when perusing the Privacy Settings extension of Firefox, I had turned all the settings to most secure, and among them turned on security.ssl.require_safe_negotiation. After I turned that off, Instagram showed again.

If you don't have the Privacy Settings extension installed, go to about:config and type in or paste security.ssl.require_safe_negotiation . The boolean setting value for it should be false. If not (if it's true), then double-click the setting or press enter on it to set it to false. Or right-click for context menu to Toggle.

Otherwise, the Privacy Settings extension is awesome, and I recommend it to everyone.

Whereas people who manage instagramstatic-a.akamaihd.net, should implement new-style SSL/TLS handshakes to keep their corner of the web safe.

So this was the issue that affected me.

NoScript

If, on the other hand, the above is not an issue, then you might be having NoScript installed to defend your browser from malware, and among other things, it's blocking Instagram domains, which means they're not in the whitelist. Jump to domains.

NoScript has a blue "S" button that shows the status of whether a page is completely blocked, half-blocked (content from other domains has been blocked, which is most common), or completely allowed.

That button is usually visible in the location bar, or accessible through Firefox's hamburger menu. (If the blue 'S' is not there either, click the green Customize button in the hamburger menu to see if the NoScript button is listed in the 'Additional Tools and Features' section.)

One can change NoScript domain permissions thus:
* Hover the pointer over the blue "S" button, which launches a menu with a list of domains. If the NoScript menu is very long, it has small up and down arrows for scrolling.
* To whitelist a domain, click on "Allow domainname.tld". Alternately, domains can be blocked by clicking on "Block domainname.tld". This can be done in one go for several domains.
* Once the cursor hovers away from the menu, NoScript will automatically reload the affected page (or pages in other tabs). If a page or pages don't reload (per custom settings), they can be reloaded manually.

For Instagram, the following domain names must be allowed:

platform.instagram.com
instagramstatic-a.akamaihd.net
www.instagram.com

The above are all third-level domains, because they contain three name components separated by periods/dots.

By default, NoScript shows only base second-level domains, such as instagram.com without the www and a dot. For most common users with NoScript, allowing instagram.com and akamaihd.net is sufficient.

Independence Day: Resurgence website and Firefox

A quick post: www.warof1996.com might not display in Firefox and other Gecko-based browsers.

The reason is that the site is based on WebGL, and Firefox blocks WebGL, if the GPU (video card) driver is out of date or does not support WebGL.

The solution in Windows is to update GPU drivers either through the computer manufacturer's website or through the site of the GPU supplier — one of Intel, nVidia, or AMD/ATI, but not limited to only these.

Thorough care should be taken to match the driver to the correct display adapter model.

If that doesn't work, the GPU is too old, or EOL'd.

I strongly recommend not to force Firefox to use WebGL, because this move can damage hardware.

The alternative is to use Google Chrome or Chromium, which probably uses a CPU-based workaround; but if either the graphics adapter or the CPU or both are too old, then rendering is unlikely to work, or is too slow.

> Explanation — contains minimum driver versions that support WebGL.

In addition, visit about:support in Firefox and the Graphics section therein, which also recommends the minimum driver version for WebGL (Direct2D, etc). The posting contains the same warnings about possible damage to hardware if Firefox were forced to use WebGL.

System requirements

This table is incomplete. I've only gotten to test the website on three computers (with some reservations), and gotten an external report about another.

PC	Hardware/software specifications
	CPU	GPU	RAM	OS	Fx	Chrome	Notes
ASUS K53SC notebook	Intel Core i3 2310M @ 2.1 GHz, dual-core	i:Intel HD Graphics 3000 d:nVidia GeForce GT 520MX	4 Gb DDR3, 665.1 MHz	Windows 7 SP1	Yes	Yes	Required driver updates: I had to upgrade both Intel and nVidia drivers through downloading them from their respective websites.
ASUS U46SV	Intel Core i5 2410M @ 2.3 GHz, dual-core	i: Intel HD Graphics 3000	8 Gb	Windows 10 (build unknown)	Slow	Not tested	Website opens, but performance is slow and jerky, and the fan began working intensely.
	d:	nVidia GeForce GT 540M
ThinkPad R60e (0657-3WG)	Intel Core Duo T2400 (Centrino)	Mobile Intel 945GM Express	2 Gb DDR2 (an upgrade from just 512 Mb)	Windows XP SP3	No	Slow / ok	Rendering was slow, but the site was usable. Chrome: 48.0.2564.109 32-bit; Blink 537.36 JavaScript: V8 4.8.271.19, (This version already announced that it's to be retired on Windows xp.) Instead of OpenGL, Chrome's default renderer in Windows is ANGLE, which translates OpenGL ES to Direct3D, as it has better driver support. Thus, results for Chrome can differ.
hp dv5204ea notebook	Intel Celeron M 410 @ 1.46 GHz	Mobile Intel 945GM Express	1 Gb DDR2, 266 MHz	Windows XP SP3	No	Too slow	While I did upgrade the driver, its version is still less than required: The latest Windows XP driver for this GPU is 6.14.10.4926 (15.02.2008), but Firefox wants at least version "6.1400.1000.5218".
PC	CPU	GPU	RAM	OS	Fx	Chrome

All this does not yet indicate much as to what the titular website's actual system requirements are. In notebook computers, the default video card used by any program in Windows is the integrated adapter, while nVidia software provides an option to launch programs using its own GPU.

The Asus notebook with greater specifications falls below the threshold, whereas the Asus notebook with slightly lesser specs, an older operating system and updated video drivers shows the website nicely.

Copying and pasting table contents into comments in social networks and discussion forums

There isn't much sense in posting whole contents of tables into a comment under a post in most social networks, because directly copied-and-pasted content becomes plaintext, data is misplaced and garbled, because the comment and display area are not wide enough, and the intended overview becomes non-sensical anyway.

One can also choose to copy and paste only the first two columns, by holding down the Ctrl key in Firefox and dragging the mouse cursor across the cells with actual data starting from the ranking.

The data should first and foremost be pasted into a text editor, all the unnecessary data removed, and then copied and pasted here:

Top 10 countries by PEV market share of total new car sales in 2014 and 2013
^ Copied and pasted separately
# Country 2013 2014
1 Norway 13.84% 6.10%
2 Netherlands 3.87% 5.55%
3 Iceland 2.71% 0.94%
4 Estonia 1.57% 0.73%
5 Sweden 1.53% 0.71%
6 Japan 1.06% 0.91%
7 Denmark 0.88% 0.29%
8 Switzerland 0.75% 0.44%
9 United States 0.72% 0.60%

Source:
https://en.wikipedia.org/wiki/Electric_car_use_by_country#Top_10_countries

The result looks much nicer, but is still relatively unwieldy, because of variable-width fonts used by most social networking sites.

ID-kaardi tarkvara seadistamine modernses SeaMonkey lehitsejas

Modernse SeaMonkey lehitseja (näiteks versioon 2.6 ja uuemad) ning ID-kaardi tarkvara töölesaamine on omaette teema, mille kohta ma leidsin, et see vajaks eraldi käsitlust, sest kõik kohe tööle ei hakka. (Nimelt ID-kaardi tarkvara installer end SeaMonkey jaoks õieti ei seadistagi, seega osa asju tuleb käsitsi teha.)

Üldised tingimused, millega kogu krempel tööle õnnestus saada:
* Windows XP (SP2 või uuem; näiteks). Opsüsteemide suhtes tuleks olla siiski suhteliselt agnostiline;
* SeaMonkey 2.6 (ingliskeelne) — on tõepoolest vanem versioon, aga mitte nii vana kui 1.1.xx), seega SeaMonkey 2.xx;
* Oletame, et NoScript ei ole Firefoxis või SeaMonkey-s peal. (ID-kaardi ja NoScriptiga on veel täiendavalt igast jama.)

Nüüd.. eeltingimused peaksid olema sellised:

* ID-kaardi lugeja draiver peab olema installitud; soovitatavalt kõige uuem, mis vastavale opsüsteemile valmis tehtud;
* ID-kaardi tarkvara peab olema kõige uuem, juba peale installitud ning peaks näiteks Firefoxil töötama. Firefoxist veidi allpool, isegi kui tegemist ei ole kasutaja vaikimisi lehitsejaga.

Kuigi ametlikult on toetatud Mozilla Firefox, siis oletatavasti installib ID-kaardi tarkvara kaasaegne versioon EstEID Firefoxi plugina sellegipoolest Windowsi opsüsteemis pluginate üldisesse kataloogi. Sealtsamast kataloogist leiavad Gecko-põhised lehitsejad kõik pluginad automaatselt üles.

Tulemuseks peaks SeaMonkey' pluginate nimekirjas olema

EstEID Firefox Plug-in 3.7.1.1009

Kui see on olemas, siis on pool tööd juba tehtud.

Kui EstEID pluginat SeaMonkey pluginate nimekirjas pole, aga Firefoxis on, siis SeaMonkey-s peaks minema aadressiribal asukohale about:plugins — See peaks panema SeaMonkey ning teised Gecko-põhised lehitsejad otsima üles kõik olemasolevad ja võimalikud pluginad, mis opsüsteem pakub.

Siit edasi tulevad toimingud, mida Firefoxile tehakse automaatselt, aga mis SeaMonkey-s tuleb "käsitsi" teha:

• Laadida PIN-koodi küsimise moodul turvaseadete hulka:
  Edit > Preferences > Privacy & Security > Certificates > Manage Security Devices nupp:
  Device Manager akna vasakpoolses Security Modules and Devices nimekirjas peaks olema

  Estonian ID Card
 Virtual hotplug slot
 OMNIKEY CardMan 1021
  antud kaardilugeja mudel ^ on Eestis üks levinumaid, aga võib olla ka mõni teine.

  Kui seda pole (milles võib SeaMonkey puhul suhtkoht kindel olla), siis
  * vajutada vasakult nupule Load ja
  * uues aknakeses pealkirjaga Load PKCS#11 Device sisestada
  * Module Name: väljale
  Estonian ID Card
  * Module filename puhul ma annan praegu ette mooduli asukoha, mille leidsin Firefoxist:
  C:\WINDOWS\system32\onepin-opensc-pkcs11.dll
  Selle rea võib sinna nii asetada või kasutada Browse nuppu ja leida moodul failikorjajaga niimoodi üles ja sisestada. Vajutada OK. Device Manager aknas peaks uus moodul nähtav olema ning vajutada OK. Preferences aknas vajutada OK. Teha SeaMonkey-le restart.
• Edasi tuleb panna SeaMonkey-le kõik Sertifitseerimiskeskuse sertifikaadid. Need on saadavad siit:
  https://www.sk.ee/Repositoorium/SK-sertifikaadid/juursertifikaadid
  Põhimõtteliselt tuleks näiteks tirida sertifikaatide PEM-lingid uuele vahekaardile ja lubada igaühele autentimine vähemalt veebisaitidele [teine ja kolmas linnuke on vastavalt e-postile (e-mail) ja arendajatele (developers)]. Iga sertifikaadi puhul vajutada OK. Mõnedel juhtudel on osad sertifikaadid juba installitud ja SeaMonkey annab sellest lühikese teatega väikeses aknakeses teada. Teha lehitsejale restart.

Põhimõtteliselt peaks asi nüüd töötama.
Et järele vaadata, kas seadistus töötab, minna aadressile
https://digidoc.sk.ee
ja siseneda ID-kaardiga.

Täiendavad seaded:
Preferences > Privacy & Security > Validation —
Aktiivsed peaksid olema järgmised seaded:
[\/] Use the Online Certificate Status Protocol (OCSP) to confirm the current validity of certificates;
(*) Validate a certificate if it specifies an OCSP server.
Need seaded ^ peaksid olema vaikimisi sees, aga igaks juhuks tuleks üle kontrollida.

Mozillale NoScripti installimine Windows Vistas

Seesinane on siis eestikeelne kokkuvõte oma varasemast ingliskeelsest blogipostitusest. Alguses kirjutasin selle kohta ühele sõbrale, ning kuna tekst osutus siiski pikemaks, leidsin ma seejärel, et jutt vajab avaldamist.

Hiljuti ühes Windows Vistaga masinas avastasin Mozilla 1.7.13. Tegemist on siis tarkvarapaketiga, mille lehitsejamoodul on sama vana kui Firefox 1.0.8 (Aprill 2006; esitlusmootor pärineb 2004. aastast ja Mozilla enda arhitektuur 2001.-st aastast).

Et Mozilla mõnede lehekülgede JavaScripti pärast kokku ei jookseks, läks alguses palju aega, et kuidas sellele NoScript nii peale panna, et töötaks, sest umbes sama vanale Firefoxile Knoppix 4.0.2-s (2005) sai küll. Lõpuks jätsin asja katki...

Mõni kuu hiljem leidsin lahenduse (Mozilla tuli käima panna administraatori õigustega) ja siis panin peale NoScripti, aga nii, et see tuli kindlasti installida Mozilla kasutajaprofiili kataloogi.

SeaMonkey 1.1-ga sellist probleemi ei tohiks olla, sest SeaMonkey 1.1 ja Windows Vista arendus/väljalase langes umbes samale ajale, et põhimõtteliselt sai seda Vista jaoks siis veel kohendada nii, et oleks parem ühilduvus.

SeaMonkey 1.1.19 on üks viimastest vabatarkvaralistest graafilistest lehitsejatest, mis töötab Windows 98/Me peal.

Manipulating page styles with the new Greasemonkey

This article assumes that the reader knows some JavaScript and a fair share of CSS, and how to create userscripts for Greasemonkey.

The argument for using Greasemnkey is that it allows for a more straightforward implementation of user-created styles, which don't require remote storage, such as userscripts.org.

Well, as of recently, it became impossible to manipulate styles on pages with modern versions of Greasemonkey running within Firefox and SeaMonkey.

I suppose this might have happened during the transition from Firefox 12 to some newer version. Oddly, the version of SeaMonkey has always remained the same, so this should somehow have ruled out that issue. Then I began thinking of NoScript — which is about the only extension maintained well for both SeaMonkey and Firefox, and updatd accordingly — but I'm not going to point any fingers, just because I don't know what the real cause is.

So, the situation happened to me using SeaMonkey 2.5 (which I am not using often, though planning to upgrade one day) with Greasemonkey 0.9.13.1, and in Firefox 15 with about the latest modern releases of Greasemonkey (0.9.22—1.x).

Greasemonkey is officially available only for Firefox, but since SeaMonkey 2.x is not supported by many extension developers, then Philip Chee decided to modify ostensibly free software extensions originally made for Firefox to then post them at xsidebar.mozdev.org for other SeaMonkey users. Some of the extensions are modified by request of other users. So the most recent Greasemonkey version for SeaMonkey 2.3 or newer is 0.9.13.1, which is modern, but by no means the newest fare.

If you think usescripts somehow stopped working, then this is not quite so. Compared to older implementations, Greasemonkey has just evolved and so have ways to manipulate styles with usescripts. IMHO.

The traditional, or classic, way of inserting lines of style code in a Greasemonkey userscript was something like this:

document.styleSheets[0].insertRule('DIV[class=pagecontent] {width:auto !important; max-width:1014px !important;}', 0);

^ Nevermind !important, which was meant to override existing online style rules. Writing declarations with [square brackets] is also clunkier, but more reliable.

Now, there are a few things about the metadata block to remember when composing a userscript: @namespace and @grant.

• @namespace does require that something is written for it. For the example I had, I wrote random, and it works for a test script, but the string can't be empty and has to be meaningful, per instructions given in the link.
• With the second, I set @grant to none.
  T., 29.01.2013. update:
  @grant is a new(ish) security measure to limit API access of a script. With this it's possible to grant none (no API access) and grant GM_*, where script lines starting with GM_* are allowed. One such example is the simplified way of modifying CSS styles through GM_addStyle. To allow GM_addStyle, set

  @grant GM_addStyle

  In conclusion, this is what I think is something that I overlooked when initially writing the blog post herein.

Interestingly, I discovered that @include strings can be equipped with wildcards. This could be an age-old feature, but this saved me a bit of effort in writing userscript code:

// @include       *.wikipedia.org/wiki/*

• By not including http:// and https:// protocols, the userscript should work for domains under both;
• The asterisk * before the primary domain (separated by a dot) allows for inclusion of subdomains. Anyhoo, the new way to insert custom style blocks is this:

GM_addStyle("DIV.pagecontent {width:auto !important; max-width:1014px !important;}")

Works for me.

Possible causes for minor reductions in Firefox market share

This was first intended as a reply to the Firefox developer mailing list, but then I decided to post it here first.

Personally, there have so far been two gripes with Firefox that I've taken some issue with:
* One was the disabling of on-demand loading of pinned tabs after session restore (between versions 9–11);
* The other is the current brouhaha over Adobe's Flash crashing the plugin container process, which is really not the fault of Mozilla. (more below)

Sometimes it's not users leaving Firefox, but some of them starting to use Chrome as their very first browser. Well, Chrome coming around is a good thing, because this gives people more choice as to which browser they want to use, as Chrome and Firefox both possess unique and attractive features that meet their users' different needs.

HTML5 video
The current situation with Flash crashing the plugin container in Firefox is coincidentally a good cause for moving to HTML5 audio and HTML5 video, specifically Ogg Vorbis, Ogg Theora, and WebM, which are free and especially license-free formats.

YouTube's work in converting most of its videos to WebM reduces the immediate requirement and sometimes unpleasant chore of installing Flash on Linux, thereby increasing adoption of Linux, as other sites will hopefully follow suit in adopting free formats.

If we exclude the Summer low and the current Flash issue, then the next reason behind a reduction in Firefox usage could be the choice of format in sites using HTML5 video — most users tend to choose the browser that plays back whatever their favoured media site offers, with variations (mobile/desktop) of Chrome being in a rather advantageous situation right now, as it has built-in support for Flash.

Yet the situation with HTML5 video seems to be split right now along the lines of which HTML5 codecs are supported by which groups of browsers: Safari and IE vs. Opera, Chrome, Firefox and its derivatives.

The choice of YouTube and DailyMotion to offer videos in license-free formats is highly commendable. Now, if YouTube could actually stream high-profile events using HTML5/WebM in addition to Flash...

Desktop to mobile/tablet
Yet another reason in reduction of Firefox market share could just as well be the transition of people's major computing devices from desktops (including notebooks) to hand-helds (smartphones, tablets), nearly all of which currently have WebKit as their main rendering engine (in the form of either Safari or Chrome). I do not know if there has been a separate browser market share comparison for just desktop computers, because I understand that general tallies have usually encompassed both desktop and mobile spaces, with mobile being the separate segment.

Ultimately, as Mozilla and then Firefox were introduced, it was hoped that the browser market would eventually take the shape that it of recent times has started to form (at least worldwide) — in that no one browser would completely rule the market to be in its singularity the one to hold back innovation, and the one to pose itself in unintended consequence a widespread vector for malicious attacks.

So, in conclusion, the situation in my humble and perhaps half-informed opinion, is quite a bit more mixed with regard to what may be the possible causes of Firefox browser market share reduction this Spring and Summer.

Installing free and orphaned extensions to Debian Iceweasel and GNU IceCat

In part, this also applies to Mozilla Firefox.

Debian Iceweasel and GNU IceCat are browsers code-compatible with Mozilla Firefox. For those not in the know, they are both like Firefox, but rebranded, just as some shops order produce from a producer (whether or not they produce generic or their own brand-name products), and the shops then rebrand said produce as "their own". The reason with Mozilla Firefox is that it's a registered trademark that belongs to Mozilla.

There are a number of free extensions and themes for which their publishers don't have their own home pages anymore, and download links from the Internet Archive might not work for various reasons (the most common being that the files were not captured into the vault). These add-ons are generally available from addons.mozilla.org, but the site tends to shut out Debian Iceweasel and GNU IceCat.

Granted, some large Linux distributions have their own repositories that host compatible addons for a specific distro version's specific version of Firefox, but distribution maintainers move on, and repositories that cater for older distros with older Firefox versions are EOL'd, as repos have to host files for newer distro releases.

So, here I had a curious case with Go Green, an MPL-licensed theme for which there was no home page anymore, archive.org didn't host the theme's installer, and the only available place is addons.mozilla.org.

There are two ways to fetch the add-on from Mozilla:

One is the easy way, the other way is more complicated, but also
offers more choice.

The ostensibly user-friendly way to installed the latest version of an add-on is thus_

In the instance of the Go Green theme, you can go to

https://addons.mozilla.org/en-US/firefox/addon/go-green/

— in which page there are two obstacles: One is that all of mozilla.org always uses the latest Cascading Style Sheets (CSS) in formatting its pages, and so the older a version of Firefox is, the less able it is in rendering the pages. Fortunately, Firefox has this great option to view the page without CSS (Cascading Style Sheets).

The other is that JavaScript also blocks showing some links, even if the browser is modern.

So, choose to view the page with no styles:

View > Page Style > No Style

In this case, links and elements previously hidden with CSS will be displayed.

Then, to fetch a specific version of an extension, go to see "Complete version history" (you can jump to it using the text find function; link is clickable).

You should reach this address —

https://addons.mozilla.org/en-US/firefox/addon/go-green/versions/

Or, if you know the address of the add-on, just add versions/ to the URL to see all versions of an add-on, page by page (much simpler, I might add).

The All Versions page shows which browser versions the extension is compatible with, so the best bet is to choose the latest version of the extension that is good for a browser version that matches the prescribed version span.

At the section of a desired extension version, there's a "Continue to Download" link. The link is not clickable, but you can drag it into a new tab, or into the existing tab's widget to cause Firefox to resolve the URL.

In the Go Green theme's case, this will actually open the "roadblock" page, with this address for the page:

https://addons.mozilla.org/en-US/firefox/addon/go-green/contribute/roadblock/?src=search&version=1.25

Since you're using IceWeasel or IceCat, you might still be shut out by JavaScript from downloading an extension, with no download button in sight. This is reasonable, as some extensions won't work in Linux, but the script at mozilla.org is not always able to tell exactly that the user is actually running a compatible browser.

When installing extensions made for an operating system different than Linux, then install these at your own risk. It may be easier with themes, but some complex extensions require that you only install the one made for your operating system, especially if it's also been made available for the OS. I've seen this happen with the DOM Inspector extension, which is made by Mozilla, has been included with Firefox, and is specifically tailored to each specific version of Firefox.

As the roadblock page doesn't show the download link when CSS for it is active, choose to use no styles in the page (if you have so far been dragging the links into the tab widget, then the no styles setting for the tab persists)...

The "Download for Windows" link is placed at its coded position, but is not clickable (probably governed so by JavaScript), so drag it into a new tab and save the extension, or if it's already an xpi, install it.

If the add-on installer's filename has a .jar extension, then the extension can be saved as .xpi or renamed later.

This whole option is then simpler, but might not guarantee that you will be getting the right extension that is made for a browser running in your operating system.

With the Go Green case, the theme has only been made for Windows, but if the browser is compatible, it can also be installed in Linux and for Debian Iceweasel. Case in point:

Click for a bigger image.

Downloading the add-on by name from the Mozilla FTP site

To see if a Linux (or Mac) version of the extension is available, you need to find out the add-on's number at mozilla.org. In some cases it's available already in the extension URL, but I think this nomenclature is being phased out from the web front-end.

If you still don't know what's the number of the addon (if the add-on's address is named and not numbered), you can find it out through its add-on icon or other clues, like links and such. See

View > Page Info > Media

Look for an image, the URL of which matches

/addon_icons/

In that URL, the image's filename starts with a number, like

/13551-64.png

^ 13551 is the number of the add-on (64 is probably the native image width). After that, it's easy to find the add-on via mozilla.org's FTP site:

ftp://ftp.mozilla.org/pub/mozilla.org/addons/13551/

The FTP folder there will then display a list of all release versions of extension or theme installers, which are usually JAR or XPI files. If the installer is a JAR file, and you want to install it for Firefox or Iceweasel, download the extension's installer, rename its extension from .jar to .xpi — and then install it in the browser from the directory it's located in.

And to top it off,

The URL for the Go Green theme's latest installer is this:

http://releases.mozilla.org/pub/mozilla.org/addons/13551/go_green-1.25-fx-win.jar

Windows Me, Netscape 4.x

This text was written as a series of replies I posted in the YouTube comments section of a promotional introduction video of Windows Me, which can be found in the said operating system.

Since the video was not uploaded from the official source, chances are that the video and the comments to it won't be available at some point of time. So I posted them here for future reference.

And since Blogspot does not have limits on the amount of text, then I have edited the replies a bit to add text.

Windows Me was really good on something like a 667 MHz CPU and 128Mb RAM at the time. If you want to run reasonably modern software without swapping much, then you need 256 Mb of RAM (factor in [modern] web browser, IM program, OpenOffice 2.4.3).

Windows Me can run on less, of course, as it was included in computers that only had 64Mb of RAM.

At one point, Windows xp ran fine with 128 Mb RAM, but nowadays it needs 512M RAM as a real-life minimum to keep the system secure & do something productive.

These specs were for a new PC from around 2000 that was first supplied with only 64 Mb RAM. I requested it have 128 Mb, since the lesser setup was slow with multimedia of the time (it had fast Internet, so I knew it was the amount of RAM). After the RAM upgrade, using the computer was a breeze.

I also took very good care of the hard drive and the OS, keeping it updated & secure, and since its users mostly used Netscape for business, then viruses and exploits never made it there.

At that time it [the popular version of Netscape] was Netscape Communciator 4.x. I think on that PC we stuck with 4.79 for a long time (the last of 4.x was 4.8, released in 2002 :-). The 4.x branch was the first to support CSS, but that was the only feature which caused crashes when turned on (especially in 4.0x), so I kept it off on all our Netscapes, which were fairly solid after that. Despite the clunky Navigator, the best part was the e-mail client, which introduced mail filters to fight spam (then seen as controversial).

We skipped Netscape 6, never considered 7.x, and in newer PC's moved instead to Mozilla, the open-source descendant of Netscape and which Netscape 6 and 7 were based on anyway.

As Mozilla Foundation started Firefox, it ceased Mozilla development, which was taken over by others, and Mozilla Application Suite became SeaMonkey.

The last version of SeaMonkey for Windows 98/Me is 1.1.19 ([from] 2010); its Gecko rendering engine is a wee bit newer than that of Firefox 2.0 (Gecko 1.8.1.20 vs 1.8.1.24).

Cannot play videos on Yahoo! News?

Symptom: This often happens with users of Firefox and other Gecko-based browsers, when:
• they can't show most news videos on the Yahoo! News website and some other Yahoo! properties;
• the commenting system is not functional (can't properly view and post comments).

Privacy-conscious users, and/or those who wish for their browsers to consume less resources, use a script blocking add-on, such as NoScript. I often have NoScript configured to allow/disallow full domains (like d.yimg.com) and not just second-level domains (just yimg.com).

As it often happens, allowing only full subdomains instead of just second-level domains brings with itself more issues.

By default, NoScript includes a whitelist of second-level domains without which major services' functionality would be wholly disabled. The whitelist also contains yahoo.com, yimg.com, and yahoopis.com). The instructions herein are for users who have chosen to impose a more fine-grained control over the websites they visit.

Right, well, I finally played around with NoScript and found a solution:

NoScript:

In addition to news.yahoo.com and screen.yahoo.com and maybe others, allow the following domains essential for video playback:
• l.yimg.com
• d.yimg.com
• connect.facebook.net (If you're privacy-conscious, then allow temporarily).
  
  
11.07.2012. Update: I later discovered that non-video news items also featured videos, so here's an addition of domains that must be allowed:
• video.query.yahoo.com
• yep.video.yahoo.com
• yui.yahooapis.com (important on other Yahoo properties, even if not using video)
• webplayer.yahooapis.com

Flashblock:
• Allow d.yimg.com

^ Including only that domain in the Flashblock whitelist will have the video area rendered with the Flashblock placeholder. Clicking on it will start playback (note that ads are also played).

• Allow l.yimg.com

^ In regular news items that included video, disallowing l.yimg.com wouldn't even load the Flashblock video placeholder.

If you want video to load automatically, allow the above domains, and news.yahoo.com and screen.yahoo.com (and/or other Yahoo! properties as necessary from the Flashblock toolbar button).

Conclusion

Even if l.yimg.com and d.yimg.com are enabled in NoScript, the crucial part for some erroneous coding reason is connect.facebook.net; If that is not allowed, most video code and commenting functionality won't load. Note that connect.facebook.net is the primary culprit. This has been discussed before at forums.informaction.com (a NoScript and web security forum).

Cheat sheet and notes for using Knoppix 6 or newer

This I initially made for myself, but then writing got out of hand :-)

For a full-page treatment, see here.

Flash

Knoppix 6.0.1 includes Iceweasel 3.0.6, which does not have support for HTML5 video, so you need to install Flash to watch multimedia. Granted, these versions of Knoppix and Iceweasel are rather outdated, so Knoppix 6.7.1 (or 7) is often a better choice on a new computer.

Another option is to download and install a newer version of Firefox. See below.

The version of Flash compatible with Knoppix 6.0.1 is 10.3. Download it, extract libflashplayer.so into the
/home/knoppix/.mozilla/plugins directory (the plugins directory must also be created). Restart Iceweasel.

02.05.2013. Update

Modern Firefox

By May 2013, Iceweasel 3.0.6 has become so old and outdated that it's not supported by major websites anymore. This includes Google and all its properties (YouTube, Google Drive/Docs, Blogger, and others). The same applies to Yahoo!, twitter, and many other major sites and services.

Using Synaptic in Knoppix 6.0.1 to upgrade to Iceweasel 17 is impractical on account of the Iceweasel 17 package having hundreds of dependencies that must also be upgraded, which really amounts to a whole operating system upgrade. Therefore it's simpler to get the Firefox Linux binary.

The latest official major version of Firefox that still works in Knoppix is version 17, specifically 17 ESR (Extended Support Release). Newer versions won't work.

Firefox 17 ESR can be obtained from Mozilla's FTP site, and I got the latest version here:
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/17.0.6esr/linux-i686/en-US
Since Firefox 17.0 ESR is in active maintenance (17.0.6 released on 09.05.2013., which is very recent), then Mozilla is likely to release newer patchlevel versions.

Since new patchlevel versions are placed in a different FTP directory, then...

...here's a beginner's "navigation how-to" for people unfamiliar with FTP

Primer

FTP (File Transfer Protocol) is older than the web, and it has been very useful in facilitating large downloads. The content of FTP sites is structured hierarchically, as in folders in a computer file system. Files and directories are listed in alphabetical order UNIX-style: directories are not sorted first, but like all other files; items starting with capital letters are at the top of the list, then followed by lower-case items. In a graphical browser, file and folder names are linked and thus clickable.

Mozilla's FTP site

FTP URLs are given as examples
As Mozilla releases a new version of Firefox, then all files specific to a version are given their own directory. Genereally, all Firefox versions are placed in /releases folder of Mozilla's FTP site:
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases
The latest version at this time is 17.0.6 and you can scroll down the list to enter that directory:
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/17.0.6esr

As Knoppix is Linux, choose /linux-i686
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/17.0.6esr/linux-i686

What you get in the /linux-i686 directory is a longish folder listing of different Firefox language versions (Firefox is released in many languages), listed in the format of ISO-639-1 two-letter language code followed by ISO 3166-1 alpha-2 two-letter country codes.

The respective code combination for English-United States is en-US —
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/17.0.6esr/linux-i686/en-US

There you'll see the archived Firefox binary firefox-17.0.6esr.tar.bz2 —
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/17.0.6esr/linux-i686/en-US/firefox-17.0.6esr.tar.bz2

Download this file to the Desktop. Once the tar.bz2 file is downloaded, go to the desktop, right-click on the file, choose the Extract > Extract To... command. You'll get a file/location picker and the default should be the Knoppix folder. Press OK to extract.

The Firefox executable is then in the /home/knoppix/firefox/ user directory (knoppix being the user account folder).

Even after Firefox is extracted, a shortcut won't be created to the Knoppix LXDE desktop environment menu.

Do keep in mind that since Iceweasel is code-compatible with Firefox, they both share the same user settings located at /home/knoppix/.mozilla/firefox

It is thus recommended to create a different profile for Firefox.

You can start Firefox from the command line:

knoppix@Microknoppix:~$ ./firefox/firefox -P &

./ stands for specifically targeting a folder from within the current directory;
-P forces the start of the Firefox Profile Manager;
& (ampersand) makes sure that Firefox starts independently from the terminal window.

After that, the Firefox Profile Manager opens up and you can create a new Firefox profile. When doing so, assign a new and simple profile name.

If you close Firefox, you can start Firefox again from the command line using the new profile:

./firefox/firefox -P newprofilename &

Alternately, the easier way is to unset starting Firefox or Iceweasel in a profile automatically. That way it's slightly more user-friendly to choose a profile, at least when starting Iceweasel. Whereas with Firefox only the ./firefox/firefox command without can be used without having to invoke additional command-line options.

So much for now. I might continue and expand on this further.

Why Iceweasel versions before 2.0 are not Debian-based

One nice day I found a screenshot of Iceweasel that looked like a version prior to Iceweasel 2.0 and added in its description that it was Debian Iceweasel, as browsers named Iceweasel with a lower-case w are usually Debian-based. (As opposed to GNU IceWeasel, which in 2007 was renamed to IceCat to avoid confusion.)

It then turned out for me, this particular screenshot, and other screenshots in the database that it was not so for the reasons that follow.

The uploader of the screenshot had the unintentionally good sense of including the taskbar of the operating environment, which happened to feature a program window with the title of package iceweasel-1.5.0.4-g1-i386. While this got me to get the version number right, the package name was just enough information to start looking further, results of which only pointed to Gnuzilla servers and mirrors. This put me into some doubt as to whether the browser in the screenshot was Debian Iceweasel, and looking even further, my doubts were confirmed.

Locations for iceweasel-1.5.0.4-g1-i386 available here:

From a selective search of most GNU mirrors, I found only one mirror still actually hosting some original files:

ftp://aeneas.mit.edu/pub/gnu/gnuzilla/
http://www.ftpdir.hu/aeneas.mit.edu/pub/gnu/gnuzilla/

The relevant binary files there were last modified on 06.09.2006 00:00.

From the Internet Archive I found another mirror which has hosted iceweasel-1.5.0.4-g1-i386:

web.archive.org/web/20070507153807/http://ftp.download-by.net/gnu/gnu/gnuzilla/
(also features a later capture)

The binaries were last modified on 05.09.2006 23:59, so a minute earlier than those at aeneas.mit.edu.

Note that researching this kind of history through the Internet Archive has three or so limits:
* I tested to see if only an HTTP mirror had an archive page. Although I did not try to see if the WayBack Machine archives FTP pages, too, I didn't find any necessity for it either; Assuming also that the WayBack Machine does not archive FTP folder listings in the first place;
* The Archive has its own exclusion list of servers that it won't crawl (limited in relation to the GNU mirror list);
* Many mirrors had blocked crawling through robots.txt, as mirrors anyway host large files, which can be taxing to the Internet Archive. It's still useful for the WayBack Machine to archive programs — especially device drivers and obscure program packages, because the Internet Archive can sometimes be the only place where these can be found.

Through my searching whether an HTTP mirror has an archive page, then in the process a substantial number of those ftp-as-http mirrors that allowed crawling had their /gnuzilla folders captured by the Internet Archive. This should serve useful at tracing browser history with a similar method in any possible future research.

No other mirror services in the list of GNU mirrors that I searched at contained the original packages of iceweasel-1.5.0.4-g1-i386.

Left out from the search:
- South America: Brazil /only country in the list;
- Africa: South Africa;
- Asia: Bangladesh, China, Japan, Malaysia, Oman, Pakistan;
- Europe: Greece, Portugal, Spain.

(Funny, Israel was in Asia, too :-)

There were two reasons for leaving these countries out of my search: Either a non-sensical URL (which I couldn't recognize as something resembling legitimacy), or the country is not trustworthy enough to visit its websites, no matter how harmless on appearance. The amount of servers not checked was approximately 10-15%, based on guesswork.

A user-published package of 1.5.0.8pre2 available at safeweb.sitesled.com/iceweasel

Now, Debian started including Iceweasel as a rebranded replacement of Mozilla Firefox only since version 2.0, after which GNU slightly renamed their package to IceWeasel (note capitalisation of W), then a year later renamed their package to IceCat to finally avoid confusion with Debian's own package.

In conclusion, all Iceweasel versions prior to 2.0 are Gnuzilla-based.

I had to add to that screenshot file's notes that this was a screenshot of a Gnuzilla-based Iceweasel and not one of a Debian-based Iceweasel. The GNU IceCat Wikipedia page was also of great help in determining the right source.

ClamWin Antivirus Glue for Firefox

If anyone is still using Firefox 1.5–2.0 and ClamWin, too, then they'd be interested in the subject extension. Unfortunately, this addon has been delisted from addons.mozilla.org and very hard to find from FTP sites (which I tend to trust more).

So I found what turns out to be only one source:
• http://pub.vse.cz/pub/Mozilla/addons/771
• http://cache.vse.cz/pub/Mozilla/addons/771
The license for the extension is MPL 1.1/GPL 2.0/LGPL 2.1.

Caveat

Version 0.2.4 officially works in Firefox 1.5, but here are instructions in a 18.01.2007 comment to a blog post on similar matters. (The original text was here.)

Instructions in my own words: Download the XPI file (the lowermost is the newest version; if you are not sure, then check the statusbar when mousing over the 0.2.4 file link), extract it into a folder, open install.rdf with an editor that supports CR & LF linebraks (NotePad2 is ok); there, edit the em:maxVersion parameter value from 1.4-something to 2.0.0, compress the decompressed files, then rename the file's .zip (I assume) extension to .xpi, then move the file into an open Firefox window to install. When recompressing, make sure that you're only compressing the selected files and folders within the extracted folder and not the folder itself.

Modern stuff

For people using newer browsers, see the Fireclam extension for both Mozilla Firefox 3 and newer, and SeaMonkey 2 and newer.

DOM Inspector XPI for older Firefox/IceWeasel browsers

Knoppix is the kind of distro that by default does not include the DOM Inspector, it's only on a CD, and I think I had even spent a month searching for a way to install it from a .deb file to a version of firefox in Knoppix. All in vain, even if I had the supposedly right package, because it would still prove incompatible and thus unusable (would crasshh).

Then, by chance, I found the right way to install the DOM Inspector XPI separately for Linux in those distros, where a package might be missing (such as a relevant .deb package in Knoppix 4.0.2, because it's a snapshot from Debian's testing branch of the time) or not included at all... — By downloading a specific DOM Inspector XPI from the old mozilla.org FTP site, which is archived at mozilla.org's own ftp site:

ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/1.0.6/linux-i686/xpi

Caveat in Knoppix and other Live CD-s: You can only install it as superuser, it won't install into the user directory and thus it won't save, but rest assured, you can install it again every time you need it, although it may be tedious for daily use, if that might be the case for some users.

Here's what you have to follow, if you're stuck using a LiveCD, a version of Firefox without DOM Inspector built-in, no package repository to rely on and no package to be found for your particular distro (Knoppix):

1. Find out what your version of Firefox is in your Live CD (launch Firefox; Help>About). For some Knoppix Live CD's I sometimes use, mine is 1.0.6 for Knoppix 4.0.2 and something else in newer versions of Knoppix. Keep in mind that newer versions of Knoppix include Debian IceWeasel (Knoppix is based on Debian), which is a source-compatible rebranded copy of Firefox.
2. Exit Firefox, relaunch it as superuser, best with sudo firefox
3. Go to
   ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/
4. From there, choose the version of Firefox/IceWeasel/GNU IceCat you are stuck using (if using a browser click the relevant version folder link);
5. Once there, browse to a folder called linux or linux-i686 and there browse to the xpi folder. Note down the address in a separate editor.
6. (Make sure that ftp.mozilla.org is the allowed domain to install XPI's)
7. Click on adt.xpi (the XPI for DOM Inspector), which should be at the very top of the directory listing, go through the extension installation procedure. If after installation you don't see the extension listed, don't worry. Restart Firefox again as superuser, via sudo (you should now know how to use it). Verify that DOM Inspector is installed by checking the Tools menu. Exit the sudo'd Firefox.
8. Start user-mode Firefox and you should see the DOM Inspector appear there.
9. To maintain that you still have the XPI for future use, save it to local storage (a memory stick, for example) by downloading it in a normal-user firefox session from the same FTP address.

Now, I haven't been able to find out an XPI of the DOM inspector for older versions of Firefox that would actually work as an extension installed into the user profile, so until then, it's more of a case for frequent users of DOM Inspector in older Firefox browsers on a Live-CD of reinstalling the XPI after every restart.

Settings for DOM Inspector can be changed through about:config, then search using the inspector string.

Putting stuff before a counter with CSS and associated caveats

I thought this too important to be passed up, so here's only a very rough draft of what I discovered. And because I was only revisiting this subject right about now, I have yet to get my own head around all this, with more detailed explanations.
(Blogger had nasty issues with updating their software, so a number of blogs were in read-only mode and so instead of writing this up I was occupied with other things. The good thing is that Blogger have been very responsive in addressing the posting outage.)

When tallying personal data and opinions for what was ostensibly a list of items in a text file, I wanted to find out how in an ordered HTML list (a numbered list with <OL> tags) I'd be able to use Cascading Style Sheets (CSS) to place some special items before counters (usually numbers, but CSS 2 standard has expanded counters to be much more) as markers of some sort.

The main point was to make a more informative and interesting list... Well, yes, but this turned out to be a far more difficult exercise than I first thought.

For an intro, the following describes the differences in rendering between Mozilla Firefox 2 and Mozilla Firefox 3+. Because these browsers use the Gecko rendering engine, which is used by other browsers, then here's also a quick browser side-by-side of the rendering engine's branches:

Gecko 1.7	Gecko 1.8.1	Gecko 1.9 and newer
Mozilla Firefox 1.0	Mozilla Firefox/IceWeasel 2	Mozilla Firefox/IceWeasel 3+
Mozilla Application Suite 1.7	SeaMonkey 1.1	SeaMonkey 2+
	K-Meleon 1.5	K-Meleon 1.6+

What follows is example CSS code with some comments. I haven't yet had all the time to describe everything, but bear in mind the lede.

OL.Eurovisioon {counter-reset:item; list-style-position:outside}

OL.Eurovisioon LI {display:block;}

/* • display:block ^ loses the browser's automatic numbering;
• The items must be displayed as block, so as to make sure that the later width attribute applies. */

OL.Eurovisioon LI:before {float:left; content:'miskitekst\ ' counter(item) '.'; counter-increment:item; border:solid 1px gray; padding-right:5px; width:82px; text-align:right; line-height:1.1em; color:navy; white-space:nowrap} _{/* these work... */}

/* ^ • Floating them left makes sure that the items are displayed like in a standard ordered list;
• item must be inside counter(), item is also specified for counter-increment;
• text-align:right aligns numbered counters right and so makes it more list-like again;
• white-space:nowrap makes sure that when increasing text size, text inside blocks wouldn't wrap and add in height and take away from the structure.

Caveats:
Once the items are all displayed as text-block or inline, the width attribute does not apply anymore. Displaying as block and floating to right works in Firefox 4 (I'm also assuming 3.0+), but not in SeaMonkey 1.1 and anything with the Gecko 1.8.1 engine (see the above table) and the caveat applies to all older browsers.). Setting the display to text-block or inline fixes the issues in SeaMonkey 1.1, only that setting width attributes does not work then. */

OL.Eurovisioon > LI.plus:before {width:82px; content:'\ sisu\ ' counter(item) '.\ '; text-align:right; color:blue} _{/* somehow works */}

OL.Eurovisioon > LI.plus {list-style-position:outside}
^ Is this really necessary?

Moreover, the list already contains tabular data; including informative content with :before or :after pseudo-classes means that this data won't be indexed and may be lost to search engines. Non-graphical and older browsers won't be able to see such content.

I, of course, thought that I'd never see the day when my own fancy CSS implementation would not be visible with something like SeaMonkey 1.1.19.

The correct rendering is supported by Mozilla Firefox and IceWeasel 3 (probably since 3.0), SeaMonkey 2, Google Chrome (Version 11 does, so I'm assuming a host of earlier versions do, too), and the latest Konqueror, Apple, and Opera fare. Internet Explorer 7 does not support this. Bleh.

So here's the example list:

1. tekst
2. teine tekst
3. kolmas tekst
4. neljas tekst

with corresponding code in HTML:

<OL CLASS=Eurovisioon>
<LI>tekst</LI>
<LI CLASS=plus>teine tekst</LI>
<LI>kolmas tekst</LI>
<LI>neljas tekst</LI>
</OL>

So long I still have to use Mozilla Firefox 1.0, I must still use a simple HTML table. At least the advantage is that most browsers will be able to see the content. The table in question is here.

As the information was laid out in a text file, it nevertheless turned out to be tabular data, which was actually much simpler to organise into a table, rather than implement complex CSS for the same.