Web Browser

[Hänsel]

Nicht umsonst soll man immer updaten. Außer windows das wird dann immer mehr schlechter hahaha

 

[crysmopompas]

Opera-Übernahme geplatzt: Chinesen wollen jetzt die Browser-Sparte

Der Verkauf von Opera Software an ein chinesisches Konsortium ist offenbar an der fehlenden Zustimmung der Aufsichtsbehörden gescheitert. Jetzt soll das Unternehmen geteilt werden.

 

[crysmopompas]

https://blog.mozilla.org/press-de/2016/07/20/weniger-adobe-flash-in-firefox/

Wie letztes Jahr angekündigt, soll Firefox ab März 2017 keine NPAPI-Plugins mehr unterstützen – abgesehen von Flash. Die nächste Firefox ESR (Extended Support Release), die ebenfalls für März geplant ist, wird Plugins wie Silverlight und Java noch bis Anfang 2018 unterstützen.

 

[crysmopompas]

Firefox: keine Feature-Updates mehr für Windows XP / Vista ab März 2017



Gibt dann ein ESR Release. Wenn dessen Supportende erreicht ist, ist damit für XP/Vista Schluß mit FF.

---------- Beitrag um 23:00 Uhr hinzugefügt ---------- Vorheriger Beitrag um 22:55 Uhr ----------

OMG. NPAPI wollen sie rausschmeißen. Dafür die PepperAPI einbauen.
Sie versuchen wirklich alles sich nicht mehr von Chrome zu unterscheiden. Marktanteil nimmt trotzdem oder gerade deswegen immer weiter ab.

Mozilla experimentiert mit Support für Chrome-Plug-Ins

 

[FlyingUberHuzo]

Opera ftw!

 

[crysmopompas]

Der ist mittlerweile wieder benutzbar und hat auch ein paar schöne Features bekommen.
Langsam läßt der Schmerz nach, auch wenn der alte ein ganz anderes Stück Software war :cry:

 

[crysmopompas]

Von SeaMonkey gab es nun schon einige Monate kein Release mehr :/. Das kleine Team hat mit diversen Problemen in der Infrastruktur von Mozilla zu kämpfen. Dauert jetzt hoffentlich nicht mehr ewig.

Yes. Long time no post.

Why? Is the SeaMonkey project dead? The last was 2.40! That’s a long time ago! (well, not really… but long enough.) Where is everyone? Why has there been no posts or mentions? (and a host of other questions…)

Just want to mention that 2.46 is currently being spun… and by spun, I mean wrenched… like loosening a very tight bolt that’s been superglued to the screw.

“What do you mean?” some might ask.

At the start of the process, we managed to hit a few hiccups… well…not so much as hiccups but boulders the size of Boulder, Colorado with large signs saying “Stop… you cannot pass!” (Hyperbole much?)

tl;dr (or if you wish, you can still read)

Since 2.40… the releng team has been ‘trying’ to unbust the infrastructure to the point that things are starting to go green. (Yay!) though we still have some l10n nightly troubles (bah humbug). So with the desperate need of getting a release done, the project felt it was a good time to build 2.46 before something crawled out of the moco workshop to put a kaibosh on our release… little did we know.

So, we (not really throwing caution to the wind… more like hoping with baited breath) started the build….

