Yellowcard added a comment.I strongly support @Srittau's comment. This is still an extremely annoying bug and should be fixed with high priority. There are plenty of exact integers and the guessed precision of +/-1 makes the data wrong. I cannot understand why this is not fixed.TASK DETAILhttps
re has to be a possibility to report errors in
"semi-locked statements" (e.g. on a central page).
Locking whole items with infinite length, though, is rarely a good idea,
I think there is no dissent about that.
Cheers
Yellowcard
signature.asc
Description: OpenPGP d
would make them much less risky to obtain them and use them directly in
Wikipedia. What would be the disadvantage of this, given that slightly
experienced users can still edit them and the lock is only a protection
against anonymous vandalism?
Yellowcard
signature.asc
Description:
erefore be able to edit also
those "locked" statements.
Such proactive limitations are widely used in various Wikimedia
projects, thinking of flagged revisions and the possibility of uploading
files for example. It wouldn't contradict the wik
necessary
due to acute vandalism and should stay a privilege of administrators.
Yellowcard
[1] https://de.wikipedia.org/wiki/Didier_Drogba
signature.asc
Description: OpenPGP digital signature
___
Wikidata mailing list
Wikidata@lists.wikimedia
Herald added a subscriber: TerraCodes.
TASK DETAIL
https://phabricator.wikimedia.org/T45578
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Yellowcard
Cc: Yellowcard, TerraCodes, Aklapper, eranroz, Sitic, Wikidata-bugs, aude,
Lydia_Pintscher
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Listeria has been down since at least Monday. I e-mailed Magnus
because of that yesterday.
Cheers
Yellowcard
Emilio J. RodrÃguez-Posada schrieb:
> Listeria is down for me https://tools.wmflabs.org/listeria Not sure
> if related.
>
> 2
Yellowcard added a comment.
@kaldari: I understand the argumentation, but it doesn't convince me. Your
statements in the linked bug seem very reasoned to me. We agree that
information about uncertainty is very important, but for each data we have to
//know// the amount of uncertainty
Yellowcard added a comment.
@kaldari: There's nothing against uncertainty, but the default uncertainty for
values that don't have any. I'm especially talking about counting values
without any unit.
For what I understand, unit conversation should also be possible without known
uncertainty
Yellowcard added a subscriber: Yellowcard.
Yellowcard added a comment.
Having a default in general is not reasonable.
If there is a sourced uncertainty, the input has to include exactly this
uncertainty, not a default one.
It here is no sourced uncertainty, guessing one is simply wrong
Yellowcard added a subscriber: Yellowcard.
TASK DETAIL
https://phabricator.wikimedia.org/T67626
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Yellowcard
Cc: Yellowcard, waldyrious, jeremyb, Ricordisamoa, Aklapper, Laddo,
Bugreporter, -jem
11 matches
Mail list logo