On Sat, Sep 5, 2015 at 12:37 PM, MZMcBride <z...@mzmcbride.com> wrote:
> Amir E. Aharoni wrote:
>>Much more importantly, Flow very much does cover basic talk pages. You can
>>write a title and an OP and get people to reply. This has been working for
>>many months already. This is my definition of "covering basic talk pages".
>>
>>Even more importantly is that you can write a title and an OP and get
>>people to reply ON THEIR PHONES. This is nearly impossible on the classic
>>talk pages; on them you are lucky to even manage to read the existing
>>discussions, and typing a reply requires extra finger-acrobatics. With
>>Flow it's as easy as on Twitter. I do almost no coding for Mobile
>>Frontend and apps, but I'm a kind of a volunteer mobile technologies
>>ambassador in my home wiki, and good mobile support for talk pages is the
>>#1 request that I hear from veteran editors with regards to using
>>Wikipedia on their phones. This is another thing that Flow has been doing
>>for many months already.
>
> I think most of the points you raise here are true of LiquidThreads or
> _any_ prototype of a discussion system. Yes, you get a reply button
> instead of needing ":: ~~~~" wikitext. That's great, I agree, but after
> having watched LiquidThreads rot and then seeing a lot of time, money, and
> effort put into Flow, I'm pretty dissatisfied with the deliverable being
> essentially a very intricate proof-of-concept. I think not getting Flow
> fully deployed to Wikimedia wikis is objectively a large failure to
> deliver. Consequently, it seems most prudent to be asking what went wrong
> and how it will be better next time. The underlying reality is that we
> still need a better on-wiki discussion system and it now looks like
> neither LiquidThreads nor Flow are going to be it.

In addition to this, we still have LiquidThreads (LQT) in production.

I can understand Flow being put into maintenance mode, especially if
temporarily while energy is focused elsewhere, but I believe the main
Flow project should at least include:

1. dumping Flow content into the public dumps (
https://phabricator.wikimedia.org/T89398 ), and

2. decommissioning LiquidThreads on all Wikimedia sites by converting
them to Flow

According to Wikiapiary [1] , there are still seven 'active' WMF sites
using LiquidThreads.

I see LQT is still actively being used on five of them:

https://en.wikinews.org/w/index.php?title=Special:RecentChanges&days=30&from=&namespace=90

https://en.wiktionary.org/w/index.php?title=Special:RecentChanges&days=30&from=&namespace=90

https://pt.wikibooks.org/w/index.php?title=Especial:Mudan%C3%A7as_recentes&days=30&from=&namespace=90

https://fi.wikimedia.org/w/index.php?title=Toiminnot:Tuoreet_muutokset&days=30&from=&namespace=90
(conversion to Flow requested: T104089)

https://se.wikimedia.org/w/index.php?title=Special:Senaste_%C3%A4ndringar&days=30&from=&namespace=90
(conversion to Flow requested: T106302)

But no Thread: activity on two others:
http://hu.wikipedia.org/
(They are trialling Flow? T107301)
http://sv.wikisource.org/

It is also installed on two locked projects: Wikimania 2010, and
Wikimedia Strategic Planning.  Can't they be converted to Flow ?

And it is still installed on https://www.mediawiki.org/ .  Is that
still necessary?

Is the current plan simply "let users request LiquidThreads pages be
converted to Flow"?

Which of the above sites are only using it in user talk?

Have any of the above sites affirmatively decided they do not want to
switch to Flow (yet)?
If so, what are their reasons?

1. 
https://wikiapiary.com/w/index.php?title=Special:Ask&offset=0&limit=20&q=[[Has+extension%3A%3AExtension%3ALiquid+Threads]]&p=format%3Dtable%2Flink%3Dall%2Fheaders%3Dshow%2Fmainlabel%3D-2D%2Fintro%3D-3Cb-3EThis-20extension-20is-20in-20use-20on-20the-20following-20websites%3A-3C-2Fb-3E-3Cbr-20-2F-3E%2Fsearchlabel%3D%E2%80%A6-20further-20results%2Fdefault%3DThis-20extension-20is-20no-20longer-20in-20use-20on-20any-20website.%2Fclass%3Dsortable-20wikitable-20smwtable&po=%3FHas+website%3DWiki+name%0A%3FHas+MediaWiki+version%3DMediaWiki+version%0A%3FHas+extension+version%3DExtension+version%0A&sort=Has+MediaWiki+version&order=descending%2Crand&eq=no

-- 
John Vandenberg

_______________________________________________
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Reply via email to
https://www.mail-archive.com/wikimedia-l@lists.wikimedia.org/msg19029.html
www.mail-archive.com
crawl=CC-MAIN-2022-27
15535
application/http; msgtype=response
sha1:RSJ2MTRUICYQLZOEM2ZLSUYDER3CDGDA
<urn:uuid:075e9eaf-6bd3-4ce5-866e-4e055e36123d>
2022-07-03T14:27:37Z
72.52.77.8
text/html
sha1:Y7QAGKGXEJ5FKK56IS3MKBMJUTONXCCI
<urn:uuid:4dd938fc-7ff6-4dc8-9d0a-ee99de248e1d>
https://www.mail-archive.com/wikimedia-l@lists.wikimedia.org/msg19029.html
response
<urn:uuid:bd612e0b-6dcf-4836-87ec-4b2616caa45d>
isPartOf: CC-MAIN-2022-27
publisher: Common Crawl
description: Wide crawl of the web for June/July 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-134
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.3-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/