… only to come to a crashing halt at the 2nd step. (Moco *did* make a change to hg.mo’s infra (thus changing the fingerprint) and caused the build bustage as well as some environment variables that should’ve been set but weren’t for some reasons (probably changes in the releng code that didn’t get translated to the release releng code… my bad).

So. 2.46 will be out. Just not today and my guess, not tomorrow either. Sorry. But since everyone’s waited for so long… what’s a couple of days more? You’re right. Not a good excuse.

Please do stay tune to this channel… more updates soon as we unhork those boulders (hyperbole.. I know).

:ewong

https://blog.seamonkey-project.org/2016/10/13/update-on-2-46/

After 6 builds (tries), we are still mired in the morass that is l10n repacks.

For those who are curious, it’s bug 1231349 .

There is a workaround for this; but, it is considered a hack and not really solving the problem, which afaik, is basically the backend mozilla code having some repacking difficulties with the extensions that we include (DOMi, Chatzilla). While we figure out the backend code, I’m spinning up a DE repack to test out the workaround and to determine if there are issues with releasing repacks created from the workaround.

:ewong

 

[crysmopompas]

WOT-Addon: Wie ein Browser-Addon seine Nutzer ausspäht

Jede URL, die ich in diesem Zeitraum besuchte, erscheint ungekürzt, inklusive Session ID, in den Datensätzen des »Datenhändlers«. Diesen Vertrauensbruch wirklich und wahrhaftig zu sehen hat mich ehrlich gesagt schockiert, auch wenn ich schon so einiges gewohnt bin. Letztendlich ist es mir gelungen, mich über die Datensätze selbst zu deanonymisieren – gruselig, einfach gruselig.

Die Analyse beweist: WOT protokolliert das Surfverhalten eines Nutzers nicht nur lückenlos, sondern verkauft / gibt die Daten offenbar auch noch an Drittunternehmen weiter. Es ist bezeichnend, welchen Aufwand die Entwickler betrieben haben, um die übermittelten Daten vor dem Auslesen zu schützen – trotz TLS-verschlüsseltem Kanal. Erst durch eine Anpassung des Quellcodes wurde sichtbar, welche Informationen WOT tatsächlich an die Server überträgt. Anders als in der Datenschutzerklärung behauptet, können die von WOT gesammelten Informationen allerdings sehr wohl zur Deanonymisierung von Nutzern beitragen – wie die NDR Recherche eindeutig belegt. Und darin liegt auch der Skandal: Die Sammlung personenbeziehbarer Daten, die im Anschluss dann auch noch an Drittunternehmen ausgehändigt werden.


Damit wäre hoffentlich ein weiteres Märchen widerlegt: Selbst wenn ein Unternehmen in seiner Datenschutzerklärung behauptet, sie würden keine personenbezogenen Daten sammeln oder diese vor der Speicherung »anonymisieren«, so sieht die Realität oftmals wohl ganz anders aus. Letztendlich müssen wir uns immer und immer wieder von neuem die Frage stellen: Wem oder was vertrauen wir eigentlich? Dem Web of Trust bzw. WOT-Addon vermutlich nicht mehr.

 

[crysmopompas]

400 Bad Request

Request Header Or Cookie Too Large

nginx/1.11.3

lol. In Chromium geht die Seite.

 

[crysmopompas]

Opera hat mittlerweile tatsächlich ein paar Fixes für Opera 36 zurückportiert für XP/Vista User

Some of you may know that the last Opera version compatible with Windows XP and Vista was Opera 36, which is based on Chrome version 49. We promised we would continue to issue security updates and crash fixes to the Opera 36 branch, and this is our first such update with backports of fixes for some security issues that were fixed in Opera 37, based on Chrome 50.

We hope these fixes will help to keep the browser a tiny bit more secure and stable. Opera 36 users will receive the update automatically; it is also available on opera.com for them.

http://www.opera.com/blogs/desktop/2016/08/security-update-windows-xp-vista-users/


Downloads sind wie immer gut versteckt, und hier zu finden:

https://ftp.opera.com/pub/opera-winxpvista/

 

[Tommyfare]

Ich wünschte Firefox würde mal was machen. Das ist total langsam geworden. Auf dem PC geht es gerade noch aber auf dem Mac ist es eine Katastrophe

 

[crysmopompas]

Der Plan steht: Mozilla tötet eines seiner exklusivsten Features in Firefox, die sehr mächtigen Add-Ons. Übrig bleiben Erweiterungen im Chrome-Style.

Zur Einstimmung wird der vor einiger Zeit eingeführte Signaturzwang mißbraucht (soll uns doch nur vor Malware schützen ), um in FF53 keine neuen Erweiterungen im alten Stil mehr zu erlauben.

Firefox 53

AMO will no longer sign new SDK, XUL or XPCOM based extensions for Firefox Desktop. Only new WebExtensions add-ons can be created for Firefox Desktop. Existing SDK, XUL or XPCOM based add-ons can still be updated and signed. Firefox Android, Thunderbird and Seamonkey extensions will be unaffected.



Firefox 57

Only the following add-on types will be loaded by Firefox in release:

• Signed WebExtensions.
• Signed bootstrapped system add-ons.
• Language packs.
• Dictionaries.
• OpenSearch plugins.
• Lightweight themes.

https://wiki.mozilla.org/Add-ons/2017
https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/

---------- Beitrag um 15:07 Uhr hinzugefügt ---------- Vorheriger Beitrag um 14:59 Uhr ----------

Android

At this time the level of WebExtensions is not good enough to provide a reasonable timeline for Android support. Once Android has reached reasonable support, we’ll aim for a similar timeline for Android.

Toll, dann gehen zukünfitg am Desktop also nur Web-E. und bei Android nur alte .


Für Seamonkey ist das ganze sowieso eine Katastrophe :cry: :cry: :cry:

 

[mojo]

warum tun sie das?

 

[elomaniak]

Vielleicht verwenden die Chefs ja keinen Firefox und wissen nicht was sie den endnutzern antun.

 

[crysmopompas]

warum tun sie das?

Weil sie XUL für veraltet halten, und glauben das hält Entwickler vom Entwickeln von Add-Ons ab.

Daher kopieren sie das Interface von Chrome, und haben vor das in seinen Möglichkeiten zu erweitern. Nur kann es aktuell viel weniger als das alte, und wird es ziemlich sicher auch nicht zur geplanten Abschaltung können. Vieles vermutlich auch niemals.
Das alte Modell (XUL/XPCOM) ist extrem mächtig, man kann afaik damit so ziemlich alles im Browser ändern. Für die neue DAU-Klick-Mich-Store Welt ist das natürlich viel zu gefährlich

---------- Beitrag um 16:35 Uhr hinzugefügt ---------- Vorheriger Beitrag um 16:23 Uhr ----------

nochmal zum Nachlesen die urspr. Ankündigung

XPCOM and XUL are two of the most fundamental technologies to Firefox. The ability to write much of the browser in JavaScript has been a huge advantage for Mozilla. It also makes Firefox far more customizable than other browsers. However, the add-on model that arose naturally from these technologies is extremely permissive. Add-ons have complete access to Firefox’s internal implementation. This lack of modularity leads to many problems.

https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/


Wenn man sich die Marktanteile der letzten Jahre anschaut, hat die bisherige "Chrome"-Strategie von Mozilla den Absturz von FF nicht verhindert. MS hat sich mit dem Edge-Launch auch selbst in's Abseits geschossen.
Bleibt nur noch Chrome Chrome Chrome Chrome Chrome Chrome Chrome Chrome Chrome Chrome Chrome Chrome Chrome Chrome

---------- Beitrag um 16:57 Uhr hinzugefügt ---------- Vorheriger Beitrag um 16:35 Uhr ----------

http://gs.statcounter.com/#desktop-browser-ww-monthly-201111-201611

 

[mojo]

kein vivaldi in der statistik..


wobei edge echt nicht übel ist für das was es ist. An der Addon Front noch sehr dünn, aber er ist wirklich schnell.

 

[tweebears]

kein vivaldi in der statistik..

Was hast du denn erwartet?

 

[mojo]

die weltherrschaft!

 

[tweebears]

Nicht mit einem Marktanteil von 0.03%

 

[crysmopompas]

Re: DownThemAll and WebExtensions [… or why why I am done with mozilla]

Spoiler

Hi mig[-1], and everybody who also asked and I BCCed, and whomever it
may or should concern too,

First: the "fucks" are directed exclusively at mozilla - the
organization, not you.

If I CC'ed you and you're now thinking: Who are you even? Valid
question: I develop one of the most popular Firefox add-ons (open source
without profit motivation), and am a decade long mozilla enthusiast,
advocate and volunteer contributor.


> I'm just back from a Mozilla event where i was sorry to hear you were
> giving up on DownThemAll. I don't know the whole story, but in my
> opinion, this would be a shame to leave a 1.25M users audience.

The whole story is basically that mozilla folks are fucking up the
add-on space.

The whole story is that DownThemAll! would need a ton of niche APIs that
mozilla has neither the resources nor the will to spec, implement and
maintain[0].

The whole story is that WebExtensions APIs explicitly are supposed to be
high level APIs, while tons of add-ons actually want, nay need low level
APIs to implement their functionality.
The rational here seems to be "Fuck yall, we consider you too stupid
and/or evil to give you low level access, also we're lazy and not good
with money so we couldn't possibly support low level anyway"
The high level API shit is what's killing the platform, not XUL or
(partial) XPCOM deprecation.

The whole story is that I just finally grew tired of the steaming pile
of utter rotten horse manure that is the mozilla decision making process.

I'll evaluate the list of forks that do exist or will exist once mozilla
pulls the WebExtension switch for real, and see if any of them will be
an alternative to the then deliberately-made-retarded mozilla browser.

I gave mozilla a list of what interfaces DTA source code contains
currently (mozI*, nsI*) either way and other feedback, since they asked.

It is my opinion that it's not me who's leaving a 1.25M Active Daily
Users DownThemAll! audience, but mozilla is abandoning them (and me) and
not just them but also the developers and users of tons of other add-ons
with small and large audiences[1].

I'll keep maintaining (most of) my add-ons for the time being, albeit
with far less enthusiasm, in case mozilla wakes up or some viable fork
comes along, tho.


> As far as i can tell, DownThemAll will be able to run on WebExtensions
> once the missing APIs (mainly file writing) will be integrated, and i
> got the confirmation this will happen in due time.

I have no hopes that they will implement proper APIs, not even for file
writing[0 again]. Other than file writing, there are no proper APIs to
do requests, there are no proper APIs for other stuff such as executing
files, other kinds of OS integration, UI integration and so on and etc
and pp.

And that's just DownThemAll!, looking at my other add-ons (public or for
personal use) and also those I use of other devs, most of them will be
dead in the water, or could only be ported with serious, serious
limitations. Some add-ons I use already were abandoned, rightfully so
because WebExtensions offer no way forward for those addons, and for now
I fix them locally for me if something breaks (I cannot take over
maintainership and publish them as I lack the time and motivation to do so)
I have no use for crappy webrequest/toolbar button APIs alone. At least
the Adblockers will survive I guess... hurray!


