abbe98

I wonder how much of Mozilla budget is actually spent on Firefox.

Wikimedia Foundation had a revenue of $157 million in 2021 and >550 staff and contractors.

The vast majority of Swedish and Finish forests are managed for logging. All of the tree cover loss on this map in my area(except for some very recent that has just been logged/replanted) is today young forest which will be logged again in a few decades...

If one is looking for public domain versions with the correct proportions, Wikimedia Commons might have what you need:

https://commons.wikimedia.org/wiki/Sovereign-state_flags

MediaWiki actually got policies to ensure breaking changes to the DOM isn't introduced.

Did it fail or did it just turn out different from what many imagined?

I mean RDF is alive and well and Schema.org is widely adopted.

Firefox fetches URLs hashes from Google and then checks the URLs you visit against that list. Only if there is a match Firefox will send the hash(not the URL) to Google to verify that there isn't a hash conflict.

I would donate to Mozilla if >50% went to FF development. Considering that I haven't seen prompts to donate in Firefox(for that last years at least), in the release notes, etc. It seems like a missed opportunity, both for FF development and for other Mozilla projects.

It's a common wish here at HN that one would like to donate directly to Firefox development. Is there a legal reason that Mozilla can't do this considering their setup having the Mozilla Corporation run Firefox development? What else could their reasons be for at least not experimenting with the option?

In 2019 the salary for Wikimedia Foundation's CEO was $387,770.

https://meta.m.wikimedia.org/wiki/Wikimedia_Foundation_salar...

The title does not give this enough credit. I was incredibly impressed by its speed(I'm used to Hound[1] at work) it felt almost instant.

[1]: https://github.com/hound-search/hound

I have tried for a while to find a web-host which can report an estimation of my environmental impact based on usage. I have not been successful and the project for which I needed this we had to go with self-hosting(which likely is less sustainable) and having to calculate this based on information from our ISP/electricity companies.

Lot's of hosting companies including all the large clouds have marketing pages about their sustainability efforts but only an obscure, expense, and inaccessible Azure service can provide CO2 pollution estimations from ones usage...

You could donate to a local Wikimedia chapter or a thematic organization, they are doing a lot of great work in various areas and many of them are small enough for one to have an impact.

https://meta.wikimedia.org/wiki/Wikimedia_chapters https://meta.wikimedia.org/wiki/Wikimedia_thematic_organizat...

This could work for cookies but how would it work for other types of tracking. GDPR is not about cookies per se but about tracking.

I always had a good experience with Phabricator, especially its customization/dashboards.

Wikimedia still uses it[1].

[1]: https://phabricator.wikimedia.org/

What are the benefits of using the no-js approach over a style or link tag inside of a noscript element? Other than that all CSS can be contained in the same file.

Not limited to art but for cultural heritage collections in general.

There is the OpenGLAM Survey, a list of Galleres, Libraries, Archives, and Museum sharing their collections under open licenses: https://docs.google.com/spreadsheets/d/1yc8z0z7XdhVKvhTbD2_z...

Then there are also aggregators like dp.la, cultural.jp, digitalnz.org, europeana.eu etc that might also be of interest.

While Google already have a pipeline in place the bottleneck of that pipeline is on the Wikimedia end of things, this project addresses that. No more scraping and data dumps when they can stream changes over gRPC. WMF didn't build this without consultation with these big companies.

Google and co will essentially pay for the SLA, free access will be available through Wikimedia Cloud Services and I'm sure that the team is investigating how to make the API available to the wider public.

I would imagine authentication being done through Wikimedia's existing LDAP or Mediawiki solution and I hope that features that already exists in Phabricator(such as snippets) will be disabled.

WMF is only replacing Gerrit for now, Phabricator will continue to be the issue tracker.

Is this mainly a concern for the Gitlab issue tracker? Wikimedia will continue to use Phabricator for issue tracking, Gitlab CE will only be used for CI and code review/hosting...

Sending a short email is estimated to release 4g CO2:

https://phys.org/news/2015-11-carbon-footprint-email.html

Wikidata has a great SPARQL editor with plenty of examples and built in visualizations:

https://query.wikidata.org/

> Right now, if you want to become an editor of Wikipedia, you simply need to have a passing familiarity with wikitext

Wikipedia have had an WYSIWYG editor for years.

> if you want to become an editor of Abstract Wikipedia, you'd need to have an in-depth knowledge of lambda calculus, and possibly a Ph.D. in linguistics

No this is not how it's intended. First the data itself is supposed to be from Wikidata which is super simple to edit. Secondly surly they can come up with an UI for the other parts.

Exactly this. Currently MediaWiki and many of its extensions have its interactive parts (editor/maps, etc) written in jQuery and the in-house developed framework OOUI. These are the pieces which might slowly be replaced by Vue.

Hopefully this will also make it easier for new contributors to get started with MediaWiki development.

"tiger" in Swedish means both tiger and "being quiet".

That Sweden were neutral during the war is a common saying that's slowly going away among Swedes. Sweden were never neutral, flexible but not neutral.

Many Swedes did great things such as taking in Jewish refugees. The Swedish government however shifted sides as the war prospects changed.

In addition to being printed on posters and similar public media it were also printed on letter paper, suitcases and envelopes.

Location: Sweden

Remote: no

Willing to relocate: yes

Technologies: Python, JavaScript, Vue, Java, PHP, HTML, CSS

Résumé/CV: on a case to case basis

Email: albin(dot]post{at)gmail.com

Currently tech lead/business developer at an government agency focusing on R&D (for the last 2 1/5 years). Extra passionate about maps, web-accessibility, and linked data. Looking for a job preferably outside of Scandinavia related climate or journalism.

I'm guessing OSM is only used for routing not for actual navigation and that they filter out clear vandalism using edit criterias and ingestion delays.