Pixeldomain

Welcome to Wikidata, Pixeldomain!

Wikidata is a free knowledge base that you can edit! It can be read and edited by humans and machines alike and you can go to any item page now and add to this ever-growing database!

Need some help getting started? Here are some pages you can familiarize yourself with:

• Introduction – An introduction to the project.
• Wikidata tours – Interactive tutorials to show you how Wikidata works.
• Community portal – The portal for community members.
• Contents – The main help page for editing and using the site.
• Project chat – Discussions about the project.
• Tools – A collection of user-developed JavaScript tools to allow for easier completion of some tasks.

If you have any questions, please ask me on my talk page. If you want to try out editing, you can use the sandbox to try. Once again, welcome, and I hope you quickly feel comfortable here, and become an active editor for Wikidata.

Best regards! Liuxinyu970226 (talk) 03:48, 27 July 2016 (UTC)

Previous discussion was archived at User talk:Pixeldomain/Archive 1 on 2016-07-27.

https://twitter.com/MickyLindlar/status/1319313452335308800 - "why are PDF/A profiles & conformance levels linked as hasPart, while PDF/X profiles are linked as hasEdition or translation?"

-Q1547957

-Q1423339

I've changed P31 on a number of items relating to smartphones in order to satisfy certain properties' constraint violations (for the most part I've just re-added smartphone model (Q19723451) where you removed it). If you think there's a better solution feel free to change the statements further.

Thanks for contributing but RAM and storage are different things. Usually devices have much less memory size than storage capacity. I removed memory capacity in iPhone 11 and iPhone 11 Pro because it has only 4 GB memory not 64, 128 or 256.

The English labels and description for volatile random-access memory capacity (P2928) were ambiguous so I have updated them to be clearer that the property is intended to apply to volatile random-access memory (Q67420692) only and not other forms of memory or storage that electronic devices may have. It looks like further work is needed to clarify the various data storage and memory capacity properties that exist and should exist in the future.

You might have some fun with this mix'n'match catalog.

Thanks for the link!

Every response for this survey can help the Wikimedia Foundation improve your experience on the Wikimedia projects. So far, we have heard from just 29% of Wikimedia contributors. The survey is available in various languages and will take between 20 and 40 minutes to be completed. Take the survey now.

If you have already taken the survey, we are sorry you've received this reminder. We have design the survey to make it impossible to identify which users have taken the survey, so we have to send reminders to everyone. If you wish to opt-out of the next reminder or any other survey, send an email through EmailUser feature to WMF Surveys. You can also send any questions you have to this user email. Learn more about this survey on the project page. This survey is hosted by a third-party service and governed by this Wikimedia Foundation privacy statement. Thanks!

WMF Surveys, 01:40, 13 April 2018 (UTC)

(That message in other languages: العربية • ‎bosanski • ‎català • ‎Deutsch • ‎Esperanto • ‎français • ‎עברית • ‎polski • ‎português • ‎português do Brasil • ‎русский • ‎اردو • ‎中文 – ‎translate that message)

Hello!

Like some other community members, you are using Flow.

An increasing number of communities now use Flow or are considering it. Although Flow itself is not scheduled for major development during 2016 fiscal year, the Collaboration Team remains interested in the project and in providing an improved system for structured discussions.

You can help us make decisions about the way forward in this area by sharing your thoughts about Flow — what works, doesn't work or should be improved?

Please fill out this survey (available in multiple languages), which is administered by a third-party service. It will not require an email or your username. See our privacy statement.

Thanks for your ideas and opinions about Flow!

Trizek (WMF), on behalf of the Collaboration team, 11:56, 7 September 2016 (UTC)

Hello! The Wikimedia Foundation is asking for your feedback in a survey. We want to know how well we are supporting your work on and off wiki, and how we can change or improve things in the future.[1] The opinions you share will directly affect the current and future work of the Wikimedia Foundation. You have been randomly selected to take this survey as we would like to hear from your Wikimedia community. To say thank you for your time, we are giving away 20 Wikimedia T-shirts to randomly selected people who take the survey.[2] The survey is available in various languages and will take between 20 and 40 minutes.

Take the survey now!

You can find more information about this project. This survey is hosted by a third-party service and governed by this privacy statement. Please visit our frequently asked questions page to find more information about this survey. If you need additional help, or if you wish to opt-out of future communications about this survey, send an email to surveys@wikimedia.org.

Thank you! --EGalvez (WMF) (talk) 20:36, 13 January 2017 (UTC)

1. ↑ This survey is primarily meant to get feedback on the Wikimedia Foundation's current work, not long-term strategy.
2. ↑ Legal stuff: No purchase necessary. Must be the age of majority to participate. Sponsored by the Wikimedia Foundation located at 149 New Montgomery, San Francisco, CA, USA, 94105. Ends January 31, 2017. Void where prohibited. Click here for contest rules.

(Sorry to write in Engilsh)

Hello! This is a final reminder that the Wikimedia Foundation survey will close on 28 February, 2017 (23:59 UTC). The survey is available in various languages and will take between 20 and 40 minutes. Take the survey now.

If you already took the survey - thank you! We won't bother you again.

About this survey: You can find more information about this project here or you can read the frequently asked questions. This survey is hosted by a third-party service and governed by this privacy statement. If you need additional help, or if you wish to opt-out of future communications about this survey, send an email through EmailUser function to User:EGalvez (WMF) or surveys@wikimedia.org. About the Wikimedia Foundation: The Wikimedia Foundation supports you by working on the software and technology to keep the sites fast, secure, and accessible, as well as supports Wikimedia programs and initiatives to expand access and support free knowledge globally. Thank you! --EGalvez (WMF) (talk) 08:19, 24 February 2017 (UTC)

Referring to [https://www.wikidata.org/w/index.php?title=Property_talk:P172&diff=prev&oldid=568660304 this], changes to a sensible property should have been discussed first. Please refrain from making edits like [https://www.wikidata.org/w/index.php?title=Q419&diff=prev&oldid=568661363 this one I had to revert] until the matter is solved. Thank you!

Thanks for your feedback. I have made the mapping for space complexity in Wikidata:WikiProject_Informatics/Data_Structure. Unlike algorithms, there are more than one operation (insert, search, find minimum, delete etc..) and current approach where we have only 3 time complexity cases (average, best and worst) does not fit. My personal opinion is to add qualifiers to these three cases making use of 'of' for possible operations. What do you suggest?

I would suggest use of qualifiers as well. So for example, average insert performance complexity becomes "average performance complexity" with value of a math equation. A qualifier "of" (or something better suited?) with value "insert into data structure" could then be added.