Dismantling the add-on system just because mozilla doesn't like the
maintenance burden all of a sudden?

"B-but we want away from XUL and a lot of XPCOM".
So what? Neither is this going to happen anytime soon realistically, nor
is that any reason not to give add-on developers access to whatever
replaces it.

"B-but add-ons will break less if ever if they are WebExtensions".
Sure, and tons of add-ons should and will go the WebExtensions route.
Doesn't mean you have to fuck over the add-ons not fitting in the
WebExtensions space. There are tons of dedicated add-on developers who
have been dealing with breaking changes in Firefox since it first got
add-ons, for better or for worse. Most of the time, we managed in a
timely fashion.

Even those add-ons which can be reasonably ported need to be ported in
the first place. Somebody will have to do the actual work, which is on
entirely different scale than a "few" "let's move this shit into a
framescript so it works with e10s" fixes.

Frankly, it's add-ons which contributed a lot to Firefox' success, and
it's add-on which eased Firefox bleeding users to Chrome, and once the
add-ons that go beyond WebExtensions stuff are gone, the bleeding will
only increase again.


> To tell the truth, i have been myself very frustrated just a few weeks
> ago, and considered giving up VDH on Firefox. Now i can see a clear
> future (even if there is a lot of development work to be done).

Quite honestly, I'm over the frustrated stage and arrived at the furious
anger stage. And I grow only more hopeless about mozilla as time progresses.

