Title says it all: https://firrre.com/ They're ZNC instances.
I've signed up and it works as advertised. It took a couple of days for
them to review my application.
It supports a bunch of ZNC modules too ( https://firrre.com/modules/ ),
configurable via the usual znc commands or through a web interface.
Including fancy things like push notifications.
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2015.08. This bundle is compatible with MediaWiki 1.23.x and
MediaWiki 1.24.x releases.
Next MLEB is expected to be released in 3 months. We are trying less
frequent releases due to low number of changes per month in the
included extensions. If there are major changes or important bug
fixes, we will do intermediate release. Please give us your feedback
at [[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]].
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2015.08.tar…
* sha256sum: 21cb43509d1e6da3cadc7e594866215d430e110aea5d04857e5cffd2a69db031
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://phabricator.wikimedia.org/
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Babel ==
* Localisation updates only.
== CleanChanges and LocalisationUpdate ==
* Supports extension registration now.
== CLDR ==
* Fix names and translations for Northern Luri, Southern Luri,
Shawiya, Laki, Jinyu (cjy) and Cham.
== Translate ==
* Special:SearchTranslations has acquired lots of new features, such
as cross language search. To take advantage of all the new features,
you need to reindex the index with "php scripts/ttmserver-export.php
--reindex". You also need to update ruflin/elastica to 2.2.0 or later,
or recent version of CirrusSearch which bundles it.
* Translatewiki.net specific message group descriptions have been removed.
* ApiHardMessage has been removed.
* The hidden, deprecated non-TUX translation view is being phased out
and many non-essential features have been removed.
* Web service queries to machine translation and remote translation
memory services are now done parallel.
* Some improvements to cache handling so that some caches are
regenerated instead of just purged when content changes.
* The appearance of workflow state selector on Special:Translate has
been improved.
* Breaking change: The output format of ApiQueryMessageGroups has
changed regarding to workflow states.
* The code no longer checks for the presence of the long deprecated
"revtag_type" database table. Things like proofread messages might
appear as unproofread. If this is the case, run "php
scripts/migrate-schema2.php"
== UniversalLanguageSelector ==
* ULS will use jQuery.i18n from MediaWiki core if available.
* Updated the default geoiplookup URL.
* ULS supports extension registration now.
* Fonts:
** Added Gothic font.
* Input Methods:
** Add Northern Luri keyboard layout.
** Add Southern Kurdish keyboard layout.
** Add South Azerbaijani keyboard layout.
** Add Arabic keyboard layout for Western Baluchi (bgn) (Only for
MediaWiki > 1.25).
** Improvement in many keyboard layouts.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
Hi,
I have enabled a Gadget on Fa Wikipedia (if you go to
https://fa.wikipedia.org/wiki/Special:Preferences#mw-prefsection-gadgets it
is the second one from the top) which depends on ext.gadgets.morebits (as
defined on https://fa.wikipedia.org/wiki/MediaWiki:Gadgets-definition). It
adds a portlet menu labeled "تذکر" which shows only on user talk pages. The
menu contains a number of links, some of which start with "+".
These "+" links are supposed to open a dialog using morebits. If you use
*debug=true* to bypass ResourceLoader, they work fine (feel free to try on my
talk page <https://fa.wikipedia.org/wiki/User_talk:Huji?debug=true> after
enabling the gadget for your account on Fa WP). However, if you don't
bypass ResourceLoader, the "+" links won't work and an error is thrown
reading "SimpleWindow is not defined" (try on my talk page without
bypassing RL <https://fa.wikipedia.org/wiki/User_talk:Huji>). Note that
SimpleWindow is defined in morebits.js
My questions are as follows:
1) How come it works when you bypass ResourceLoader? Note that nothing else
has changed recently (including the morebits.js code on that Wiki)
2) Is it safe to assume that just by listing ext.gadgets.morebits as a
dependency, morebits will be properly loaded by ResourceLoader?
3) Unless 1 or 2 answers it already: how would I fix this problem and make
the gadget work?
Thanks,
Huji
Hello Folks,
Many apologies for cross-posting. We have got a page with reading team
updates for August [0]. The brief for those is:
[1]. The team is doing more efforts in order better understand user
behaviors and patterns, and has a survey tool in place
[2] There are discussions around possible alternatives for article layout
on mobile
On a side note: If you are interested in helping the apps team understand
what users want, get in touch with me, please. We need more OTRS
volunteers to help with handling users and community questions
As usual, comments and questions feel more at home on the talk page of
their relevant topic than they are on this email thread. :)
Happy Weekend!
Moushira
[0] https://www.mediawiki.org/wiki/Reading/Reading_team_updates_August,_2015
[1]https://www.mediawiki.org/wiki/Extension:QuickSurveys/Documentation
[2] https://www.mediawiki.org/wiki/Talk:Reading/Features/Article_lead_image
After a successful Google Summer of Code, Sumit (@codezee) on irc with
help from Nicolas Raoul of the Wikivoyage editing community and
myself, I am excited to announce that Wikivoyage is now using the
WikidataPageBanner extension [1].
A bit of back story - the Wwikivoyage community built a template so
articles could display banners to increase engagement with their
content. The implementation had a few problems - for instance,
templates do not allow you to ship different styles for smaller
devices or use media queries, nor do they allow you to serve different
images to different browsers. As a result not only did banners not
render well on mobile but they also would result in a large image
download for a reader.
New features include a drop down table of contents, responsive images
and better mobile support. For the purposes of mobile, we have
introduced a focus parameter called `origin` which allows editors to
define which part of the banner shows on a smaller screen.
To take an example https://en.m.wikivoyage.org/wiki/Seattle before and
after pictures of applying the parameter [2] and getting banners to
focus on the space needle:
http://imgur.com/iA1N1RC,K3EvpDi
I'm hoping we can write API's and tools to make this easier for
editors to use and I'm hoping other wikis might adopt this interesting
feature (they are very cool for user pages [3]!! :)).
There's still room for improvement. The banners on mobile can be made
even better, I think, and there has been little design input for the
mobile site so far. There are also issues with srcset support on older
browers, and hard problems to think about. Tasks are open for tracking
this work so please dive in [4].
I welcome any new contributors to help polish it even further by
working on one of those tasks or contributing new tasks. I'll be at
hand to help with code review.
If you have any questions please fire them away and please join me in
congratulating Sumit on his first major contribution to our movement
and building the first mediawiki extension to launch first on
Wikivoyage :-).
Thanks to everyone who has helped advise, review the extension for
deployment and provided input/discussions on Wikivoyage travellers pub
and phabricator.
~ Jon
[1] https://www.mediawiki.org/wiki/Extension:WikidataPageBanner
[2] https://en.m.wikivoyage.org/wiki/Special:MobileDiff/2846318
[3] https://en.wikivoyage.org/wiki/User:Jdlrobson
[4] https://phabricator.wikimedia.org/tag/wikidata-page-banner/board/
Hi,
I remembered how readily "the guys" assumed that any woman there was there
> for more than just networking and learning. I remembered having my butt
> pinched, my breasts "accidentally touched", my questions ignored or laughed
> at. I remember how the buzz of background conversation is always much
> louder when the speaker is a woman than when the speaker is a man.
All of these behaviors fall somewhere on the spectrum from rude to
depraved, but am I correct in thinking that most of them would not actually
be covered by a code of conduct? Ignoring or laughing at someone's
question, for example, is certainly rude, but I can't imagine anyone
getting officially reprimanded for it, unless there's an additional element
of confrontation there. (I don't know if this happened at a talk or during
an outside discussion, but either way I'd think it's the same.) Certainly
neither the Wikimedia code of conduct as currently drafted nor the WMF
Friendly Space Policy cover simple acts of rudeness, even if motivated by
bias.
-Yaron
--
WikiWorks · MediaWiki Consulting · http://wikiworks.com
Hi everybody!
I want to write an extension for the VisualEditor (great work by the way) and I need a little help. I've browsed through various documentation [1-4](and more) and already learned that using RL module 'ext.visualEditor.desktopArticleTarget.init' and 'mw.lib.ve.addPlugin' method is the way to go. Unfortunately my attempts to hook into the user interface by binding on events provided by the components (like 'save' from 've.ui.MWSaveDialog' or 've.init.mw.Target') have not been successful yet. Maybe you could give me a little push into the right direction.
Are there any HowTos or Tutorials for VisualEditor that cover topics like
1. Adding buttons to the toolbar
2. Accessing the data model (e.g. retrieve all set categories from the Parsoid DOM)
3. Extending/replacing a single tool (e.g. the GalleryInspector)
4. Binding on components events (e.g. the 'save' event, to analyze content and maybe abort saving)
Points 1 and 2 get more or less explained by the docs I've found. But 3 and 4 are very unclear to me. Some hints would be appreciated!
[1] https://www.mediawiki.org/wiki/VisualEditor_gadgets#Gadget_-_Registering_VE…
[2] https://en.wikipedia.org/wiki/User:%D7%A2%D7%A8%D7%9F/veReplace.js
[3] https://doc.wikimedia.org/VisualEditor/master
[4] https://www.mediawiki.org/wiki/OOjs_UI/Toolbars
Greetings,
Robert Vogel
Hi,
Is it possible in 2015 to rename Wikimedia domains?
The usual domain name structure for a Wikimedia project is
languageCode.project.org: en.wikipedia.org, it.wikisource.org, etc.
In a few projects the language code in the domain is different from the
actual language code: 'als' is a code for Tosk Albanian, but
als.wikipedia.org is written in Alemanic; 'no' is a code for both Bokmal
Norwegian and Nynorsk Norwegian, but no.wikipedia.org is only Bokmal; and
there are several other examples.
In the past when requests to rename such domains were raised, the usual
replies were along the lines of "it's impossible" or "it's not worth the
technical effort", but I don't know the details.
Is this still correct in 2015?
I would love to get that done, because these inconsistent and non-standard
codes repeatedly cause issues in various languages applications, the
current big one being ContentTranslation.
Thanks!
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore