Huggle

huggle@lists.wikimedia.org

124 discussions

21 Jul '17

According to < https://lists.wikimedia.org/pipermail/huggle/2017-July/000173.html> the original message by Declan Martin has not been delivered to the list, possibly due to the known yahoo issues with Wikimedia mailing lists. I am copying below my reply and his original message below so those looking at this thread can know what this is about. ---------- Forwarded message begins ---------- From: MarcoAurelio <strigiwm(a)gmail.com> Date: 2017-07-20 0:17 GMT+02:00 Subject: Re: [Huggle] Login issue To: List for huggle developers and support <huggle(a)lists.wikimedia.org> Hmpf, it seems that on MacOs it is possible to use OAuth as oposed to BotPasswords on Windows? In any case, the working is similar. I am not a huggle dev but an user. First that comes to my mind is that you did not authorize huggle to use rollback on enwiki. If you're using OAuth/BotPasswords be sure to select too a group of permissions that allows the application to use rollback. If you already have done that, be also sure that you've Special:Mypage/huggle.css and Special:Mypage/huggle3.css configured correctly (enable:true). If nothing helps, hopefully a more experienced user will reply or you can create a ticket in the Huggle project of the phabricator.wikimedia.org issue tracker. I hope that your issue gets resolved soon. Best regards, M.A. El El lun, 17 jul 2017 a las 19:43, Declan Martin <declanmatthew(a)yahoo.com> escribió: > Hi, > I’m getting the "Login failed on enwiki: You don't have rollback > permissions on this project.” message when I attempt do login. I do have > rollback permission and have used it many times. I tried getting help on > IRC, but no one was online. > > Cheers, > Dmartin969 > > _______________________________________________ > Huggle mailing list > Huggle(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/huggle

1 0

20 Jul '17

Hi, I’m getting the "Login failed on enwiki: You don't have rollback permissions on this project.” message when I attempt do login. I do have rollback permission and have used it many times. I tried getting help on IRC, but no one was online. Cheers, Dmartin969

2 1

Huggle 3.2.0 released
by Petr Bena 12 Jul '17

12 Jul '17

Hi all, I would like to inform you that new version of Huggle was released. We are still lacking builds for Linux and MacOS, but I hope that will be fixed soon. This version has a massive diff of changes compared to last one and it also took pretty long for us to release it (due to lack of active devs). I hope that we will be faster in future when it comes to releases, hopefully if I manage to automate packaging a bit, it shouldn't be so much of a problem. Most significant change and reason why it's minor version was incremented is support for web engine based on Chromium, which also allowed us to switch to newer Qt 5.7. So all Windows builds are now running on newer Qt and use Chromium instead of WebKit. Full changelog can be seen here: https://github.com/huggle/huggle3-qt-lx/compare/3.1.22...3.2.0 Thank you

1 0

Re: [Huggle] EventStreams launch and RCStream deprecation
by Andrew Otto 10 Jul '17

10 Jul '17

