[ { "Id": "43", "CreationDate": "2016-12-06T22:23:33.217", "Body": "
I want to provide some basic reminders regarding tags. As many of you will know from the other SE sites you participate in, tags are not on the top of the pile functionality wise in the SE sites. However if we keep it a sensible taxonomy from the start we have a good chance to make it better.
\n\nLet me start out with the obvious.
\n\nLet's do it right from the start.
\n", "Title": "Keeping tags clean from the start", "Tags": "|discussion|tags|", "Answer": "In some other SE's I frequent, a good rule of thumb when referencing a language-specific tool is to drop the .py
and .js
where they aren't necessary. Also making proper use of hyphens (-
) will save a lot of formatting headaches down the line.
Particularly for IoT builders and developers, it might be better to simply use the name of the formal language they're using and not specifically the tools within those languages. Tool-specific questions are best asked elsewhere anyway.
\n" }, { "Id": "44", "CreationDate": "2016-12-06T23:31:14.953", "Body": "smartthings has been created and I get an annoying warning when trying to change it to smart-things. Generally all multi-word tags should be hyphenated. Can we please change the tag name.
\n\nSince it is a product name / trademark we should likely have one called samsung-smartthings too. We already have one question (Safety of a smart switch on a fireplace) that is tagged with it without disclosing any Samsung specifics in the question.
\n\nEdit: Someone changed it to samsung-smartthings.
\n", "Title": "Smart-Things vs Smartthings", "Tags": "|discussion|status-completed|tags|", "Answer": "SmartThings is a proper noun, not a concept. It's spelled as a single word.
\n\nAs the brand is getting confused with the concept, I've suggested an edit to change the tag to samsung-smartthings.
\n\n\u201cSmart things\u201d as a concept is far too vague to be a valid tag.
\n" }, { "Id": "50", "CreationDate": "2016-12-07T07:00:24.163", "Body": "Finally we've got a chance to have a site for this long-standing out of scope topic! Thanks guys!
\n\nI would like to propose the creation of a \"philips-hue\" tag. While it's a very specific vendor-related tag, there are many Hug devices in the world, so probably many visitors will benefit from it.
\n", "Title": "I would like to propose a tag for Philips Hue", "Tags": "|discussion|status-completed|tags|", "Answer": "The only way to create a tag is to apply it to a question, either when initially posting the question or by editing the question. Tags are not created preemptively, and conversely tags are deleted automatically (after a small delay) if they are removed from every question.
\n\nSo if you think that a question should have the tag philips-hue, then add the tag to the question. And if there's no applicable question, then we don't need the tag (yet).
\n\nThere's no need to open a meta discussion for every tag, only when there's some doubt about the usefulness, scope or name of the tag.
\n" }, { "Id": "55", "CreationDate": "2016-12-07T08:49:23.603", "Body": "While wireless and Wi-Fi do not mean the same (one could reasonably consider wireless as a hypernym of Wi-Fi), they are often used as synonyms. This poses a certain problem for our emerging taxonomy.
\n\nEither we edit posts tagged with either with prejudice and make sure the tag wifi is only used for 802.11 related questions or we create a specific 802.11 tag and synonymize wifi into wireless.
\n\nI'd prefer the second option for two reasons. We would not need to edit every post where someone uses WiFi as synonym for anything wireless and falling back on a hypernym never makes the tagging incorrect. Secondly, a specific 802.11 tag will only be used by people who actually thought about the technology and want to focus on that aspect.
\n\nThoughts?
\n", "Title": "Wi-Fi vs. Wireless Tags", "Tags": "|discussion|tags|", "Answer": "WiFi is basically a technology for Wireless LAN based 802.11 standards so it is a subset of wireless.
\n\n\n\n\nEither we edit posts tagged with either with prejudice and make sure\n the tag wifi is only used for 802.11 related questions
\n
If the user tags a question with wireless which is basically wifi specific then I suppose it's fine there is no need to do any extra work, if we want to tag it specifically we can edit it to include wifi. I presume not many
users know of 802.11
or 802.11x
specifications,so 802.11 posts will be less, here we can synomize
802.11, wi-fi to wifi.
\n\n\nor we create a specific 802.11 tag and synonymize wifi into wireless
\n
Synomizing wifi into wireless is not considered
apt in my opinion as making so, one cannot specifially
look for wifi
related questions, instead they get all wireless related posts which contains all other wireless technologies.
So there is this initiative about Keeping tags clean from start. I think this includes adding tag descriptions and excerpts as soon as possible. There will be tags, there are tags which are already presented on other SE site.
\n\nSo in what circumstances should someone copy edit this tag information to save effort by avoiding the redefinition of a tag?
\n\nFor example:
\n\nMore example tags in question could be bluetooth, wifi and so on.
\n", "Title": "When is it acceptable to copy edit a tag wiki excerpt and description from other SE site?", "Tags": "|discussion|tags|", "Answer": "There are two aspects to consider when copying from other tag wikis.
\n\nFirstly, attribution. While SE operates generally on a license that allows copying its contents it does require attribution. So for a verbatim copy of another person's work you'll need some basic attribution to the source.
\n\nSecondly, we should always have the IoT aspect in mind. Tag wikis are not about copying the wiki article from Wikipedia or another SE. They are about how the tag should be used on this site.
\n\nThus, I don't think simply copying any tag wikis is a good idea.
\n\nI have made a post about tag wikis in general on ELU.meta (English.StackExchange Tag Wiki Blueprint and Guideline1) and I would not mind if we'd use a similar structure on this site.
\n\nThe two most important things:
\n\nAlso keep this blog entry in mind Redesigned Tag Page.
\n\n1 Disclaimer, that's one of my posts.
\n" }, { "Id": "58", "CreationDate": "2016-12-07T10:16:01.780", "Body": "We already have post regarding regular votes (Vote Early, Vote Often (Seriously)), but I want to cast a special light on close votes. Private beta is about making the scope of the site more clear. Thus, trying to close questions you think are not a good fit is essential.
\n\nDon't hesitate to vote to close questions you think are a bad fit. People will either agree or disagree, by joining your close vote, abstaining or challenging you on meta. Either way every discussion about what's on scope and what's not on scope is a good discussion. It sharpens the scope and sets precedents we can work with.
\n\nRemember you can access the review queues earlier and have the privilege to close vote as long as we are in private beta even without those 2k reputation. It's a basic privilege in private beta. Also remember if you bring something to meta and it's not well received, you do not lose reputation on meta for down voting or being down voted. So vote on meta on those on-topic questions.
\n", "Title": "You have the power. Use your close votes!", "Tags": "|discussion|site-scope|vote-to-close|", "Answer": "It seem important at this stage to differentiate between down-voting an on-topic but poorly researched question, and voting to close. I tend to vote unclear
maybe too frequently on other sites - I think we need to make special effort here, this week, to rescue weak questions (which means more comments on the questions emphasising this topic)
A few recent questions have asked about how a specific IoT device should be constructed, like so:
\n\n\n \n\n\n
It's almost certain that these questions will be too broad, but it's worth considering whether these are actually on-topic at all - are these questions really about IoT or are they just software and hardware design questions in disguise?
\n\nI propose that we create a canned off-topic reason for these sorts of questions; something like this would be ideal:
\n\n\n\n\nQuestions asking about how an IoT device should be constructed are off-topic at Internet of Things because they are often not related to the topic of IoT, rather they are questions regarding hardware and software design. Consider asking about specific design choices rather than asking \"how should I build this?\".
\n
As I discussed in a comment below, I think that a lot of software/hardware questions are beyond the scope of this site anyway:
\n\nThere is certainly precedent on Stack Overflow and other SE sites to make certain classes of questions that are mostly closable anyway off-topic completely. Take, for example, the \"debugging help\" reason on Stack Overflow:
\n\n\n\n\nQuestions seeking debugging help (\"why isn't this code working?\") must include the desired behavior, a specific problem or error and the shortest code necessary to reproduce it in the question itself. Questions without a clear problem statement are not useful to other readers. See: How to create a Minimal, Complete, and Verifiable example.
\n
These will often be 'unclear what you're asking' anyway, but Stack Overflow make it clear that this class of question is inappropriate by providing an off-topic reason.
\n\nThe reason I chose the wording, 'Consider asking about specific design choices rather than asking \"how should I build this?\"' is because I would imagine there are some questions that can be good and on-topic for the site. Questions asking \"Why should I use _____ for an internet-connected LPG indicator?\" could easily form a great question, but could start out as something like the example I linked at the start of the question.
\n\nIn summary:
\n\nI disagree with this approach. If I understand your proposal correctly, it sounds like questions which are initially off-topic (how do I build...?) can become on-topic by actually building them, identifying specific issues, and then reposting. That sounds like moving from too broad to answerable, rather than off-topic to answerable.
\n\nIf you're going to accept specific questions on hardware/software, but not huge 'spec my whole project' questions, the distinction is one of scale, not of the questions being on- or off-topic.
\n" }, { "Id": "74", "CreationDate": "2016-12-07T22:43:25.327", "Body": "We currently have the tags protocol and beacon but the tag standards, sensors, kitchen-appliances and over-the-air-updates. That's inconsistent. All those are either general concepts which have clearly defined elements like protocols (HTTPS) and standards (802.11x) or are very much countable like the kitchen appliances and sensors.
\nI'd suggest to make tags like theses plural and make the singular tag a synonym.
\nThus, right now to create protocols, microcontrollers and beacons with the singular versions made synonyms.
\nAs Aurora0001 has stated in chat, a good rule of thumb is this:
\n\n\nmy rule is this: the tag should satisfy the sentence "this question is about _____"
\n"this question is about flash memory" is ok
\n"this question is about microcontroller" - nope
\n
(Emphasis mine)
\nSince nobody can vote on synonyms yet and the pluralization/hyphenation filters block us from doing this as users, we'll need the help of the mods which is currently the SE team supporting us in private beta.
\nIn the future we should make tags like these plural from the beginning. If we do so, the pluralization filter should prevent the singular tags from being created if I am not mistaken. I do believe it works for hyphenating tags as well.
\n", "Title": "Should these tags be plural?", "Tags": "|discussion|status-completed|tags|tag-synonyms|", "Answer": "I agree with this, primarily because the alternative of singularising tags such as standards would look totally ungrammatical (standard wouldn't mean the same thing!). There seems to be precedent on other Stack Exchange sites such as Community Building and ELU to have primarily plural tags, so we should follow this trend (and keep an eye out for any new tags popping up which don't look quite right!).
\n" }, { "Id": "150", "CreationDate": "2016-12-22T13:06:54.623", "Body": "Since it seems to be tag review season (judging by the amount of recent meta threads!), I think we need to consider whether edge-device is appropriate for the site, and if so, how we can improve the tag wiki and excerpt to make the meaning clear.
\n\nThere is currently no usage guidance for edge-device, but Wikipedia does have a useful definition which we could use if we decide this tag is worth keeping. I'm not sure whether it would be better to keep this tag or just use a more specific tag for the situation - on the one hand the generality of the tag could be useful for some questions, but it does seem to make it easy to write broad questions.
\n\nShould we keep this tag and clarify it, or should it be burninated?
\n", "Title": "Where is the edge of [edge-device]?", "Tags": "|discussion|tags|", "Answer": "I'm sure we will have a need for this tag in the future, but it probably makes sense to wait till we have questions which focus specifically on the characteristics of the edge device, rather than nodes which fit in the network at this position. I'd say that would be concentrator or cache types of function, rather than something like Alexa (which is arguably a borderline edge device).
\n\nConcepts like fog computing (where the processing and bandwidth is pushed out away from a central (cloud) server) might give a scenario where this tag is relevant in the future.
\n" }, { "Id": "186", "CreationDate": "2017-01-06T10:18:09.970", "Body": "Strongly related discussion. We should widen this site-scope discussion to handle all possibly emerging programming questions not just the embedded aspect.
\n\nWe certainly will have questions about the followng APIs for example:
\n\n\n\nI consider these on-topic at the moment, but then we should allow questions about any other web-service API too.
\n\nMaybe some questions about scripting will show up as well so all in all we should cover/handle all programming question from the beginning.
\n", "Title": "On-Topicness of programming questions in general", "Tags": "|discussion|site-scope|", "Answer": "I have no problem with that as long as there is a certain connectivity/IoT aspect to the use case. There might even be some APIs like the ones you list that should be generally on-topic.
\n\nThe really generic programming stuff without IoT connection, embeddedness or the like belongs on Stack Overflow.
\n" }, { "Id": "188", "CreationDate": "2017-01-07T10:12:11.510", "Body": "There have been several questions about web services and applications recently, and some have received close votes, so I think it'd be helpful to discuss whether these questions are on-topic for the site.
\n\nSome examples:
\n\n\n\nSo, are these questions on-topic, or should they be closed (and, in future, potentially migrated to Web Applications if it is clear that these questions will not be on-topic here)?
\n", "Title": "Are questions about web services on-topic?", "Tags": "|discussion|site-scope|", "Answer": "This is a poorly stated question, as it imagines a category of \"web services\" that is entirely orthogonal to anything which matters for fitting into this this site - and groups three entirely distinct things for common attention, which they are simply too different to receive.
\n\nRather obviously the google business email question is blatantly off topic.
\"What IoT services are available for storing/sending/publishing generic data in the cloud?\" is a site-related area, but pretty much all Stack Exchange sites reject as too broad questions which seek a list of what is out there - Stack Exchange sites are for questions that can have a specific answer, not for making lists.
\"How delayed can IFTTT triggers be?\" This seems like an IoT question, and at least from the title an appropriate one (though as in the previous go-around, not all IFTTT questions will be device related)
The diversity of answers for the three examples should demonstrate why it's hazardous to encourage thinking in terms of inapplicable categories - what matters not is if these are \"web services\", what matters is if they are about IoT and additionally if they are questions fitting the Stack Exchange model.
\n" }, { "Id": "200", "CreationDate": "2017-01-10T16:31:51.157", "Body": "Now all joking aside and still being new to all of this, what is beta a version of Internet of things? Or is beta a mix of different meanings?
\n\nI am assuming we had an alpha stage right?
\n", "Title": "When do we finally progress \"Internet of Things\" from beta to released?", "Tags": "|discussion|", "Answer": "This is largely extracurricular to the answers already posted, but this is important to provide a bit of context…
\n\nThis site is essentially \"done\" \u2014 released. This is a a fully functional, launched site. It is not \"in beta\" as you've come to understand it the traditional software development model, or \"in testing\" or something that failed to \"graduate\". So congratulations; enjoy your site!
\n\nThe continued use of the words like \"beta\" and \"graduated\" in this context is an unfortunate misnomer (as you can see by having to ask this questions at all). I wish we would do away with it for the reasons I outlined in this meta post.
\n\nSomeday, hopefully.
\n\nOne final note \u2014 pushing the \"seven essentials\" discussions (as mentioned in Helmar's answer) has often been found to be more harmful that helpful. There's no need to force \"rules discussions\" where there is no actual problem. Folks are more than willing to point out problems where they show up in actual practice, so tackle the problems when/if they become prominent in actual use — but until then, enjoy your newly launched site!
\n" }, { "Id": "211", "CreationDate": "2017-01-13T09:50:16.047", "Body": "This question belongs on the Security Stack Exchange.
\n\nWhen I voted to close it as belonging to another site, the only option I had was here on meta.
\n\nI have seen quite a few questions which clearly belong on Security; not to mention SuperUser, Software recommendations and even S.O.
\n\nSuch posts will only persist if we allow them and do not discourage false-posting.
\n\nIs it just that I don't have enough points to see them, or do other sites simple not exists as an option? And, if not, why not?
\n", "Title": "This question belongs on another site in the Stack Exchange network", "Tags": "|discussion|migration|", "Answer": "To me, this question is clearly on topic. Maybe the answers are a bit generic, but blockchain has been proposed as relevant to IoT, and that seems relevant (regardless of the answer and how much the primary discussion which supported the question was clickbait). Security is the big IoT issue...
\n" }, { "Id": "219", "CreationDate": "2017-01-13T21:11:24.323", "Body": "The tag emqttd was created lately. Since the project adopted the short name of EMQ
a emq tag might be prudent (synonymized to each other).
\n\nEMQ(Erlang MQTT Broker) is a distributed, massively scalable, highly extensible MQTT message broker written in Erlang/OTP.
\nNote
\nAdopt a shortened project name since 2.0 release: EMQ
\n
Source: http://emqtt.io/docs/v2/index.html
\n", "Title": "Tag review: emqtt and emq", "Tags": "|discussion|status-completed|tags|tag-synonyms|", "Answer": "I propose we just burninate emqttd and change all the uses of that tag to emq. When asking a question, new users will find emq popping up as they type 'emq', and the tag excerpt can be edited to something like this:
\n\n\n\n\nFor questions related to the Erlang MQTT Broker (formerly emqttd), its operation and the behaviour of the broker/clients.
\n
Ghanima has now retagged all the questions under emqttd, so the tag has been destroyed under the nightly maintenance. In other words, this proposal is status-completed.
\n" }, { "Id": "237", "CreationDate": "2017-01-27T05:19:08.113", "Body": "In Area51, while I was browsing, I saw 'Internet of Things' and joined this community. The description was:
\n\n\n\n\nBeta Q&A site for everyday objects embedded with electronics to be sensed, monitored, and controlled remotely.
\n
But I can't understand the subject to be discussed here. (I want to know)
\n", "Title": "What is IoT (Internet of Things)?", "Tags": "|discussion|site-scope|", "Answer": "Internet of Things is not a specific technology, or dependant on any specific technology. Rather it is a stage in the evolution of connected devices, enabled by the availability of two things: cheap endpoint compute, and cheap ubiquitous connectivity. We have progressed from telegram, telegraph and POTS, through an era of expensive home and business computers, to a time when it costs only a few $ to enable any device to communicate with other devices.
\n\nAs well as accessible connectivity, IoT exists in part because of cloud computing, and the ability to extract value from the large amounts of data which can now be collected very cheaply. A good example of this is collecting traffic data flow (by monitoring Sat-Nav activity on cellphones) and mass-transport route and pinch-point data (by monitoring cellphone MAC addresses as they traverse a physical space).
\n" }, { "Id": "254", "CreationDate": "2017-02-09T20:00:43.163", "Body": "The Help Center has a section about on-topic questions for this site, called 'What topics can I ask about here?'. At the minute, it's essentially blank, being filled with only boilerplate information:
\n\n\nPlease look around to see if your question has been asked before. It\u2019s also OK to ask and answer your own question.
\nIf your question is not specifically on-topic for Internet of Things Stack Exchange, it may be on topic for another Stack Exchange site. If no site currently exists that will accept your question, you may commit to or propose a new site at Area 51, the place where new Stack Exchange communities are democratically created.
\n
In our previous chat event, there was a discussion about what key points should be included, and based on that, and my observations of what seems to be accepted so far on the site, I propose adding the following information to the Help Center:
\n\n\nWhat topics can I ask about here?
\nIf you have a question about...
\n\n
\n- controlling, automating and sensing the environment using electronics ('smart devices'),
\n- consumer technology used for home automation,
\n- industrial applications of the Internet of Things, or
\n- the security, privacy, reliability and safety of these devices
\n... and it is not about ...
\n\n
\n- general computer networking, software and hardware
\n... you're in the right place!
\nPlease look around to see if your question has been asked before. It\u2019s also OK to ask and answer your own question.
\nIf your question is not specifically on-topic for Internet of Things, it may be on topic for another Stack Exchange site. If no site currently exists that will accept your question, you may commit to or propose a new site at Area 51, the place where new Stack Exchange communities are democratically created.
\n
I want to stress that this is a first draft of what the Help Center could look like; I think it's probably a waste of time to try and enumerate every possible off-topic question at this point, which is why there are only five bullet points worth of guidance. I expect that we'll need to iterate on this (if we choose to accept it at all), which brings me to the point of this meta question.
\nIt's probably helpful to have some guidance to show new users so that they can try to understand the site scope a little better; at the minute, off-topic questions are closed with a link to the Help Center, where there is no guidance at all specifically for this site.
\nSo, what do you all think about this draft? Should we include it in the Help Center now, or wait a little longer until we've got an even clearer picture about what is on-topic?
\n", "Title": "Improving the guidance in the Help Center for new users", "Tags": "|discussion|status-completed|new-users|help-center|", "Answer": "This draft is fine. We've been discussing it on a chat event and another meta post. I don't see how waiting a little longer will benefit is at all. If we discover that changes need to be made to the text later on, we can always discuss it over again and have our mods change it.
\n\nFor now: upload it.
\n" }, { "Id": "260", "CreationDate": "2017-02-23T18:05:01.247", "Body": "On Robotics.SE they have the following option in the Close --> Off-Topic list.
\n\n\n\n\nLife Questions are off-topic. Questions about choosing how to spend your time (what book to read, which class to take, what robotics project to construct, what career to pursue, etc.) may be about difficult decisions, and they are often important, but they are too specific to your own situation and are unlikely to help future visitors to the site. They would be better off asked in Robotics Chat.
\n
The quote says it all, what type of regular questions brought this option alive.
\n\nI think recently we had a question in this category and as we did not discuss such topic so far I though that we should now.
\n\nAs IoT is quite a popular buzzword there could be questions (very very broadly speaking here) like:
\n\n\"I want to do some IoT, where should I start\".
\n\nCurrently it does not seem to be a serious problem and maybe we do not need this closing reason at all, but we can talk about it in advance.
\n\nMaybe there are three ways:
\n\nAdd it as a close reason.
+1 It is completely unnecessary.
I think it's too early to add is as a close reason. We've got only three and we should make them count. So for the time being let's go with your option one and add it to the help center if we get a few more applicable questions.
\n\nFor the time being can use comments and too broad / primarily opinion based to handle these questions\u2014if they keep popping up.
\n" }, { "Id": "269", "CreationDate": "2017-03-22T15:38:30.747", "Body": "The smart-home tag is by far the biggest on the site, with 62 questions (about 19% of all questions) tagged with it.
\n\nHowever, as pointed out by dsample in this answer, it's quite a broad tag. As far as I can tell, it just says \"this question is about IoT in a home environment\", so it doesn't really convey a lot of information.
\n\nIt also doesn't match up with any of the tags used on other Stack Exchange sites:
\n\n\n\nNote: iot is not valid for this site, and is blacklisted because the whole site is about IoT.
\n\nCould we improve this tag to make it more useful? We could consider:
\n\nsynonymising home-automation with smart-home and then leave it as it is.
burninating smart-home and using more specific tags
narrowing down smart-home to be used for a specific purpose rather than just anything in a home
doing nothing at all.
What do you think? Share your views on the tag below, and if you have any good ideas about how we can improve smart-home (if it does need improving), feel free to suggest those.
\n", "Title": "Is [smart-home] too broad?", "Tags": "|discussion|tags|", "Answer": "\n\nsynonymising home-automation with smart-home and
\nnarrowing down smart-home
\n
Smart-home should (here) be more about the home, not the appliances. I think we have a different focus compared with the other sites, we have some other big areas of interest (particularly if more developers start to come this way).
\nHowever, it may be useful for some users to be able to follow smart-home, rather than a collection of other tags. I'm still on the side of removing the smart-home where there is a better tag, such as lighting, smart-tv, smart-plugs, digital-cameras etc. Even then, we have a fair number of more general questions which are about the system context rather than individual elements.
\n" }, { "Id": "271", "CreationDate": "2017-04-08T16:30:06.690", "Body": "I'm new to the IoT field and want to know about IoT. For some of the questions I need clear explanations which I don't get by google search. I'm a little afraid of down votes. Is it ok to ask very basic questions here?
\n", "Title": "Afraid to ask very basic questions", "Tags": "|discussion|moderation|", "Answer": "Basic questions are best if you can add enough detail in your post to show that you have done some research. This will also make it easier for people answering your question to pitch their answer at roughly the right level. There is a difference between a badly asked question, and a very basic question.
\n" }, { "Id": "274", "CreationDate": "2017-04-20T15:20:11.290", "Body": "We've had quite a few questions involving code on the site now:
\n\nRecapture/reset the first frame from a motion detector every N seconds
How can I change Alexa's pronunciation of a specific word in a skill?
Creating indirect (managed) connection between audio source and sink in CSR bluecore VM
The general consensus (see also here) is that programming questions are usually on-topic provided there is a link to an IoT use case.
\n\nI think it'd be helpful to enable syntax highlighting here (using language hints, where <!-- language: lang-example -->
comments are placed before the code block). Personally, I find it much easier to read code blocks with syntax highlighting once they begin to pass trivial sizes (even 5 or 6 lines can benefit from some syntax highlighting), so I imagine many posts will benefit here.
Would this be useful to others, and should it be enabled here? If there's enough support, I'll let the community managers know that we're interested, but I see little point in enabling it if the majority of people aren't going to use it.
\n", "Title": "Enable syntax highlighting for code blocks", "Tags": "|feature-request|status-completed|", "Answer": "I have edited our posts so far to enable the fitting code syntax highlighting. It seems like we don't have a real conclusive tag which we could set to a definitive language. If there is a more clear correlation in the future just shoot a notice to the mod team and we will set the proper default for the tag.
\n" }, { "Id": "362", "CreationDate": "2018-03-09T08:25:06.610", "Body": "In my profile I have to follow smartHome badge instead of for example networking badge, which is my top tag.
\n\nThe selector does not give any other option, it has only that one value.
\n\nWhat is wrong?
\n", "Title": "Cannot select what ever tag for \"Next tag badge\" selector", "Tags": "|bug|status-bydesign|badges|", "Answer": "It is said on meta stackoverflow, that tag must have at least 100 questions before a badge is able to be earned.
\n\nIt appears that this site is such a young one that only smartHome (and maybe some few others I am not active in) have reached that level so that smartHome is the only one qualified to the selection.
\n\nBy now, networking has only 70 questions and smarthome 135, so that seems the case.
\n" }, { "Id": "377", "CreationDate": "2019-01-06T09:55:47.067", "Body": "If not, then how can word it? If not possible to be on topic here, then where?
\n\nTl;dr - how can I detect the presence of a Xiaomi Mi Band 3?
\n\nThe full story:
\n\nAs you can see from my question on h/w recommendations, I am trying to design an evacuation system for a chemical factory.
\n\nThat requires knowing which room each employee is in at any given time. I can handle the system to track the employees, but have been looking for a long time for a durable wearable with long battery life for each employee to wear or carry.
\n\nI had considered Android 'phone, but they might be too expensive/bulky/fragile/short battery life.
A Raspberry Pi Zero W is cheap, but also quite large, needs a casing and I am unsure about battery life.
Passive RFID might not have the range, and active requires battery.
The AdaFruit Flora BLE looks interesting, but I can't find data about its battery life.
The I had an epiphany when I looked down and saw the cheap fitness tracker on my wrist. It's a Xiaomi Mi Band 3. I am charging it about once every 3 weeks, although I currently do not turn BT. I will need to calibrate that, although reviews give it 7 days of heavy usage, so it will be more than sufficient for a single day's use.
\n\nSo - finally - to the question: would it be on topic to ask how I can detect transmission from the device?
\n\nIf they are frequent enough (say, more than once per minute), then it doesn't matter what the signal is, so long as I can get a MAC address out of it and use that to locate the device.
\n", "Title": "Is device detection on-topic?", "Tags": "|discussion|", "Answer": "The question would be better with more generic phrasing, I think - as it stands, the reader is lead mistakenly to the specific brand/device.
\n\nAsking how to monitor a population of bluetooth devices (in any of the various possible states) seems perfectly in scope, and also brings in the meta/derrived sensing aspects of IoT.
\n" }, { "Id": "385", "CreationDate": "2019-08-12T07:23:53.517", "Body": "I am looking for a board, and think that I need someone to say that they have used it, rather than googling for it, and can confirm that it does what I want.
\n\nI would like to program in Ada, so the STM32 looks ideal (I am also aware that the BBC micro:bit has good Ada support, but ...) I would like a board with a display, and, importantly, I want to use the the PlatformIO IDE's debugger, to enable me to set breakpoints, examine variables, view the stack, etc, rather than just print to the serial monitor.
\n\nSo I need a board that supports the Platform Unified Debugger.
\n\nIs such a question on topic here? I am aware of our hardware recommendations, site, but doubt that I would get much of an answer there.
\n", "Title": "Seeking an STM32 - is the question on-topic?", "Tags": "|discussion|", "Answer": "You can ask 'does PIO support all Cortex-M, or only specific devices'. That wouldn't be an IoT question, and I'm not sure who would answer, other than the developer. This answer does seem to be 'yes' though.
\n\nOverall, I think these sorts of selection questions are best asked by identifying the selection criteria which would rule them out. This would probably come down to a minimum flash/ram requirement for Cortex-M, and maybe some RTOS support features (i.e. not M0).
\n\nI think the dev board selection is a difficult problem to generalise. There are so many different factors which make for a specific selection. Maybe the board which looks good is being replaced by something newer/cheaper. Maybe an over-spec and more expensive board is OK, or maybe you're putting 20 in different places around the house. Actually keeping up with the variety of different dev boards and IoT eval kits seems like a full time job, so you're always going to be out of date.
\n" }, { "Id": "369", "CreationDate": "2018-09-06T08:18:20.437", "Body": "The following question is pretty obviously (at least to me) unsalvageable, the edit was made to point out how badly written the question was and doesn't improve it at all (apart from to make it even clearer to the OP what was wrong with it).
\n\n\n\nCan anybody come up with a reason for the reopen vote?
\n", "Title": "Reopen vote on question that should be deleted", "Tags": "|discussion|voting|", "Answer": "I see a 2nd question (not a clear case for deletion, but still in need of work) is gaining re-open votes after a minor edit. As per the suggestion above, I flagged it.
\n" }, { "Id": "365", "CreationDate": "2018-04-19T11:35:42.290", "Body": "When looking at accounts on my profile, we have a generic logo. Lots of other stacks have cool designs.
\n\nIs anyone accepting design concepts for an IoT logo?
\n", "Title": "Iot Stack logo addition?", "Tags": "|feature-request|status-deferred|", "Answer": "You're absolutely right that many sites have nicer logos - and actually full themes - than we do. The reason is because we are still in beta. As it stands currently, beta sites don't have a full site theme, and all follow the theme mentioned in this post on meta.
\n\nThere is, however, a tentative change coming, in which there is supposed to be a fairly major overhaul of the themes. There's also a little-noticed comment by Jon Ericson which suggests that beta sites may be able to work out their own themes once the changes have been rolled out.
\n\nSo by and large, the answer is, we can't change this; we have to wait on the Stack Exchange team. Hopefully, they'll work something out. Probably in about 6-8 weeks.
\n\nFor more information, you can browse the beta-sites and design tags on meta.stackexchange.
\n" }, { "Id": "356", "CreationDate": "2018-01-22T07:50:56.187", "Body": "This question is the second by the same author asking for code only help for Amazon Web Services.
\n\nHere is my comment :
\n\n\n\n\nAs I said in my accepted answer to your previous question, I am not\n sure that this is actually an IoT question. Even if it is, you would\n probably get better help on Stack\n Overflow. We currently have a total of\n 34 AWS questions on 3 tags, where they have that many ASW-xxx\n specialized tags with many thousands of questions. Furthermore, this\n question suits their format - post some code, say what it should do\n and what it is doing wrongly. I am unsure here, and more\n interested in getting you an answer than which site you should post\n on.
\n
Am I correct to say so? I realize that we are still in beta, and every bit of traffic helps, but, of course, that should not be a consideration.
\n\nI honestly do believe that the OP would get more help on SO.
\n\nIs there even a question here? :-)
\n\nHow about, \"are pure coding questions on-topic\"?
\n", "Title": "Are Pure Coding Questions On-Topic?", "Tags": "|discussion|site-scope|", "Answer": "The OP is trying to set up AWS IoT. That should be in scope. Short reason: It's right there in the name.
\n\nAlso on-topic are any coding questions which have an IoT purpose. Stack Exchange gave us a site to help out people who want to create or use IoT stuff. Something along our definition of IoT devices (the result was quite fuzzy) and our discussed tag lines should set the borders.
\n\n\n\n\nQ&A for builders and users of networked sensors and control devices\u2014be it for your smart home, industry automation or environmental sensors.
\n
One of the guiding principles around all new beta sites is that a question being on-topic somewhere else doesn't mean necessarily that it is off-topic on a new site. With the logic that there are more coders on SO (which is very true) no other site in the network should allow any coding questions. Obviously that's not the case when one considers the almost 1800 Java questions on Superuser. On the other hand developer-only focused sites do not survive the Area 51 process as duplicate of Stack Overflow.
\n\nSo yes, our SE mandate if you will does not point to pure coding questions being on-topic but coding questions can very well be on-topic on other sites on the network.
\n\nAre there more people on SO who know about AWS-IoT. Considering the user base in the millions\u2014probably. Are IoT questions getting good answers over there? At the time of this writing there are 302 questions tagged AWS-IoT and 172 of those unanswered (i.e. no upvoted answer). That's a meager 43% success rate\u2014well below Stack Overflows 71% answer rate. Other IoT-related tags rank similarly. Our 24 AWS-IoT questions however have only 2 unanswered with one of the latter asked yesterday. That's well over 90% if one calls that statistically significant.
\n\nStack Exchange gave us a site to create out a place in the network for IoT questions. We're not here to duplicate Stack Overflow, but if someone tries to set up their future IoT solution and the solution happens to require some coding or the configuration needs some tweaks it's very much on-topic.
\n\nIf it's about basic coding problems like basic string operations point the people to Stack Overflow, if it's more specific, especially with an expressed IoT purpose welcome them.
\n" }, { "Id": "352", "CreationDate": "2018-01-13T15:29:37.100", "Body": "Is there any way to follow my favorite questions to get notifications (answer, comment) to my messages inbox such as the question I asked?
\n\nIf there is not, could you add this feature?
\n", "Title": "Can I get notifications for my favorite questions?", "Tags": "|support|", "Answer": "There's currently no way to get notifications for favourite questions (starred questions). You can mark favourite questions like this:
\n\n\n\nThe 'favorites' tab in your profile will show you any activity on your favourite questions \u2014 the number on the tab increases, like this:
\n\n\n\nImages from Meta Stack Exchange's FAQ\n on favourite questions.
\n\nYou don't get an inbox notification, but when you go to your profile and check, this will be indicated. When you click on the tab, the questions with recent activity will be near the top, and highlighted in yellow.
\n\nThere is a request to add notifications for favourites, but that was nearly 7 years ago, and it's still not implemented today. So, unfortunately, this seems unlikely to happen, and you'll have to use the alternative method I described above.
\n" }, { "Id": "332", "CreationDate": "2017-10-19T15:59:05.267", "Body": "For this answer... https://iot.stackexchange.com/a/2215/3640
\n\nAdmittedly not a great answer, but why does the Achievements rep shows +6 for this answer but the answer itself shows -1. How can that be?
\n", "Title": "Why does header show +6 but Answer show -1", "Tags": "|support|reputation|", "Answer": "Reputation:
\n\nOne upvote: +10\nTwo downvotes: -4\nTotal: +6\n
\n\nNet vote count: -1
\n" }, { "Id": "328", "CreationDate": "2017-08-22T15:51:28.637", "Body": "I noted that the question: Remote access through carrier-grade NAT
\n\nis answered, but not via a answer but via a reference to another answer.
\n\nThe thing is that it is still marked as \"0\" answers and status as unanswered.
\n\nIs there a way of changing the status to \"Answered\"?
\n", "Title": "Closing or mark questions as answered", "Tags": "|support|closed-questions|exact-duplicates|", "Answer": "That question is closed as a duplicate of a different question. There isn't any need to \"mark it as answered\" in any way, for a couple of reasons:
\n\nUsers who aren't logged in (and, for example, find that question through search results) will automatically be redirected to the duplicate target. Open an Incognito tab and click the link in your meta question to try it; you won't see the unanswered question!
Closed questions don't show up in the unanswered tab (note that the link there is for the unanswered tab of remote-access), which the question is tagged with. It also won't count as unanswered in our site stats.
In our system, a question is considered 'answered' in the unanswered questions tab if it has at least one answer with score > 0 or accepted. So essentially, in direct answer to your question, no, there's no way to manually mark it as solved, but there's no need to do that anyway!
\n\nBy the way: welcome to the site!
\n" }, { "Id": "324", "CreationDate": "2017-08-14T09:14:14.113", "Body": "Today, when I was looking in the Area 51, I found that the number of questions asked in this site seems to be 1 per day, which it says to be poor.
\n\nAs I have noticed, SE will has removed sites from beta earlier due to low performance.
\n\nI don't mean to pump in low quality questions into the platform, I just wanted to know whether we will stand the crisis.
\n\nWe need more people viewing the site and more genuine doubts and clarifications coming up everyday.
\n\nHope we could contribute something towards it!
\n", "Title": "Will we go down with the number of questions each day?", "Tags": "|discussion|", "Answer": "Activity seems to be kind of level - we get good views, but not so many questions now. As a new field, its not unreasonable that we take time to grow - particularly since there is some overlap with existing sites (different ones depending on the questions). What will help is more good questions, more experts in the field, and more views.
\n\nSo to help, share the best questions you find with your other networks, and ask good questions here.
\n" }, { "Id": "316", "CreationDate": "2017-07-22T17:44:54.537", "Body": "I don't know if the question belongs here, but I have faced this mostly in this site.
\n\nWhen a question is overly difficult to answer and there is no easy way to tell who is correct, instead of up and down votes or new answers or constructive comments I see two opposite opinions starting to battle under the question and answer(s).
\n\nTo tell that answer is wrong you can vote down and comment, but if things go arguing, I would go to chat. My first meta post was such case, then I moved the arguing to meta.
\n\nIs chat the correct place for arguing or should we just shoot down answers little bit with less arguing? Mostly I refer to cases where the opposite opinions are clear by first time said and the point of comments is more to say the last word than to be constructive.
\n", "Title": "Correct way and place for arguing", "Tags": "|discussion|", "Answer": "First things first. You're in the right place.
\n\n\nI don't know if the question belongs here, but I have faced this mostly in this site.
\n[...]
\nTo tell that answer is wrong you can vote down and comment, but if things go arguing, I would go to chat. My first meta post was such case, then I moved the arguing to meta.
\n
Yes, meta is very much the right place to go. For asking about how the site works and where to do what that is.
\n\n\nMeta is our community for discussing the site itself, including bugs, feedback, and governance issues. \u2014 Help Center
\n
Meta is where you can discuss and influence the things that don't sit right with you on a more general level. While there are discussions about specific questions on meta, most meta questions deal with general topics and try to add a level of abstraction to the problem. Now to your actual question.
\nGenerally there's five types of reaction open to you if you disagree with an answer.
\nYou'll observe that none of the options above involves getting into bipartisan discussions about questions or answers in the comments. Trench warfare in the comments to have the last word is not what comments are for.
\n\n\nComments are temporary "Post-It" notes left on a question or answer. \u2014 Help Center
\n
There's a reason for commenting on other people's posts requiring the most reputation from all options mentioned above. They also do not generate reputation are to be seen as temporary. Don't pour effort into winning comment matches.
\nWe \u2014 as mods \u2014 treat comments very much as the ephemeral virtual Post-It notes they are and delete tons of them. These are the reasons for deleting comments: Violates Be Nice, no longer needed, too chatty and otherwise unnecessary. That encompasses almost every I-want-the-last-level-word-debate. If you stumble across such debates or find yourself as a part of it feel free to flag it.
\nTo summarize, every time you feel it's gotten to the point where it's just about having the last word and you wan't it. Don't.
\n\n1: Don't worry about anyone's reputation. If you comment on a new user's post they can comment to answer there. The 50 reputation barrier only applies to other people's posts.
\n2: Remember that chat requires 20 reputation.
\n" }, { "Id": "304", "CreationDate": "2017-07-12T05:22:03.560", "Body": "There is a vast discussion around this question and its answers, where it is difficult to say who is wrong and right.
\n\nThe question is about a function in a software, where a quite short text
\n\n\n\n\nYou will also have the option to check the box saying This was a false alarm. This is for internal tracking and helps us improve Smart Home Monitor.
\n
tells how the specific part of software is used by the software.
\n\nIf no more information is given online by the manufacturer of the software, why should there be more speculation of the purpose? Another answer tries that, and is getting down votes.
\n\nIn both cases these options are basically what you can say and is it about the answerers responsibility if there is not possible way to answer in long format to this without taking answers from your head?
\n", "Title": "How to answer question when not much information about the issue is available and you cannot fetch it by yourself?", "Tags": "|discussion|site-scope|answers|", "Answer": "\n\n\nAny answer that gets the asker going in the right direction is helpful, but do try to mention any limitations, assumptions or simplifications in your answer. Brevity is acceptable, but fuller explanations are better. - The help center of every Stack Exchange site.
\n
In most questions worth asking there is information that is not readily available on #1 of a google search. Providing such information from a credible source \u2014 and I do consider the manufacturer of a device a credible, authoritative source \u2014 is always helpful.
\n\nTo every question there is a literal interpretation and the interpretation of intent. The literal question in this case was:
\n\n\n\n\nIs there, at this point, a purpose for the \"false alarm\" response? What does marking an alert as a false alarm do?
\n
The answer with the quote from the manufacturer does in fact answer this on a high level. There is no customer functionality. It's used for internal purposes.
\n\nOf course, it can be argued that he question that is not written is actually more a long the lines of, \"which button should we press?\"
\n\nDoes your answer answer that question? No it does not. It only informs the decision that the OP can now make. Could the answer be improved by giving a recommendation? Sure. Is a recommendation necessary to answer the question as written? No.
\n\nThere's another problem that in my view sparked this discussion that plagues many questions where the OP cannot know what information is out there. Sometimes it's just a snippet that's out there, but that's okay. If a better answer does come along from someone who found more information or maybe from a SmartThings engineer with internal knowledge that answer should get more appreciation.
\n\nAlas, sometimes there isn't more information. We cannot ask of every person answering to make a research project out of it. In short, if you provide an authoritative or at least credible source that does point the OP in the right direction by either answering the question as written or as intended \u2014 hopefully both \u2014 that can be posted as answer. It's not pulitzer worthy, but it is an answer.
\n" }, { "Id": "301", "CreationDate": "2017-07-11T06:17:11.890", "Body": "I do see a digital-cameras tag that is used to tag questions related to surveillance cameras.
\n\nI am proposing a separate surveillance-cameras tag which can be used to tag questions related to surveillance-cameras that have features of security, alerts, face recognition and are targeted towards the theme of surveillance.
\n", "Title": "Should we have a tag for surveillance cameras?", "Tags": "|discussion|status-completed|tags|", "Answer": "Yes. I agree that this would be useful. Feel free to edit that tag in to any relevant questions (the first use of the tag will create it).
\n\nSince surveillance cameras typically have more functionality than a typical camera might, it makes sense to have a specific tag. Having product-related tags may also be worth considering in the near future.
\n" }, { "Id": "299", "CreationDate": "2017-07-07T15:19:00.950", "Body": "There have over the past several months been many questions about CSR Bluetooth chips posted, all by the same user. Many of these have gone unanswered, and there's no clear relevance to classic IoT goals or issues in any of them.
\n\nAdditionally, many of the older questions seem to be about Bluetooth Audio - which typically means the classic BT headpiece or speaker type of application.
\n\nAre these on topic just because someone \"could\" use Bluetooth for an IoT purpose, even absent any suggesting that they are doing so or that such a desire has any specific relevance to the question being asked? Or especially when there are counterindications that the application is not IoT, for example in the audio questions?
\n\nSome points to consider:
\n\nThere is a long history of covering similar questions about details of competing BLE-enabled MCU from Nordic and TI on Electronics Stack Exchange. If CSR has less coverage there, it's likely because they've historically made less technical information publicly available and provided their own support to the corporate customers using their parts. Is it healthy for the SE system overall to have two manufacturers chip's covered on EESE, while a third builds a tradition on IoT just because one anonymous user put it there?
There is a long history of covering both PC and mobile (iOS/Android) programming for interacting with both classic Bluetooth and BLE devices on Stackoverflow itself. This includes both traditional BT use cases, and some of the newer more gadget-like BLE ones, such as location Beacons, etc.
Substitute WiFi for BT, and it would likely be clear from the popularity of non-IoT uses that generic questions are probably off topic unless they are closely aligned with an IoT need. Substitute Zigbee, and opinions might lean more towards relevance, but then, unlike BT or WiFi, the most well-known applications of Zigbee have been in systems of the sort which have come to be be called IoT.
It's also worth noting that many of these questions are poorly stated - especially when considering the reaction that someone may get when trying to post them elsewhere. Both EESE and Stackoverflow tend to deal quickly with poorly stated questions on the basis that they are unanswerable, and that may at times be mistaken to mean that they are off-topic, when in fact well stated questions on the same topics have been handled there well.
\n\nOf course a question involving Bluetooth where the question itself was about an IoT-specific problem would be clearly on topic, and if well stated appropriate here. The meta question is rather if being about Bluetooth alone is enough for a question to qualify as on topic, absent any IoT specificity to what is being asked.
\n", "Title": "Are Generic Bluetooth Questions on Topic Here?", "Tags": "|discussion|site-scope|", "Answer": "No. Generic Bluetooth Questions which do not actually invoke any IoT-specific application are, off topic and should be closed unless edited to show a specific relevance of the question actually asked.
\n\nThis would be in keeping with Wifi and similar generic communication questions where the means of communication does not make something \"IoT\", but the information being communicated could.
\n" }, { "Id": "249", "CreationDate": "2017-02-08T19:22:41.077", "Body": "Referring to comments in question \"How can I find Narrow band IoT module or chipset? [on hold]\"
\n\nIn the comments it is argued that \"it is of an essentially transient value. In other words, the answer cannot remain the same long-term\".
\n\nSurely you cannot propose that questions only remain open if the answer is valid until the end of time? It is my understanding from the Stack Overflow origins is that the upvoting and editing format exists precisely to allow questions to be re-answered over time. Granted, it doesn't always work, but is the general idea.
\n\nWe are wanting people to come here and ask (basic) questions on a new and emerging field of technology, but we close questions because, although they are right now, may not be right in future? I think that it is banal over-moderating that will chase people away when it is needed the most. The Area 51 stats say that the number of questions asked per day \"Needs work\", but people are discouraged from asking questions. It's absurd.
\n\nIndeed one of the most popular questions is almost guaranteed to be irrelevant in a years time. Are the moderators suggesting that \"How can I stop Alexa from ordering things if it hears a voice on TV\" be closed because it is highly likely, considering the mainstream news attention that this problem has received, that Amazon is going to correct it on the next version?
\n", "Title": "Should questions be closed as off-topic because \"any answer will be of transient value\"?", "Tags": "|discussion|site-scope|closed-questions|", "Answer": "Sometimes, the stated close reason is a shorthand for saying you don't seem to have put any real thought into reasearching this subject, or maybe you are just really out of your depth.
\n\nThe trade-off is really in working out how to encourage people to do more work before asking a question. If these borderline questions don't get closed, I think it sets the wrong expectation for what will be answered, and that will discourage the regular users who are already here.
\n\nThe question in case didn't seem useful right now, let alone in 6 months time. Seeing your answer makes the subject more relevant - but the ideal version of the question would set out the timeline of these protocols, and question if they are slideware, vapourware or about to break into primetime. A question which would be suitable for the same answer you wrote...
\n" }, { "Id": "158", "CreationDate": "2016-12-23T16:32:31.043", "Body": "I was fairly intensely running through a bunch of older posts this morning and used up all 40 of my votes. When I try to upvote a question, I see:
\n\n\n\nTotally normal. What isn't normal is that the Vox Populi Progress remains at 38/40, and has done for the past hour or so. Usually, it takes a few minutes, but this seems a bit long.
\n\n\n\nIs this a bug, or do is it taking a bit longer to come?
\n", "Title": "Vox Populi Badge not given", "Tags": "|support|badges|voting|", "Answer": "You aren't guaranteed 40 votes per day, which may seem confusing (and I think it is!), so here are the rules, summarised from What are the limits on how I can cast, change, and retract votes? on Meta Stack Exchange:
\n\nAfter that, your vote cap is dictated by the formula in the first link:
\n\n\n\n\nmin(\u202f30\u202f+\u202f\u230a1.2\u00d7Q25\u230b, 40\u202f)
\n
Where \u230a\u230b
means \"round down\" and Q25 is the number of question votes in your first 25 votes.
In effect, the above means that you must have voted on questions at least 9 times within your first 25 votes to get the maximum of 10 'bonus votes'
The other catch is that as soon as you see the '_ votes remaining' warning, that's it - you will not be able to get any more votes for today no matter what you do.
I suspect you only voted on 8 questions in your first 25 votes (Q25 = 8 / 1.2), giving you only 8 bonus votes.
\n" }, { "Id": "154", "CreationDate": "2016-12-22T19:23:03.973", "Body": "I saw this question asking about the UK regulations for making your own electrical equipment, and it got me thinking: if someone answers it one way and gets it wrong, and the guy's house burns down or he ends up in jail, is the site in any way culpable? Is simple participation here taking on liability for interpreting laws? Should we allow these questions? Or, like Security SE, should we flat-out issue a \"legal questions are off topic\" edict, and avoid the liability?
\n\nThe Help Center for IoT isn't yet complete, of course. But I'd propose that we should start off by either avoiding questions that have the potential to get people in legal trouble, or making sure questions about safety, legal, or regulatory, issues come with a big legal disclaimer: \"neither IoT.se, the posters, nor the community are liable for the accuracy of this information; neither posters nor moderators are lawyers; even if a reader or poster on this site happens to be a lawyer by chance, he or she is not your lawyer, you are not paying for his or her advice, so he or she has no responsibility for the accuracy of what you may read; nothing on this site constitutes legal advice; the reader assumes all risks; no lifeguard on duty; do not stand on or above this page; blah blah blah.\"
\n", "Title": "Should legal or code questions be off-topic?", "Tags": "|discussion|site-scope|", "Answer": "According to the bottom of the page of every SE site:
\n\n\n\n\nsite design / logo \u00a9 2016 Stack Exchange Inc; user contributions licensed under cc by-sa 3.0 with attribution required
\n
Everything any user posts is cc by-sa 3.0 licensed, which following the link excludes all warranties.
\n\n\n\n\nNo warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material.
\n
Added to the terms of service Aurora already cited, SE and us users seem to be very well shielded against legal liability\u2014as long as no one can prove harmful intent1.
\n\nWith my layman legal evaluation out of the way1, I say we shouldn't start marking some posts with legal disclaimers. The reason is simple. If we start putting organized disclaimers on some posts we create the impression that everything else doesn't need the disclaimer\u2014furthering the false assumption that everything else can be used without any own thought at all. So let's not do post notices.
\n\nAs the CC license tells us, there are no warranties given and it does not even mean I can use anything mentioned in the answer. Simple example, just because an answer mentions a commercial software, I cannot use it, I still have to buy it first. Even if that answer were to give hints where I could find it.
\n\nFurthermore, which legal code would one use as basic? US, because Stack Exchange is based there? The country where the OP or the answering user comes from because they happen to know something about that legal situation? Or err on the side of caution and pick the strictest law? How to find out which one that is? Do we stop with safety? What about privacy, security, violation of radio bands, copyright, etc ... That would require full-time lawyers to assess most of the posts on the site.
\n\nNeither we as users, nor any future moderation team will be able to catch every pitfall in every post. Even worse, if a moderator decided that a safety note is not necessary, the legislation or other bases for his or her assessment could change, so a post notice for such concerns would have to be re-assessed for every post on a regular basis. No voluntary staff of moderators and user reviewer pool however big can provide a consistent tagging with post notices. So let's not start with it in the first place.
\n\nHowever, that does not mean that one can't as a user provide all the warnings one deems appropriate as part of the answer, question or comment. I'd even encourage everyone to rise the safety, security, privacy and whatnot concerns they have with answers because it will likely make those answers better. Better, safer content is always good for the site. If you do see answers that don't take important points into consideration comment on them, downvote or provide an answer of your own, that's everyone's prerogative as user of the site.
\n\nStack Exchange gives us the tools to downvote, correct (by editing, commenting or posting answers), close and delete posts already. Those are the things that Stack Exchange moderation is build on. Let's use these community moderation tools rather than using post notices that future lawyer moderators can use.
\n\nI think in there narrow confines of IoT related legal questions we should consider having them on-topic for now. The problem with every real regulatory problem is, that there are two sides to it, a legal one and a practical one. Generally laws are fuzzy and living the law is established by court rulings and precedence. Within the IoT domain there is barely established precedence available and the project knowledge of IoT experts might be even more applicable than that of a generic legal expert.
\n\nIf we as a community can't provide proper answers to those questions, we can always re-evaluate\u2014or try winning a legal expert with IoT knowledge.
\n\n1 Not a lawyer
\n" }, { "Id": "148", "CreationDate": "2016-12-22T12:00:18.113", "Body": "Do we really need an unmanned-aerial-vehicle and a drones tag as well?
\n\nBoth of the tags are used once, at the same question. I think one of them should be the other one's synonym.
\n", "Title": "Tag review: [tag:unmanned-aerial-vehicle], [tag:drones]", "Tags": "|support|status-completed|", "Answer": "I have proposed synonymisation of drones and unmanned-aerial-vehicle, however there is only one user eligible to create and vote on synonyms for the drones tag: myself, so the community is currently unable to handle the issue by itself.
\n\nSince I am now a moderator, I have just approved this.
\n" }, { "Id": "145", "CreationDate": "2016-12-21T13:46:10.980", "Body": "Since we won't be going public until 2017, we as private beta users should make every effort to keep the fire burning until the site does get opened to the general public.
\n\nThere is also a terrific badge to be earned by amping up your beta participation. The beta badge. Its requirements are very reasonably and only require you to do the following.
\n\n\n\n\nIt will allow you to proudly pin a shiny silver beta badge to your
\nchestprofile that people will adore you for forever.
The one additional requirement the badge has is that we actually reach public beta. Luckily, everyone's own chasing of that badge with valuable questions, answers, votes and visits will help us get there. Hopefully, it will also broaden our pool people asking questions a bit.
\n\nDon't worry, our voting base doesn't bite. Only 7 from over a hundred questions have a negative score and no single answer is below zero.
\n", "Title": "Take Your Once-in-a-Lifetime \"Beta\"-Badge Opportunity in Private Beta!", "Tags": "|discussion|", "Answer": "\n\n\nGood news, everyone! The new Internet of Things Stack Exchange site is now open to the public.
\n
Congrats and thank you to all nineteen honorees and everyone else who helped us get here. Let's keep getting more people involved, asking more great questions and providing great answers. On to site graduation we go :)
\n" }, { "Id": "134", "CreationDate": "2016-12-20T21:29:41.797", "Body": "Looks like we are not going public this year due to holidays.
\n\n\n \n\n\n
That begs the question how we get all those despaired souls to this site who get new IoT stuff on the holidays and just can't get it to work. Has anyone an idea besides word-of-mouth to get the word out? Ordinarily if we were public those questions about all the new toys that don't work and our great answers how they do get to work would be highly searchable on Google. Those days will be full of questions by people who try to figure out how their new stuff works. We just have to get them here.
\n\nMaybe there can be special Community Ads that advertises us over the holidays. I used my unparalleled(ly bad) paint skills to make a sketch.
\n\n\n\nDo you guys have other ideas?
\n", "Title": "How do we get the people who desperately want to use their new Christmas IoT stuff on the site?", "Tags": "|discussion|site-promotion|", "Answer": "I tweeted this image, and gained one user (with only 200 odd followers).
\n" }, { "Id": "130", "CreationDate": "2016-12-19T18:40:49.080", "Body": "As suggested in A Recipe to Promote your Site, we need to start taking small, focused steps to start getting the word out about Internet of Things Stack Exchange.
\n\nTo help the site to grow, I think we should try to reach out to other IoT communities and see if they're interested in writing about us or allowing us to share a link to the site. I shared a link on Reddit recently, which seemed to have a dramatic effect on the site traffic (I shared the link on the the 12th of December).
\n\nAre there any sites you frequent that might be interested in discussing the site or allowing us to share our Internet of Things Stack Exchange with their community? Once we've collected a list of sites that might be interested, we should ask them if they are happy with the idea once we reach public beta, and spread the word from there.
\n", "Title": "Which blogs and IoT communities might be interested in this site?", "Tags": "|discussion|site-promotion|", "Answer": "Here are some ideas:
\n\nOver this question What does the Lively Medical Alert Watch Monitor? (prior to any edits) the following issue has been risen:
\n\n\n\n\nWhy the upvotes for someone who can't be bothered to Google? The information requested is easily discoverable at the company's site mylively.com or by Googling for reviews, such as yahoo.com/tech/\u2026 If I had enough rep to vote to close, I would. This sort of question does not help our site at all
\n
Potential \"lack of research\" notwithstanding* - what is the level of difficulty for acceptable questions of this site?
\n\nSo this is again a question about the expected audience of this site. Do we embrace entry level questions that seem easy to the expert and may be easily researched using the right search terms - a thing that is often trivial to the expert but not so much to any beginner - or do we not?
\n\n* Don't get me wrong here. It is of course generally accepted that a certain amount of own research effort is expected of users before they post any new questions - with the ever ongoing controversy being about the How much. Failure to provide this research should be communicated to the OP by downvotes, comments, and flags where appropriate.
\n", "Title": "Easy questions - or: Are there questions just too simple for this site?", "Tags": "|discussion|", "Answer": "I'll be brutally honest in what I say below, since I think this is an issue which can easily lead to driving users away from the site if we don't handle it carefully.
\n\nI think if a question is on-topic (i.e. it is about IoT), well-written (clear, not too broad or opinion based) and is likely to be useful to someone else, it is a good question and shouldn't be closed - after all, 'too easy' is not a close reason, and using 'off-topic' as a catch-all for something you consider simple is not appropriate in my view.
\n\nMeta Stack Exchange has a discussion on site-wide policy, which I'll quote for convenience:
\n\n\n\n\nThe answer to your basic question here, though, is that yes - easy questions are allowed and encouraged, When people type \"What is a regular expression\" into google, we want them to come here and find out. The individuals whose comments told you to google it or go somewhere else to learn it were not following the site guidelines.
\n
However, the issue I see as even more important is this: discouraging users with comments such as \"If I had enough rep to vote to close, I would. This sort of question does not help our site at all\" is likely to discourage other users from asking, which harms the site significantly. Imagine you were a beginner trying to learn more about IoT, and you come across the site and ask a (relatively simple) question. If I got that response, I highly doubt I would want to continue, and IoT cannot survive without new users.
\n\nIf you feel a question could be easily researched, I have no objections to a comment like this:
\n\n\n\n\nHave you read [insert reference page you just searched for], and does that answer your question or is there something you didn't understand here?
\n
What helps the site most isn't overly technical, theoretical questions that are difficult even for the experts to grasp, but the simple, practical things that lots of people are looking for the answer to. Failing to realise this could easily alienate enthusiasts, which is exactly the impression that this user had (which sadly drove them away from the site).
\n\nIn brief:
\n\nI have noticed that the more prolific users of this site tend to accept the first answer to their question quite fast. Now there is obviously nothing wrong in accepting any good and thorough answers that address the question properly and solve the issue at hand. It encourages the user who gave said answer to proceed to contribute to the site... and that is a good thing.
\n\nHowever, there is also a downside to the quick acceptance of the first answer - it discourages additional answers. A question with an accepted answer is likely to receive less further attention than one without, i.e. it doesn't show up in the unanswered list. It is therefore worthwhile to at least consider waiting some time before accepting an answer. On other branches of SE a grace period of a full day is discussed to give other people a chance to give another (better) answer.
\n\nSo, please do not take this post as an advise to not accept (as in never) well-written answers that fully solve the posted problem - just consider to wait now and then.
\n\nFurther reading:
\n\n\n", "Title": "How fast should I be accepting an answer?", "Tags": "|discussion|", "Answer": "I tend to accept answers relatively quickly, under certain criteria:
\n\nIf an answer meets those, I'm happy to accept straight away, and Stack Exchange guidance seems to consider this acceptable:
\n\n\n\n\n\n
\n- Don't hesitate to accept an answer that is well-written, suggests a good practice and works for you.
\n- Otherwise, even if there are answers that are good enough but that you're not entirely satisfied by, you might wait 24 to 48 hours to give other people a chance to give you a better answer. A question with an accepted answer isn't as likely to receive further attention as one without an accepted answer.
\n
The key bit in my mind is works for you. It's important to remember acceptance doesn't mean \"this is the best answer\", it means \"this is the answer that solved the author's problem (in their opinion)\". If an answer is detailed enough that I don't need any clarification from other answers, I'm happy to accept to say \"this solved my problem/query\".
\n\nOf course, I could turn this question on its head and ask if you believe that the question could be answered more completely, why not answer even if it is accepted? Even days and weeks after the question is asked, I believe it's only fair to read new answers and adjust the acceptance if the new answer is significantly clearer/more detailed than the previous accepted answer.
\n\nOn meta, however, I follow a different policy, since accepting an answer represents a more fundamental decision on site policy in a lot of cases. If there is one, unanimously upvoted answer after several days, I will accept, but in any other case I think it's best to simply leave questions with no accepted answer to give the community the choice.
\n\nIn summary:
\n\nI was recently discussing self-answers in the IoT chat with Ghanima, and I think it's a good idea to bring this to everyone's attention: if you've recently encountered a problem and found your own solution (especially a problem that made you think, \"surely someone else had this problem!\"), asking and answering your own question here is not just permitted, but encouraged!
\n\nBy doing this, you can help in multiple ways:
\n\npeople searching for problems that you've already solved can find an answer, which helps them
you already know the relevant information to add to your question, so you can write a question with a sharp, clear focus
other people will find the site more easily if we have answers to common problems
you might even get a better solution to your problem!
So, go forth and share your solutions that you think might be useful, and let's try to put a stop to this, all too common, problem:
\n\n\n\n\n", "Title": "There's no shame in self-answering!", "Tags": "|discussion|", "Answer": "I also agree with self-answering. But I would like to ask everyone to take time and write as detailed answers as possible.
\n\nI have seen some self-answers over EE.SE which was just a brief summary and the exact solution could not be reproduced based on that. While it is better than not answering at all, it may only give some unclear clues.
\n\nFor example this one, where some clear facts known by the OP are missing.
\n\nSo please do not forget to include such important points into your self-answers.
\n" }, { "Id": "106", "CreationDate": "2016-12-13T22:33:32.723", "Body": "Since I reached 1k I have an annoying all-time present suggested edits indicator stuck at 8.
\n\n\n\nIt's stuck at eight. At first I thought it might be the problem about my own edits being shown. ( Number of suggested edits seems to include own edits ) However, it did neither resolve itself with another actual edit I did since reaching 1k like it was when I reached 750 and opened up tag wikis. Moreover, 1k didn't give me any additional edit queues.
\n\nI have tried the usual culprits and opened the site with full reloads, cleared my cache and switched to incognito mode. When there are actual suggested edits it seems to start at eight, showing nine or more. If I clear my queue, I go down to eight again. It still works normally on ELU.SE.
\n", "Title": "Annoying suggested edits indicator", "Tags": "|support|status-completed|", "Answer": "Now that you have the \u201cmoderator tools\u201d a.k.a. \u201c10k\u201d privilege (1000 rep in private beta, 2000 in public beta, 10,000 (hence the nickname) on graduated sites such as ELU), the indicator shows the total number of pending reviews, not just the number of pending suggested edits.
\n\nFurthermore the suggested edit count deducts the edits that you've already reviewed, but the total review count does not even attempt to deduct the reviews that you aren't eligible for. That was deemed too expensive for the database. So the number you get is an overapproximation and is often uselessly wrong.
\n\nThere have been numerous complaints and suggestions of improvements over the years. See Review Count - Fix It or Lose It, Wrong posts number on Review section, Notification for reviews shows way too many, \u2026
\n" }, { "Id": "103", "CreationDate": "2016-12-13T11:46:32.277", "Body": "Recently, there was an IoT related question about WiFi modules on EE.SE.
\n\nWifi-enabled IoT boards with AP mode and SSL
\n\nThe question itself has been closed as primary opinion based, which it was actually. Also there was product recommendation request in it which is also off-topic on most of the SE sites.
\n\nIMO the problem with this question is that the OP ask too many things in a single question. For example the following questions can be quite useful:
\n\n\n\n\nAre there any counterpoints in using any of these modules? I mean, do they \"hang\" like the CC3000 without a good reason? Can they be left running for months at a time?
\n
As the OP has done a little research about the different boards. Asking which one of them is the most suitable for a long term application that requires high stability could be useful.
\n\nAll in all my question is:
\n\nIn what form can this question be asked on this site? What parts of it make it on or off-topic here?
\n", "Title": "IoT questions on other sites we can learn from", "Tags": "|discussion|site-scope|", "Answer": "While I don't think that this questions shows a lack of research its two major problems are being too broad and still somewhat opinion based.
\n\nFirst important thing to make it a better fit would be to focus on a single issue - reasonably scoped. Right now it is asking ten questions and that's not a good fit for the StackExchange system where it is preferred to post separate questions instead of combining many questions into one. Put differently asking separate questions helps the people answering to focus on aspects the feel most comfortable answering according to their specific knowledge and experience. In this particular example a comprehensive answer would require knowledge on multiple platforms. While it is clear that there are experts out there that possess that knowledge it limits the base of potential responders to just those. Multiple specific questions gives users with \"limited\" experience (for lack of a better word) a chance to contribute - which is something we should encourage.
\n\nWith regard to opinion based questions the helpcenter gives us some leeway if they are constructive - which seems to be the case here. I think that it is possible to have \"which plattform is better suited for a particular task\" answered mainly based on experiences over opinions and explain \u201cwhy\u201d and \u201chow\u201d. We just need to be careful to not let it slip down to a flame war about platforms but I believe that community moderation can put a quick and effective stop to such things.
\n\n... and there is of course the question which parts of the actual content are on-topic here but I will leave that to another answer.
\n" }, { "Id": "101", "CreationDate": "2016-12-12T19:10:50.567", "Body": "Where - and related: how - can we get more experts to join this site either now during private beta or later during open beta?
\n\nWe have to face it, IoT is a very wide field and contains myriads of different physical devices, technologies, protocols, systems, and so on. It is therefore imperative to have more experts join the site to extend and diversify the knowledge of our user base. More users could provide a different perspective and alternative solutions, thus increasing the number of answers per question (which is according to Area 51 quite low on our site).
\n\nSo, what can we do to entice more experts to contribute their knowledge here?
\n", "Title": "Where can we get more Subject Matter Experts?", "Tags": "|discussion|site-promotion|", "Answer": "I've done some further research around this question, because it is almost certainly the most important question of this beta.
\nI can summarise almost all the sources and opinions I've read into three simple words, though, despite this being an enormously complex topic: content is king.
\nThe article I linked is from an essay written by Bill Gates in 1996, and although his essay is primarily about monetising content from print media, this paragraph is particularly compelling:
\n\n\nIf people are to be expected to put up with turning on a computer to read a screen, they must be rewarded with deep and extremely up-to-date information that they can explore at will. They need to have audio, and possibly video. They need an opportunity for personal involvement that goes far beyond that offered through the letters-to-the-editor pages of print magazines.
\n
This theme keeps popping up again and again. An answer to Attracting experts to a young site with little expert content from Community Building Stack Exchange (which is definitely worth 10 minutes of your time to read) is similarly keen on the creation of good content:
\n\n\nFirst think about what you can offer:
\n\n
\n- Why should experts of any topic come to you?
\n- Why should they answer questions or discuss on your site?
\n- What is the advantage of being active on your site?
\nThe first two questions can be easily answered: They should come to you because you can offer extraordinary content concerning the topic. To build this extraordinary content, you have to create content, and spread this content.
\nContent is created by users who aren't present right now. So you have to create some content with the users who are already there.
\n
At the moment, we're not doing a bad job at seeding the content with promising questions and answers. However, I fear this will start to feel like a chore if regular users are having to post more and more questions just to keep the activity up, so I think the only option is to bring in new users with questions, especially ones that are more practical and likely to be searched for through Google.
\nIdeally, you may argue that we should reject easy questions or 'boring' localised practical questions. But, from a pragmatic point of view, this is a quick way to kill the site - organic traffic will come from (in the view of an expert) simple questions and troubleshooting problems, so embracing these questions is highly important.
\nWhat you mustn't mistake is the difference between accepting poor questions and simpler questions - unclear questions should still be closed, and poorly formatted questions should still be edited - but we should make an effort to save content which may be useful to others rather than turning it away.
\nThe key points are:
\ngenerate great content which can be found on Google by experts and novices alike
\nhelp new users post content that is high-quality - don't compromise and allow poor content to remain
\nan empty site, however great the older content may be, attracts no-one!
\nI recently asked a question about a technical feature of Ubuntu Core (and specifically its package manager, Snappy). Some users voted to close this, so I think we should start a bigger discussion about whether these questions are fundamentally on/off-topic to help define the scope of the site.
\n\nA good point of reference in my opinion is Stack Overflow. Their help center specifically allows questions related to:
\n\n\n\n\nsoftware tools commonly used by programmers
\n
Should we consider a similar policy for this site, where questions about tools commonly used for IoT would be on-topic? Would this make the scope too broad or would excluding these make the site too narrow in its focus?
\n", "Title": "Are questions about software/hardware primarily related to the Internet of Things on-topic?", "Tags": "|discussion|site-scope|", "Answer": "Software and hardware tools used for IoT should be on-topic here as long as the particular use case is directly related to IoT.
\n\nThere will be an overlap with other branches of SE these tools will often be used for other non-IoT applications as well. This overlap is unavoidable and a redirection to other sites may be prudent if the question could be answered in a more general sense that exceeds the realms of IoT.
\n" }, { "Id": "97", "CreationDate": "2016-12-12T12:36:39.580", "Body": "Has the question about monitoring IoT devices on plane been auto-deleted? Here is the link to the original post.
\n\nI assume this post was removed because the system will automatically delete any question (and its answers) or answer with a negative score when its owner\u2019s account is deleted.
\n\nSo I know the user got deleted, I don't know it's score, but it was closed so guess it might have been negative and I guess that took the question down the drain.
\n\nI think it wasn't to bad an edge question to test our scope with. Can we get it back? Maybe have Community own it.
\n", "Title": "Where's the question about monitoring IoT devices from a plane?", "Tags": "|support|deleted-questions|", "Answer": "Yes, the question was originally removed because of the down-votes when the user requested their account be deleted. The handling of that question was unfortunate; I restored the post.
\n\n\n\n\nUnnecessary snarkiness in the comments. This is not a welcoming site.
\n
The user is right. For a consumer-level question, how is this NOT a legitimate inquiry? It takes a certain level of technical snobbery to assume that how networks work or how these devices work is just an innate knowledge everyone is born with.
\n\nThat aside, let's be mindful that it is really easy for a community to become insular and unwelcoming when a well-meaning question is treated like it's beneath them to ask. The user was embarrassed for having dare asked such a \"retarded question.\" So they left.
\n\nLet's not do that.
\n\nIt is helpful to remind ourselves on occasion to keep things friendly and constructive and to be tolerant of others who may not know everything you know. That's just good advice in general.
\n" }, { "Id": "86", "CreationDate": "2016-12-09T16:53:35.570", "Body": "I noticed that we have both cameras and digital-cameras in our inventory of tags. I don't believe they are both necessary... I propose synonymizing them. The only kind of camera broadly used today is the digital camera, and in the world of IoT, if someone is speaking about a camera, it will definitely be a digital camera.
\n", "Title": "Merge [cameras] and [digital-cameras]", "Tags": "|support|status-completed|", "Answer": "No. It's unfortunate that this action appears to already have been taken, as it was probably mistaken.
\n\n\"digital-camera\" tends to refer devices that are specifically alternative to film cameras, which generally means handheld and human operated. These would only infrequently be on-topic in an IoT context, and having lots of occurrences of that tag in external searches is likely to attract questions about general point-and-shoot camera support that have nothing to do with IoT.
\n\nIn contrast, the kinds of cameras that are on topic in an IoT setting - streaming, recording, recognizing - while implicitly digital are essentially never referred to with that adjective. Adding it is quite unnatural.
\n" }, { "Id": "29", "CreationDate": "2016-12-06T21:16:33.517", "Body": "\n\nAll my icons for network questions apear as the little 3D icon...? Is anyone else having this problem?
\n\nSeems like this is not a problem just with the IoT beta (May have been caused by it?)
\n\nbecause it seems to have happened everywhere
\n", "Title": "All icons are broken", "Tags": "|bug|status-completed|", "Answer": "All Stack Exchange site logos are showing up as the 3D Printing one REDUX:
\n\n\n" }, { "Id": "21", "CreationDate": "2016-12-06T20:21:45.157", "Body": "I actually managed to screw this up in a new and exciting way as we moved favicon generation around. Due to caching on dev, we missed it. It was a grep for favicon.less, but turns out our base .less includes it via: @import "favicons/favicons", which didn't show up in my grep of "places to fix".
\nA fix is building out now.
\n-- Nick Craver \u2666
\n
Some posts I see here are lower quality. However, if I downvote, I'll lose reputation and lose privileges.
\n\nIs there a way for me to express my opinion on this new site without the loss of rep?
\n", "Title": "I'm afraid to downvote because I will lose reputation", "Tags": "|discussion|support|", "Answer": "If the post is low quality, you've the following possibilities:
\nAnswers: If other users share your opinion and the vote has zero or negative score, you can flag it as 'very low quality'.
\n\n\nThis answer has severe formatting or content problems. This answer is unlikely to be salvageable through editing, and might need to be removed.
\n
If it has positive score, it's worth to comment on the post explaining your thoughts, so the author can improve the post (you can also suggest the changes) and other users can reconsider their votes, also this may alert other users who can share your opinion.
\nQuestion: Downvotes on questions are free. You can also flag them as primarily opinion-based, off-topic or as unclear.
\nEither way, you should not afraid of down voting the post, because the owner of the post will lost twice as that (2 reputation). It is actually a moderation privilege, and it comes with the cost of 1 reputation which is taken away from you to avoid any abuse, so use it wisely.
\nSee: Help Center > Privileges > Vote Down help section:
\n\n\n" }, { "Id": "7", "CreationDate": "2016-12-06T18:38:31.237", "Body": "When should I vote down?
\nUse your downvotes whenever you encounter an egregiously sloppy, no-effort-expended post, or an answer that is clearly and perhaps dangerously incorrect.
\nYou have a limited number of votes per day, and answer down-votes cost you a tiny bit of reputation on top of that; use them wisely.
\nWhat happens when I vote down?
\nWhen you vote down, you are nudging that content "down" the page, so it will be seen by fewer people. Voting down answers is not something we want you to take lightly, so it is not free.
\n\n
\n- Downvotes remove 2 reputation from the post owner.
\n- Downvotes on answers remove 1 reputation from you, the voter.
\n- Downvotes on questions are free.
\n
Unable to find the general chat room for this new site and thus assuming it does not yet exist:
\n\nHow should our main chat room be named? It is custom to use a clever play of words on the topic of the site.
\n", "Title": "How should this site's general chat room be named?", "Tags": "|discussion|chat|", "Answer": "The Internet of things are also referred to as \"connected devices\", so room with \"connected people\" using \"connected devices\" would be great.
\n" } ]