Timeline for Should we edit the sidebar text on the ask page?
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 16, 2017 at 16:43 | history | edited | CommunityBot |
replaced http://meta.hardwarerecs.stackexchange.com/ with https://hardwarerecs.meta.stackexchange.com/
|
|
| Mar 19, 2016 at 0:22 | comment | added | ArtOfCode Mod | cheers, @Shog9! | |
| Mar 19, 2016 at 0:18 | comment | added | Shog9 | meta.hardwarerecs.stackexchange.com/questions/421/… @Art | |
| Mar 2, 2016 at 23:31 | history | edited | ArtOfCodeMod | CC BY-SA 3.0 |
deleted 132 characters in body
|
| Mar 2, 2016 at 23:30 | comment | added | ArtOfCode Mod | @Shog9 Yes. Experience speaks again :) Editing that in. (Done) | |
| Mar 2, 2016 at 23:28 | comment | added | Shog9 | So you want folks to list all their requirements for a single, specific piece of hardware, @Art? | |
| Mar 2, 2016 at 20:05 | comment | added | ArtOfCode Mod | @Shog9 There's an important distinction between them, though it may well be unclear. (2) is about knowing whether you need a frobble or a blobble; (3) is about the exact degree of pink your frobble needs to be and how far it can jump to the nearest millimetre; (4) is about if you need both a frobble and a blobble, you should ask about them separately. I did think of putting something like that in there, but it would have been rather long. What else could we do? | |
| Mar 2, 2016 at 18:27 | comment | added | Shog9 | Bullets 2,3 and 4 are all pretty similar, @Art. | |
| Feb 26, 2016 at 22:42 | history | edited | ArtOfCodeMod | CC BY-SA 3.0 |
added 103 characters in body
|
| Feb 26, 2016 at 22:39 | vote | accept | ArtOfCodeMod | ||
| Mar 19, 2016 at 0:21 | |||||
| Feb 26, 2016 at 22:35 | history | edited | ArtOfCodeMod | CC BY-SA 3.0 |
deleted 233 characters in body
|
| Feb 16, 2016 at 22:16 | history | made wiki | Post Made Community Wiki by Andy | ||
| Feb 16, 2016 at 21:41 | comment | added | Shog9 | It looks like you're trying to establish a dialog. However, the obvious way for the reader to respond is to just post their question, so that's kinda wasted - you're better off getting straight to the point: 1) Must want specific hardware; 2) list specific requirements 3) show your research 4) one hardware request per question. Last three lines are meta links. Six lines of dense information a conscientious asker needs to know instead of 8 lines of dialog. | |
| Feb 14, 2016 at 17:15 | history | edited | ArtOfCodeMod | CC BY-SA 3.0 |
added 378 characters in body
|
| Feb 10, 2016 at 22:05 | vote | accept | ArtOfCodeMod | ||
| Feb 26, 2016 at 22:39 | |||||
| Feb 5, 2016 at 7:54 | comment | added | ArtOfCode Mod | Nice one. That's definitely a better wording | |
| Feb 5, 2016 at 6:45 | history | answered | Andy | CC BY-SA 3.0 |