Hi all, This is just a friendly reminder that we plan to turn off the RCStream service after July 7th. We’re tracking as best we can the progress of porting clients over at https://phabricator.wikimedia.org/T156919. But, we can only help with what we know about. If you’ve got something still running on RCStream that hasn’t yet ported, let us know, and/or switch soon! Thanks! -Andrew Otto On Wed, Feb 8, 2017 at 9:28 AM, Andrew Otto <otto(a)wikimedia.org> wrote: > Hi everyone! > > Wikimedia is releasing a new service today: EventStreams > <https://wikitech.wikimedia.org/wiki/EventStreams>. This service allows > us to publish arbitrary streams of JSON event data to the public. > Initially, the only stream available will be good ol’ RecentChanges > <https://www.mediawiki.org/wiki/Manual:RCFeed>. This event stream > overlaps functionality already provided by irc.wikimedia.org and RCStream > <https://wikitech.wikimedia.org/wiki/RCStream>. However, this new > service has advantages over these (now deprecated) services. > > > 1. > > We can expose more than just RecentChanges. > 2. > > Events are delivered over streaming HTTP (chunked transfer) instead of > IRC or socket.io. This requires less client side code and fewer > special routing cases on the server side. > 3. > > Streams can be resumed from the past. By using EventSource, a > disconnected client will automatically resume the stream from where it left > off, as long as it resumes within one week. In the future, we would like > to allow users to specify historical timestamps from which they would like > to begin consuming, if this proves safe and tractable. > > > I did say deprecated! Okay okay, we may never be able to fully deprecate > irc.wikimedia.org. It’s used by too many (probably sentient by now) bots > out there. We do plan to obsolete RCStream, and to turn it off in a > reasonable amount of time. The deadline iiiiiis July 7th, 2017. All > services that rely on RCStream should migrate to the HTTP based > EventStreams service by this date. We are committed to assisting you in > this transition, so let us know how we can help. > > Unfortunately, unlike RCStream, EventStreams does not have server side > event filtering (e.g. by wiki) quite yet. How and if this should be done > is still under discussion <https://phabricator.wikimedia.org/T152731>. > > The RecentChanges data you are used to remains the same, and is available > at https://stream.wikimedia.org/v2/stream/recentchange. However, we may > have something different for you, if you find it useful. We have been > internally producing new Mediawiki specific events > <https://github.com/wikimedia/mediawiki-event-schemas/tree/master/jsonschema…> > for a while now, and could expose these via EventStreams as well. > > Take a look at these events, and tell us what you think. Would you find > them useful? How would you like to subscribe to them? Individually as > separate streams, or would you like to be able to compose multiple event > types into a single stream via an API? These things are all possible. > > I asked for a lot of feedback in the above paragraphs. Let’s try and > centralize this discussion over on the mediawiki.org EventStreams talk > page <https://www.mediawiki.org/wiki/Talk:EventStreams>. In summary, > the questions are: > > > - > > What RCStream clients do you maintain, and how can we help you migrate > to EventStreams? > <https://www.mediawiki.org/wiki/Topic:Tkjkee2j684hkwc9> > - > > Is server side filtering, by wiki or arbitrary event field, useful to > you? <https://www.mediawiki.org/wiki/Topic:Tkjkabtyakpm967t> > - > > Would you like to consume streams other than RecentChanges? > <https://www.mediawiki.org/wiki/Topic:Tkjk4ezxb4u01a61> (Currently > available events are described here > <https://github.com/wikimedia/mediawiki-event-schemas/tree/master/jsonschema…> > .) > > > > Thanks! > - Andrew Otto > > >

2 2

Help needed!
by Petr Bena 31 Mar '17

31 Mar '17

Hello, There is a huge amount of people listed on https://meta.wikimedia.org/wiki/Huggle/Members yet it seems that nobody is really active very much. I am myself extremely busy lately and barely find any time to contribute which results in massive amount of tickets waiting to get solved: https://phabricator.wikimedia.org/tag/huggle/?order=priority You don't have to understand C++ in order to solve each of them, there are couple of tickets that only require knowledge of Huggle, such as these where someone need to enable it on some wiki. It would be epic if someone could help me get these tickets resolved. Thanks

2 2

New Contributor-Introduction
by perside rosalie 05 Mar '17

05 Mar '17

Hello, I am Perside Rosalie a computer software engineering student at university of buea-Cameroon. I wish to contribute to the huggle app and maybe participate in GSoC program with the project Please I will apreciate any getting started tips or links. Thank you

1 0

Fwd: EventStreams launch and RCStream deprecation
by Andrew Otto 26 Feb '17

26 Feb '17

Hi everyone! Wikimedia is releasing a new service: EventStreams <https://wikitech.wikimedia.org/wiki/EventStreams>[1]. This service allows us to publish arbitrary streams of JSON event data to the public. (Psssst: we’re looking for cool new uses <https://www.mediawiki.org/wiki/EventStreams/Blog_-_Call_For_Entries>[2] to put on an upcoming blog post.) Initially, the only stream available will be good ol’ RecentChanges <https://www.mediawiki.org/wiki/Manual:RCFeed>. This event stream overlaps functionality already provided by irc.wikimedia.org and RCStream <https://wikitech.wikimedia.org/wiki/RCStream>. However, this new service has advantages over these (now deprecated) services. 1. We can expose more than just RecentChanges. 2. Events are delivered over streaming HTTP (chunked transfer) instead of IRC or socket.io. This requires less client side code and fewer special routing cases on the server side. 3. Streams can be resumed from the past. By using EventSource, a disconnected client will automatically resume the stream from where it left off, as long as it resumes within one week. In the future, we would like to allow users to specify historical timestamps from which they would like to begin consuming, if this proves safe and tractable. I did say deprecated! Okay okay, we may never be able to fully deprecate irc.wikimedia.org. It’s used by too many (probably sentient by now) bots out there. We do plan to obsolete RCStream, and to turn it off in a reasonable amount of time. The deadline iiiiiis July 7th, 2017. All services that rely on RCStream should migrate to the HTTP based EventStreams service by this date. We are committed to assisting you in this transition, so let us know how we can help. Unfortunately, unlike RCStream, EventStreams does not have server side event filtering (e.g. by wiki) quite yet. How and if this should be done is still under discussion <https://phabricator.wikimedia.org/T152731>. The RecentChanges data you are used to remains the same, and is available at https://stream.wikimedia.org/v2/stream/recentchange. However, we may have something different for you, if you find it useful. We have been internally producing new Mediawiki specific events <https://github.com/wikimedia/mediawiki-event-schemas/tree/master/jsonschema…> [3] for a while now, and could expose these via EventStreams as well. Take a look at these events, and tell us what you think. Would you find them useful? How would you like to subscribe to them? Individually as separate streams, or would you like to be able to compose multiple event types into a single stream via an API? These things are all possible. I asked for a lot of feedback in the above paragraphs. Let’s try and centralize this discussion over on the mediawiki.org EventStreams talk page <https://www.mediawiki.org/wiki/Talk:EventStreams>[4]. In summary, the questions are: - What RCStream clients do you maintain, and how can we help you migrate to EventStreams? <https://www.mediawiki.org/wiki/Topic:Tkjkee2j684hkwc9> - Is server side filtering, by wiki or arbitrary event field, useful to you? <https://www.mediawiki.org/wiki/Topic:Tkjkabtyakpm967t> - Would you like to consume streams other than RecentChanges? <https://www.mediawiki.org/wiki/Topic:Tkjk4ezxb4u01a61> (Currently available events are described the event-schemas repository <https://github.com/wikimedia/mediawiki-event-schemas/tree/master/jsonschema…> .) Thanks! - Andrew Otto [1] https://wikitech.wikimedia.org/wiki/EventStreams [2] https://www.mediawiki.org/wiki/EventStreams/Blog_-_Call_For_Entries [3] https://github.com/wikimedia/mediawiki-event-schemas/tree/master/jsonschema… [4] https://www.mediawiki.org/wiki/Talk:EventStreams

