Sometimes merged topics, such as this one just won't load
Why?
because it's merged with another topic
So my suggestion, is that if we went to a old non merged topic (that you cannot access), it will redirect to the actual topic

Support, those 403s are confusing.

Support, I actually thought my post had been dustbinned after the merge, but Pads said otherwise.

bump

I'm a little upset now as I was thinking of making this exact same suggestion, but I was certain there was a dupe somewhere out there. Sadly there isn't, so I'll just have to live with this regret now.

Merged topics can be incredibly annoying as it requires third party programs to view the original topic and find where it was merged to. I normally rely on ancient topics that are closed from dupes, so I can crowd-source the dupe finding to past forumers. However, whenever a topic with a lot of dupes gets merged, all those links become dead, and it becomes way more difficult to find the correct dupe.

fdreerf wrote:

I'm a little upset now as I was thinking of making this exact same suggestion, but I was certain there was a dupe somewhere out there. Sadly there isn't, so I'll just have to live with this regret now.

Merged topics can be incredibly annoying as it requires third party programs to view the original topic and find where it was merged to. I normally rely on ancient topics that are closed from dupes, so I can crowd-source the dupe finding to past forumers. However, whenever a topic with a lot of dupes gets merged, all those links become dead, and it becomes way more difficult to find the correct dupe.

wait what kind of third party program can be used to view dustbinned topics?

*not getting why this isn't implemented yet*
this means support in speak terms

Scratchy697 wrote:

wait what kind of third party program can be used to view dustbinned topics?

All I'm allowed to say is that it exists.

Scratchy697 wrote:

wait what kind of third party program can be used to view dustbinned topics?

I remember seeing it before, but I don't remember where it is.

Maximouse wrote:

Support, those 403s are confusing.

Support, too.

GachaN0nsense wrote:

Support, I actually thought my post had been dustbinned after the merge, but Pads said otherwise.

Support, too.

fdreerf wrote:

I'm a little upset now as I was thinking of making this exact same suggestion, but I was certain there was a dupe somewhere out there. Sadly there isn't, so I'll just have to live with this regret now.

Merged topics can be incredibly annoying as it requires third party programs to view the original topic and find where it was merged to. I normally rely on ancient topics that are closed from dupes, so I can crowd-source the dupe finding to past forumers. However, whenever a topic with a lot of dupes gets merged, all those links become dead, and it becomes way more difficult to find the correct dupe.

Support, too.

Bump

NanoPIex wrote:

Maximouse wrote:

Support, those 403s are confusing.

Support, too.

GachaN0nsense wrote:

Support, I actually thought my post had been dustbinned after the merge, but Pads said otherwise.

Support, too.

fdreerf wrote:

I'm a little upset now as I was thinking of making this exact same suggestion, but I was certain there was a dupe somewhere out there. Sadly there isn't, so I'll just have to live with this regret now.

Merged topics can be incredibly annoying as it requires third party programs to view the original topic and find where it was merged to. I normally rely on ancient topics that are closed from dupes, so I can crowd-source the dupe finding to past forumers. However, whenever a topic with a lot of dupes gets merged, all those links become dead, and it becomes way more difficult to find the correct dupe.

Support, too.

I heard these types of posts are unconstructive?

Scratchy697 wrote:

-something unconstructive-
I heard these types of posts are unconstructive?

And yours is too.

Support, if a third party program can do it, so can Scratch.

Bump

PkmnQ wrote:

And yours is too.

I believe that Scratchy is the OP, on a different account as they moved, so technically since its their topic they can ask questions to users such as nano.

GachaN0nsense wrote:

PkmnQ wrote:

And yours is too.

I believe that Scratchy is the OP, on a different account as they moved, so technically since its their topic they can ask questions to users such as nano.

Yes, that is correct, i have moved my account to Scratchy697 as i mentioned in my signature

Yeah, I knew that, I just wasn't paying attention to the accounts

bump

Scratchy697 wrote:

fdreerf wrote:

I'm a little upset now as I was thinking of making this exact same suggestion, but I was certain there was a dupe somewhere out there. Sadly there isn't, so I'll just have to live with this regret now.

Merged topics can be incredibly annoying as it requires third party programs to view the original topic and find where it was merged to. I normally rely on ancient topics that are closed from dupes, so I can crowd-source the dupe finding to past forumers. However, whenever a topic with a lot of dupes gets merged, all those links become dead, and it becomes way more difficult to find the correct dupe.

wait what kind of third party program can be used to view dustbinned topics?

If it's indexed, Web Archive (Wayback Machine) can access the topics, assuming you know the URL.
https://web.archive.org

dominic305 wrote:

If it's indexed, Web Archive (Wayback Machine) can access the topics, assuming you know the URL.
https://web.archive.org

All snapshots of https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/412/ on the Wayback Machine display a blank page.