WebExtensions are far off from feature parity, let alone bug parity for
even the Chrome extension APIs, yet announce EOL for new add-ons in 53
and EOL for all add-ons in 57 [0 again]?
What the fuck are they thinking?
Whoever was involved in that decision with actual say: Please do us all
a favor and just step down from any leadership position you might have.
Or better yet, apply for a leadership position in the Google Chrome
team; Firefox can use some help from you eventually ending up
inadvertently sabotaging Chrome sooner than later.

What's even more discouraging is that mozilla will be using their
"signing required" Walled Garden they installed because "reasons, not of
them actually sane or good" that they swore they will not use to fuck
with add-ons[2] - just to do exactly that, and fuck with add-ons,
stopping to sign new non-WE add-ons with the Firefox 53 release.
THANK YOU VERY MUCH! I TOTALLY TRUST EVERYTHING YOU SAY NOW MORE THAN EVER!

Does the Walled Garden help make Firefox more secure? Nope.
Is it abused to force unrelated policy changes instead? Yep!



mozilla has been a huge clusterfuck for years now, not just in the
add-on space; lacking proper (tech) leadership, lacking vision, focusing
on the wrong things at large more often than not, fucking with their
core users for no apparent reason other than "but we have to do
*something* to stay relevant". And even stupid stunts like force
bundling crapware (pocket) isn't too goddamn stupid to do these days.
"1 million mozillians!", yeah, you will certainly achieve this by
alienating everybody on many fronts at once.

