Do you want to explain this closure?

meta
42

You say, er… type that like it’s a bad thing or something.

If a site doesn’t grow at least a little, it stagnates.

3 Likes
43

You ain’t wrong

  • Search and browse 10k most recent messages

  • 10 service integrations

Most people don’t seem to care that only 10k messages are retained because most of the stuff typed in a chat is so ephemeral anyway that retention of history is a non-issue.

You see the tension: retaining full history is more complex, and in chat, actually unnecessary … even unwanted, as in “forgetting as a feature”.

4 Likes
44

Same, For the last few weeks, Firefox mobile has been crashing in threads that have a lot of non-text stuff. Gifs are especially prone to crashing FF on mobile.

45

Huh, totally misread the title. I was expecting a thread on programming closures.

5 Likes
46

Badge name: Discourse Can’t Handle Me.

13 Likes
47

I was wondering whether it would be programming closures or some new kind of dress fastener. Seriously.

5 Likes
48

Link bait?

4 Likes
49

When I write the screenplay for the Fahrenheit 451 remake, Captain Beatty is totally going to say, “Forgetting is a feature.”

Also, if anyone acts a jackass it will just get screen-shotted anyways.

3 Likes
50

It’s funny, we are a remote development team in 8 different timezones, and over the last 4 years we’ve moved from three different chat systems:

  1. HipChat
  2. Kato.im
  3. Slack

In each case we threw away all chat history, and never needed to refer to the historical chat again.

(To be fair, we are rather disciplined about keeping “significant” stuff in our internal Discourse. I understand tears in rain.)

3 Likes
51

OK, after some internal discussion we think 200 might be too low as a default for private/personal messages, so we will bump this to 500 default.

As always, site owners can override either of these numbers as they see fit.

4 Likes
52

Bingo! If people thought that their communications were disposable they’d be in a chat!

Hmmm. But they’re not!

Hmmmm… I’d better tell them to stop talking, and that their communications should be considered disposable, and hie thee to a chat-room, go!

2 Likes
53
5 Likes
54

I would hope your internal biz chats are considered the intellectual property of the employer. Discussion on a public web-pages with no access restrictions to read and minimal requirements to allow write would seem to be different user stories.

Unless you mean to imply that we are all now Discourse employees.

http://img.pandawhale.com/post-19259-so-I-got-that-going-for-me-whi-CKYI.gif

6 Likes
55

Also, it is hilarious that this is the last reply in Questions

Hey, I got an idea! How about a feature that limits you to 10,000 replies? :laughing:

8 Likes
56

Hmm, not really. It’s more of a meditation on the meaning of a topic that has more than 10,000 replies. pssst, that means it’s a chat

2 Likes
57

Oh if it’s no difference then send me an invite to your slack.

1 Like
58

You’re welcome to post on http://meta.discourse.org any time you want; same difference.

59

I tried the search function and can’t find your salary. How much do you make?

60

At the moment I pay myself $0/month from Discourse. Not really sure where this is going, but I just got a “you’re posting too much in this topic” warning from Discourse which is probably correct at this point, so I’ll bow out.

4 Likes
61

You just told us our communications were disposable, and then you laughed at us.

You’re an awesome tech-writer, an incredible programmer, but you fall short in the public communications realm.

4 Likes