Atualização automática de tópicos antigos em uma categoria

[sam (Sam Saffron)]

Em certas categorias, faz sentido impulsionar automaticamente tópicos antigos em intervalos regulares.

• Em categorias de compra/venda, pode ser útil impulsionar periodicamente a visibilidade enquanto o tópico estiver aberto e o item ainda estiver à venda.

• Em categorias de #suporte, pode ser interessante impulsionar tópicos antigos caso tenham sido esquecidos.

Até agora, a única forma de aumentar a visibilidade era “editar” a última postagem de um tópico ou publicar uma resposta com bump.

Ambas as soluções não são ideais.

Acabamos de adicionar uma nova configuração de categoria chamada: Número de tópicos abertos para impulsionar automaticamente por dia. Por padrão, está definido como 0 e nenhum impulsionamento automático ocorre. No entanto, você pode aumentar esse número (no meta, configuramos para 3 na #suporte).

O que isso faz?

SE existir um tópico não fechado, não resolvido, visível, não arquivado, não de descrição da categoria e não fixado que tenha sido impulsionado há menos de 24 horas.

O sistema buscará os N tópicos impulsionados mais antigos e os levará para a primeira página. O processo impulsionará no máximo 1 tópico a cada 15 minutos e possui limitação de taxa, de modo que realizamos apenas N impulsionamentos por dia (você define N).

[Pad_Pors]

such a nice and needed feature! thanks for developing this

---

@sam

every 15 minutes

1. This seems very fast, especially if a forum doesn’t have such dynamics.

   can this time be tuned based on the the number of N: e.g. time_interval = 24hours/N, so that there’s a uniform dynamic for old topics during the day?

2. Also if the topic is older than some months, there exists this system-notification which tells users that “the topic is old, and are you sure you want to answer it?!”

   this makes users a little bit confused: from one hand admins bumped the topic to make it more visible and “get replies”, and from the other hand system is telling users “do not contribute”!

[Bas (Bas van Leeuwen)]

Really nice idea!

Will it be indicated somehow that it’s bumped?

[david (David Taylor)]

@Bas

Will it be indicated somehow that it’s bumped?

I also think this would be good - it’s a bit confusing to see super old topics at the top of ‘latest’. How about adding a ‘small action’ whenever the topic is bumped. Something like:

If the most recent post in the topic is an auto-bump small action, edit it rather than creating a new one. That way we keep noise to a minimum.

[pfaffman (Jay Pfaffman)]

Yesterday I lamented re-starting a thread that was over 6 months old (I think because it was in recommended topics), not realizing that it was over 6 months old. Several people participated in a thread that I thought was current, but it wasn’t. I was embarrassed that I’d cranked up the topic again.

Now when I go to latest, I’m recommended https://meta.discourse.org/t/custom-print-style-should-be-added/14921/12 , which is from April 14. (And it’s on almost the same topic that I replied to errantly yesterday) And when I look at it in Latest I see that there’s “activity” 14 minutes ago, except, there’s really not activity in over 3 years.

It was confusing enough when Suggested would send me to long-dead topics that don’t need to be revisited, but now I can’t tell from Latest whether I should visit a topic.

I’m having a hard time understanding the value of this feature.

[sam (Sam Saffron)]

I like the idea of the auto bumped small action, not sure how @codinghorror feels about

@Pad_Pors I have a nice idea of how to space out the bumps, will implement tomorrow

[sam (Sam Saffron)]

Having these forever open support topic is a problem, I like that this triggers us to clean up, an alternative I guess is just to auto close all old support topics, but it is a bit more drastic

[pfaffman (Jay Pfaffman)]

@sam

Having these forever open support topic is a problem,

That makes sense. It seems that topics are more likely to be closed lately, so perhaps this will be less annoying once that clean-up is done. It seems rather painful (for me, anyway) until that’s done, though.

Perhaps it would be safe to auto-close stuff that’s, say, a year or two old?

[codinghorror (Jeff Atwood)]

@pfaffman

It was confusing enough when Suggested would send me to long-dead topics that don’t need to be revisited,

First of all there is a cap of one year on suggested so your statement isn’t correct.

Second, it is completely valid to continue the same discussion later if it was not resolved. Of course you did not know it was resolved, which is understandable since you can only trigger “real” printing mode from a keyboard shortcut… which is quite undiscoverable…

Proceed on auto-bumped small action @sam, this makes sense, because “invisible magic” always leads to confusion.

[barreeeiroo (Diego Barreiro)]

Really nice feature

One suggestion: Add integration with discourse-solved plugin and add the ability to choose non-closed and/or non-solved posts

[sam (Sam Saffron)]

This resolves the 2 big issues with the initial system:

FEATURE: adjust autobump system

1. We spread out bumping through a 24 hour period. If you are autobumping 4 topics in a category, then it is one per 6 hours.

2. We add an auto bump message at the bottom of the topic so you can tell why it floated to the top

@barreeeiroo I love the idea of integrating with solved … we need to create a hook for it in core though, will work on this now!

[sam (Sam Saffron)]

Per:

FEATURE: support filter_auto_bump_topics event

And:

FEATURE: if auto bump is enabled, do not bump solved

This now integrates with Discourse solved and will not bump solved topics.

@eviltrout / @tgxworld not sure if you ever needed to do this before, but this seems like the best pattern for composable filters I can come up with without adding a proper filter interface (or leaning on the only used in one plugin, filter interface I added years back)

  on(:filter_auto_bump_topics) do |_category, filters|
    filters.push(->(r) { r.where(<<~SQL)
        NOT EXISTS(
          SELECT 1 FROM topic_custom_fields
          WHERE topic_id = topics.id
          AND name = 'accepted_answer_post_id'
        )
      SQL
    })
  end

[Pad_Pors]

is the system avatar needed in the topic list?

it doesn’t give a good feeling to meet a machine-type avatar in the first page, also it doesn’t make sense to change this avatar to a more human-based image.

[sam (Sam Saffron)]

Yeah I feel the same, I am not sure what avatar to give it though… a simple fix here would be assigning meta system user a nicer avatar.

Maybe Baymax works better, he is certainly softer.

We could also let discobot do the bumping if it exists … which may make more sense here. Will change that tomorrow.

[Pad_Pors]

@sam

Maybe Baymax works better, he is certainly softer.

would be awesome ! knowing that his duty is to take care of the community health!

[tophee (Christoph)]

Earlier today, I wanted to try this new feature and set our support category to 3 topics per day. About 20 minutes later, I realized that this was not a good idea because we have plenty of formally unresolved but de-facto resolved support topics so I turned it off again by setting it to 0 topics per day. However, at the time of writing, we’ve nevertheless had ten (!) old topics bumped.

Am I misunderstanding how this is supposed to work or is this some kind of double bug (it’s not obeying the max of three topics per day and it’s ignoring that I turned if off before the first topic was bumped. We’re on v2.1.0.beta2 +274

[sam (Sam Saffron)]

We had some issues with this earlier this week, be sure to be on latest … 324 or up…

@tophee

plenty of formally unresolved but de-facto resolved support topics

Is there value in keeping these open forever?

[tophee (Christoph)]

@sam

Is there value in keeping these open forever?

No, but:

@tophee

few users understand that (or how) they can create linked topics if they want help on a similar issue as in the closed topic

So I’d prefer to keep most of them open until it’s easy for people to reply to a closed topic.

Also, we still have a bunch of uncategorized topics from migrating and categorizing those has priority.

[Bas (Bas van Leeuwen)]

So this 2014 topic just got bumped:
https://meta.discourse.org/t/is-there-a-way-to-use-without-an-email-server/15650

Doesn’t feel very useful
I’d put in a limit on the original posting date, you don’t want to be boosting years old posts.
E.g. only bump posts from the past week or so.