I've been part of the mozilla universe for almost one and a half decades
(or almost 15 years in "metric") now. I'm doing DownThemAll! and other
extensions since about a decade now. I've seen tons of fuckups in that
time, and produced a few myself; but that was OK because none of those
were deliberate and we always worked together on fixing things.
Not ever before did I think mozilla is hopelessly fucked at a
fundamental level. But the last one or maybe two years changed that.

I have to admit that I failed to see this for a quite some time,
deluding myself into thinking "it's not that bad", "they'll will do it",
"temporary setback", "they will recover", "I can learn to live with
that"... Tried to rationalize all this away...
But that's ended.

I'm fed up as an add-on developer, I'm fed up as a mozilla advocate, I'm
fed up as somebody who used to help the other add-on devs, I'm fed up as
somebody who contributed an enormous amount of volunteer time directly
in many different ways, I'm fed up as a Firefox user.

In conclusion, let me end with two quotes from[3] (second one quoting
myself)

"It’s fascinating how Mozilla manages to always find the exactly right
words — to make their most avid browser enthusiasts feel absolutely
miserable!"

"I honestly hate you [mozilla] right now."
"Bye"

Nils

PS: If anybody feels the inexplicable urge to reply and wants me to know
about it or even respond, make sure to CC me.


[-1] who is on BCC because publicly posting his email address might be rude.
[0] I'm explicitly not dumping on the team that actually implements the
WebExtensions support and APIs, they seem to be doing a fine job with
the resources they got from mozilla. And I am not opposed to
WebExtensions, quite the opposite. But I am opposed to WebExtensions-only!
[1] Well, unless you're NoScript and get special treatment. Well again,
DTA is probably large enough to beg and get special treatment, but I
don't actually want better treatment than others.
[2] And that's still a large legal gray area; e.g. can mozilla legally
sign add-ons of devs from countries with US sanctions/embargoes
[3]
https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/comment-page-1/#comment-223086