Hello

@daviesgeek There could be a version 10.5 of a lot of things. Mac OS X 10.5 is Leopard. BBEdit 10.5 is not. Bad alias.

@DanielLawson Umm...no...did you check the tag room?

@daviesgeek Clearly I did not. I'm just weighing in with my uneducated opinion.

@daviesgeek WRT this one, you didn't ask me, but I'd say if you make a one-word edit, particularly if it's removing unnecessary fluff or improving/clarifying , that's not a problem. If you make another one-word edit a week later, that's not a problem either. A batch of one-word edits, particularly when the edit removes something that isn't clearly out of place or when the post needs more work than that, is problematic.

@DanielLawson Glad you took it upon yourself to answer. Thanks! I will try to keep those edits to a bare minimum :-)

@DanielLawson :-)

@bmike @DanielLawson @JasonSalaz I know some of you saw this question, but I was wondering why it wasn't closed yet, as it is a duplicate. Was there some reason it hasn't been closed yet?

@daviesgeek Perhaps it's open because not enough people have cast votes for it to be closed?

@bmike exemplary of confusion around MacFUSE, "… tried a few versions but have been unable to find … work for my system." — apple.stackexchange.com/q/48196/8546

@DanielLawson Yeah, but bmike edited it!

@daviesgeek Editing ≠ voting to close

@DanielLawson True, but he clearly read the question, and I would have thought he would have notice the 3 close votes on it...

I'd also say that @JasonSalaz saw it too, but that was clearly before he was a mod.

So 3 people voted to close it. I'm not one of them, and neither is bmike

One is Jason, one is me, and the other is unknown.

However, I'd guess it's CajunLuke

fair enough

Maybe I need to stay out of your tag room. The state of tag space just gets me grumpy

:-) i just want to fix it.

So...about the duplicate question.....

What are you thinking about it?

bmike and Jeff Atwood convinced me a while ago that duplicate questions usually aren't really a problem. I've stopped voting to close them, for the most part.

There are exceptions, but asking a question differently triggers different search terms, etc.

I would say that this one is pretty clearly a duplicate...although bmike's been doing Jedi mind tricks on me too

Now in this case, I might be swayed, though. There's really not much difference at all.

I know! My point exactly.

If I were a regular user, I'd vote to close. I don't think it needs mod superpowers, though, so I'll wait for two more close votes. Or one more, for that matter; I'd be okay being the fifth vote, but not preemptively closing it as the fourth vote.

@DanielLawson Ok. Just so long it's on your radar.

@daviesgeek Thanks for putting it on my radar.

Hi Nathan

@daviesgeek They are not duplicates.

Should it get closed, I would be inclined to re-open it. I do see it has garnered three close votes - but it hasn't reached a point where any moderator needs to take action

@DanielLawson Here comes the jedi with his (hopefully smooth argument)

Look at the original versions of both questions.

One wants a solution for a stealthy command line tool to avoid countdown timer and sounds.

The other wants to schedule time lapse.

We don't code questions that happen to share the same answer.

We do start closing 100% totally verbatim questions when we get a dozen versions of the exact same thing. The dozen is a guideline for moderators - not a hard and fast rule. Philosophically we will want to code questions when they are causing noise and preventing people from providing good answers.

In this case - closing one or the other would be shoehorning a time lapse question into a surveillance question. Just because the OP thinks terminal is the solution - these are really similar but totally different needs. I hope over time several good answers arrive for both in terms of apps, terminal commands - so keeping them open seems obvious to me to be in the interest of the site.

@bmike that's a good differentiator. I drafted an edition to include stealth in the title.

@GrahamPerrin Thanks - I took a look and refined the edits to leave one alone and really shorten the others.

How do they look to you now?

@bmike I'm sold. Thanks.

@bmike thanks both look fine, I'm looking at the titles alone. Keyword stealth, as you noted.

@GrahamPerrin Yes - I wanted to be as light on the edits as possible.

The one really doesn't care about command - the other can sit in that space.

@DanielLawson :-)

Did anyone else wake up to hard precipitation today? Brrrr.

Not here, but it's potentially coming! :-(

@GrahamPerrin Let's bring the fuse conversation back here since it's clearly something not to do with tags - and more to do with how people use that software which is open source, many versioned, sometimes breaks things bases on your base OS or even the version of OS you run at one point in time ;-)

@bmike at wake a few hours ago, just grey. Now approaching 21:00 and it's blowing vulgarity right up the road …

@bmike Ok. read your statements and I agree. (another jedi mind trick)

@bmike yeah here is better for most of the MacFUSE and FUSE chat.

@DanielLawson Yah.

For a moment, forget everything I said about MacFUSE. If you saw the tag wiki entry for FUSE (or Filesystem in Userspace) for the first time, how would it strike you? apple.stackexchange.com/tags/filesystem-in-userspace/info

@bmike @GrahamPerrin I think the title should include "command line" as well. Currently, it doesn't have that and I think it needs it.

@daviesgeek big +1

@daviesgeek That's exactly the sort of substantive edit that I'm happy to be seeing more of from you. You've been doing far less batch editing "How to" to "How can I" and more like that. And if you are making a substantive edit, please, please do also throw in the style edits you want to see for that post (how to -> how can I, etc).

@DanielLawson Ok. I was leaving when I said that, but I shall take a look at it

Done. @DanielLawson @GrahamPerrin How's that look now?

@DanielLawson @bmike Now this question I see as a dup.

@daviesgeek looks fine to me, thanks.

@GrahamPerrin Cool!

@daviesgeek Agreed. Keyword search apple.stackexchange.com/search?q=UIScrollView finds rubber band, which is bouncy; the OP could/should have contributed there. A vote up for your comment in the ~dupe.

@GrahamPerrin Oh. You don't have enough rep to cast a vote.

:-)

@daviesgeek 's OK. I'm patient :-)

Hehe

I could vote down the question, but I wouldn't be so harsh to a newcomer who is experiencing bounce sickness! Simple closure and reference to the matching question is the nicer way for them to learn.

G'night all

@GrahamPerrin I know. I rarely downvote, especially on dups. If it's a dup, it means that there's more than one person that was having that problem, so I don't downvote

@daviesgeek typo in the subject line, apple.stackexchange.com/q/18160/8546 "stealthly". FWIW I reckon the most recognisable expression will be "stealth photography".

I'll lave it with you.

Leave it, even. I need new spectacles, and sleep!

@GrahamPerrin Darn! I thought it looked slightly wrong!

Sorry!

Fixed

@daviesgeek Well - even that isn't really a duplicate.

However it needs help.

It asks the disable question as a drive by introduction to the real issue - how do I find useful things.

I'll edit out the dupe and leave that remaining unique question (until we go find if that is dupe too...)

Ok.

@daviesgeek What do you think now?

versus apple.stackexchange.com/posts/49956/revisions

@bmike OK. Better now. Not a dup.

Yet another bmike Jedi mind trick.