I think allowing hardware is a good idea, for several reasons:
The scope of this stack is already narrow. If we narrow it down too
far there won't be enough activity to sustain it.
There will be many questions that relate somewhat to hardware and
you'll end up with lots of meta discussion over time as to what
kinds of hardware questions are okay and what ...
I would say yes. This site is intended both for users of e-book and e-reader software as well as publishers creating content for e-books and e-readers. Therefore, at least from a broad point-of-view, programming questions should be on-topic.
This question may be okay if it remains limited and well vetted in its responses (and possibly 'locked' if it starts accumulating runaway answers) — but let's set that aside for a moment to avoid using Community Wiki as a way to make these questions somehow "okay".
Community Wiki was not designed to solicit crowd-sourced lists of stuff. The ...
I would propose that asking for shopping options for a specific ebook or author be listed as off-topic for the site.
Specifically, asking for the cheapest option and/or queries where a simple search can replicate any answer. (e.g. Where can I buy "Hot book X" for less than $8?)
On-topic would be how to understand the various drm or quality / features of ...
This is not product recommendation question, but specific question about hardware failure. The reason why most sites don't allow recommendation questions is independent from whether hardware questions should be on-topic here.
But answering your second concern, I think that such hardware questions should be on topic. They are allowed on Android SE, for the ...
For the immediate future we are being more accommodating so we can see what questions are coming in. When we have enough of a sample size we can better decide what will be in scope or out.
That said, one of the topic areas of this site is ebook authoring, which by extension likely includes production.
I'd like to nominate Jason Down:
In the short time since E-books launched, he has gained 988 reputation*.
He is an active member of E-books.
He is also an active member of Stack Overflow.
Nominee response: I accept the nomination.
* I realize that reputation isn't everything, but it does show that many users found his answers useful.
Stack Exchange is a place to get answers to specific questions. Not to advance agendas or advocacy.
Getting rid of DRM is an agenda.
Asking about pros or cons of DRM, so people can make their own mind about whether DRM is good or bad, is a good SE post.
The only time an answer that advocates against DRM is appropriate is when:
It is answering a question ...
Anytime you find yourself answering the same question over and over and over and over … it's blog post time.
Please read: Does this site have a chance of succeeding?
I hate to sound so trite, but please stop watching (and interpreting) these numbers so literally. Watching numbers is our job. Your job right now is to host and encourage the best ...
These two features should be somewhat mutually exclusive. Locking a post is designed to save an otherwise good post that has started attracting a lot of "me-too" answers (typically when a post goes viral). But locking a post (or turning it into a community wiki) should not excuse a post that otherwise would have been closed. If a post should be closed, it ...
If you think it's appropriate, you're probably a good judge of that. There's no inherent problem with copying and modifying tag wikis from existing sources. If some other members find the tag wikis you create less helpful, then they can flag them or edit them themselves.
I'm not suggesting that we start copy-pasting en masse from Wikipedia (primarily, ...
I would like to nominate Nathan Osman:
Has been instrumental in setting up E-books.
Has moderator experience on StackApps
Has a cumulative reputation of 70K+ on the various Stackoverflow/Stackexchange sites.
Nominee response (Unable to edit himself at this time): I accept the nomination.
I'd say the proper thing to do is to check with a moderator on that forum first. This site is sort of competition to that site and they may not appreciate us advertising on their forum (it may be considered spam).
We're sorry to lose your valuable contributions. I hope you'll reconsider rather than rage-quitting.
I'll offer a few points in response to your comments.
The Deleted Post
First, for those who can't see the post I deleted (which is nearly everyone), here it is:
Oh, gosh, I hate to break the news to you, but Stack Exchange has lots
of rules about the types ...
While I like (and upvoted) Chad's suggestion of The Prologue, considering the fact that chat is part of the long tail of things you learn about after getting started on the main site rather than what you get up front, I thought maybe The Epilogue would be more appropriate. For some reason that didn't have the right ring to it*, but the more common parlance ...
In my opinion ebook-readers is an ambiguous tag. I think we should blacklist it and replace it by ebook-devices for the hardware devices and ebook-viewers for e.g. epub reading software on Android or PCs.
It would be nice to have a hardware tag reserved for questions that actually deal with hardware questions like "The touch screen of my reader does not ...
I think they are both shopping list questions.
The Stackexchange position I think is best explained in this question on meta stack overflow.
The main issue here for us is
They are open-ended; there is never one perfect answer to them.
However I think we probably should be a bit more lenient that say Stack Overflow as some questions ask for a product ...
Let's tackle one problem at a time. Right now, our problem is to collect a good set of expert answers to ebook questions. It's way too early to worry about keeping out hoards of authors. But when authors do stop by to ask questions that don't quite fit in or when they don't get helpful answers, feel free to point them to Writers:
Questions on these ...
The Ebooks Stack Exchange is not a search engine or a collection of links. It's okay to add links for further reading, but this site was created to build a definitive collection of answers to ebook questions.
The folks here will work hard to curate this collection of knowledge, so when someone comes looking for answers through search, the last thing we ...
I would nominate Anthon. He seems to both be:
Active in user level moderation via editing
Active in user level moderation via reviewing
Very knowledgeable about subject matter
Reasonably active on meta
I accept the nomination, as indicated on the Moderator Pro Tempore moderator page, by editing this answer.
I think it will depend on the context of the HTML5 question, but in many cases, yes. For example, many web-based reader software, such as the Kindle Cloud Reader and the Kobo Cloud Reader are developed in HTML5.
There is a decent blog here about the relevance of HTML5 (and EPUB3) in the future of electronic reading.
Quick intro excerpt:
I would be inclined to let the answer go, unless a competent legal authority was able to determine that the practices contained in the answer were clearly illegal. There is a tremendous amount of misinformation, speculation, rumor, unsubstantiated claims, etc. floating around the internet regarding copyright law, and I would hate to see us deleting answers ...
I would like topics related to the structure of ebooks to be on topic and included in this stackexchange site. They're intrinsic to the books themselves; and the devices, the formats, etc. are all on topic.
By sharing our understanding of the structures, how to create, modify, and use them, we may help people to publish and repair ebooks.
Current SE policy discourages link-only answers and require the answers to be self-contained, so that they remain valid after the external link is no more available.
Links in answers are welcomed, as long as they provide additional reference etc. (so no ads). You are therefore free and welcomed to put links to external helpful resources, as long as they are ...