Hello
I'm unsure if my messages are being delivered. Can someone confirm?
It's about the truncation of the description ("..."). It would be better
to not have these truncated, lile before.
Hi all,
Hope you are safe and well. We've just released v2.13 of the Commons
Android app[1] to beta, which includes:
- A new media details UI, which includes the ability to zoom and pan
around images
- When the user uploads a picture with a geotag, the app will check for
Nearby places that need photos around that location, and one is found, it
will ask the user "Is this a picture of Place X?"
- Modifications to Nearby filters based on user feedback
- Bug and crash fixes for stuff that got broken by the codebase overhaul
Our next release will likely contain structured data integration, bookmarks
for the Nearby map, and a couple of other new features.
Thank you all for your support and encouragement - feedback, bug reports,
and suggestions are always welcome in our GitHub repo[2]. :)
[1]: https://play.google.com/store/apps/details?id=fr.free.nrw.commons
[2]: https://github.com/commons-app/apps-android-commons/issues/
Best regards,
Josephine / @misaochan (Commons app project lead)
Hi
There's something new with the "read more, 3 articles" section at the end
of each article.
First, the 3 articles change on each refresh. Before, it was more static
(better to me).
Second, the short description is not complete for the 3 articles. It is
cut, with then "...". I do not want to click the article to go see the full
description (this will refresh the page with 3 different articles).
So, I want more static "read more 3 articles", with full descriptions, not
truncated.
The web version does not have this new behavior.
Is it possible to back to previous version for the mobile app?
Thanks
Hi all,
We (the Commons app team) are hoping to release a Commons iOS app this
year! :) We have received quite a few requests for it, so we have included
it in our Project Grant proposal:
https://meta.wikimedia.org/wiki/Grants:Project/Commons_app/Commons_app_Andr…
.
Additionally, we are proposing a few new features for the Android app, and
stability/code quality improvements.
If this sounds useful or interesting to you, please do take a look at our
proposal, and endorse it if you see fit. Or if you have any questions or
concerns, please feel free to email me or post in the discussion page.
Thank you so much for all of your encouragement and support. We really
appreciate it!
Best regards,
Josephine / @misaochan (Commons app project lead)
Hi all,
We've just released v2.12 of the Commons app to production on the Play
Store[1]! :) This contains the legacy code overhaul that we've been working
on for the better part of the last year, in order to reduce
difficult-to-debug issues and create a better foundation for stability and
further improvements.
One of the goals in this overhaul is to prevent the issue of failed
uploads which has plagued our users sporadically for years. According to
our beta testers' feedback, this issue has been solved - however, if you
are using v2.12 (can be seen in About page) on a *fresh install* and you
are still experiencing failed uploads, please do let us know so we can take
a look at it. Also, as this version contains the most lines of code changed
compared to any of our other versions, it is possible that there may be a
few teething issues that we are as of yet unaware about, but we will try to
fix any reported issues ASAP.
Also, we have a new feature: Filters for place types and states in Nearby
Places! With this feature, you should be able to filter for (or filter out)
specific types of places that need photos, and also filter out places that
are on Wikidata but don't "exist" anymore.
Thank you all for your support and patience. :)
Best regards,
Josephine / @misaochan (Commons app project maintainer)
[1] https://play.google.com/store/apps/details?id=fr.free.nrw.commons
Hello everyone,
As of this week, the Readers Web team has expanded the deployment of a
small set of features from the mobile "advanced mode" users to all
logged-in users. All logged-in users will now have access to article and
talk tabs, as well as direct access to history pages.
We hope that these changes will allow new contributors to access these
parts of the interface with more ease. For more advanced contributors, we
do recommend using the "advanced mode", which includes the above features
and more!
Thank you!
Olga
--
*Olga Vasileva* // Reading Product Manager // Web
https://wikimediafoundation.org/
*Imagine a world in which every single human being can freely share in
the sum of all knowledge. That's our commitment. Donate
<http://donate.wikimedia.org/>. *
Hi everyone,
*tl;dr: We'll be stripping all content contained inside brackets from the
first sentence of articles in the Wikipedia app.*
The Mobile Apps Team is focussed on making the app a beautiful and engaging
reader experience, and trying to support use cases like wanting to look
something up quickly to find what it is. Unfortunately, there are several
aspects of Wikipedia at present that are actively detrimental to that goal.
One example of this are the lead sentences.
As mentioned in the other thread on this matter
<https://lists.wikimedia.org/pipermail/mobile-l/2015-March/008715.html>,
lead sentences are poorly formatted and contain information that is
detrimental to quickly looking up a topic. The team did a quick audit
<https://docs.google.com/a/wikimedia.org/spreadsheets/d/1BJ7uDgzO8IJT0M3UM2q…>
of
the information available inside brackets in the first sentences, and
typically it is pronunciation information which is probably better placed
in the infobox rather than breaking up the first sentence. The other
problem is that this information was typically inserted and previewed on a
platform where space is not at a premium, and that calculation is different
on mobile devices.
In order to better serve the quick lookup use case, the team has reached
the decision to strip anything inside brackets in the first sentence of
articles in the Wikipedia app.
Stripping content is not a decision to be made lightly. People took the
time to write it, and that should be respected. We realise this is
controversial. That said, it's the opinion of the team that the problem is
pretty clear: this content is not optimised for users quickly looking
things up on mobile devices at all, and will take a long time to solve
through alternative means. A quicker solution is required.
The screenshots below are mockups of the before and after of the change.
These are not final, I just put them together quickly to illustrate what
I'm talking about.
- Before: http://i.imgur.com/VwKerbv.jpg
- After: http://i.imgur.com/2A5PLmy.jpg
If you have any questions, let me know.
Thanks,
Dan
--
Dan Garry
Associate Product Manager, Mobile Apps
Wikimedia Foundation
Hello,
We have started using the wikimedia-android-data-client library(
https://github.com/wikimedia/wikimedia-android-data-client) to make
mediawiki api calls in the Commons Android app, replacing the legacy
library that we were using previously. Most of the authenticated calls
(i.e. login, upload, nomination for deletion, thank, notifications etc)
made to Commons wiki are working with the new library, but we are stuck
with a cross-wiki call to Wikidata. We are trying to call
`Service:wbcreateclaim` to create a claim on Wikidata but the call is
failing.
We have posted relevant http logs at
https://github.com/wikimedia/wikimedia-android-data-client/issues/21#issue-…
We would greatly appreciate it if could take a look at the logs and suggest
what we might be doing wrong. Is it because of some issue with cookies?
Because as far as we can see, as expected we are sending the params in POST
request body with application/x-www-form-urlencoded.
Relevant code:
https://github.com/commons-app/apps-android-commons/blob/backend-overhaul/a…
Relevant method call: service.postCreateClaim(entityId, snaktype, property,
value, "en", csrfTokenClient getTokenBlocking())
Thank you so much!
Best regards,
Josephine