3 2

Code-In - tasks and mentors needed
by Petr Bena 04 Nov '16

04 Nov '16

Hi folks, Wikimedia has applied for taking part in Google Code-in 2016 (a contest for 13-17 year old students for small tasks taking max. a few hours). Tasks are welcome in the following areas: code, outreach/research, documentation/training, quality assurance, user interface/design. If you have any idea for a small task for a student that could enhance Huggle, let me know. Do that as well in case you would like to be a mentor and help supervise their work. Read more at https://www.mediawiki.org/wiki/Google_Code-in_2016

1 0

Huggle 3.2.0 based on Chromium instead of WebKit
by Petr Bena 21 Oct '16

21 Oct '16

Hi, I would like to announce that as of Huggle 3.2.0 we will support Qt WebEngine which is based on Chromium (libre version of Chrome's engine) instead of Apple's WebKit. The reason is that Qt officially dropped support for WebKit now and that makes it impossible to build Huggle 3.1.x with anything newer than 5.4. Because many vendors, including Canonical are now shipping only newer Qt (Qt 5.7) it's impossible to build huggle on some OS'es like Ubuntu and we had to use older Qt builds even for other OSes. The support for WebKit will however stay implemented in Huggle and it will be default backed for now. Packages for MS Windows and MacOS will however be shipped with Chromium backend as of next version (we need to do some beta testing). If you want to build your own Huggle version with chromium backend you can do that by running ./configure with --web-engine option. This is a major change in huggle's core which may have big effect on memory usage and performance so some testing is going to start soon (I will publish some beta versions). Also rendering of some pages may start looking different (they will probably look more like if you opened them in Chrome instead of Safari). If you are interested in the code, it's not yet merged: https://github.com/huggle/huggle3-qt-lx/tree/web_engine There are some known bugs, clicking a link on a web page will open the link within Huggle, which is wrong (Huggle won't even notice that thinking you are still viewing a diff). Fetching source code of web page for viewing by user doesn't work yet as well, but isn't really important for huggle. Let me know if you wanted more info

1 0

The Wikimedia Developer Summit wants YOU!
by Srishti Sethi 19 Oct '16

19 Oct '16

Hello! The Wikimedia Developer Summit <https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit> is the annual meeting to push the evolution of MediaWiki and other technologies supporting the Wikimedia movement. The next edition will be held in San Francisco on January 9-11, 2017. We welcome all Wikimedia technical contributors, third party developers, and users of MediaWiki and the Wikimedia APIs. We specifically want to increase the participation of volunteer developers and other contributors dealing with extensions, apps, tools, bots, gadgets, and templates. Important deadlines: - Monday, October 24: This is the last day to request travel sponsorship. Applying takes less than five minutes. - Monday, October 31: This is the last day to propose an activity. Bring the topics you care about! Subscribe to weekly updates: https://www.mediawiki.org/ wiki/Topic:Td5wfd70vptn8eu4 Please feel free to forward this email to anyone who might be interested in attending! Thanks, Srishti -- Srishti Sethi ssethi(a)wikimedia.org

1 0

← Newer
1
2
3
4
5
6
7
...
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

Huggle