Author

Topic: Open Question: What Mt Gox discussions are allowed? (Read 1235 times)

legendary
Activity: 3052
Merit: 1031
RIP Mommy
Instead of dozens of Gox topics across all subforums, there should be one, that all new topics containing "Gox" are auto-merged into.
legendary
Activity: 3472
Merit: 1721
Currency exchange is only for... currency exchange Wink Exchange service talk belongs in Service Discussion.
legendary
Activity: 1512
Merit: 1028
I just looked at https://bitcointalk.org/index.php?board=1.0 - the entire first page is mtgox trolling.

Quote
Discussion of specific Bitcoin-related services usually belongs in other sections.

While it is interesting that money is no longer coming out of the oldest Bitcoin exchange, I think ALL that talk can be moved to some other child forum, as this Bitcoin user is unaffected.

Child forum "Currency exchange" in "Marketplace" is currently too crowded. That forum should be renamed "Bitcoin Exchanges", as the sole place where exchange service talk is not off-topic. A new child forum exclusively for person-to-person exchange requests and solicitation should be created.
global moderator
Activity: 3794
Merit: 2615
Join the world-leading crypto sportsbook NOW!
I think most get moved there, especially when they're about its service problems. Maybe if the threads are about how the general gox fiasco affects other aspects of Bitcoin etc then they stay in the Bitcoin forum?

I suppose everything related to the the general gox fiasco that affects other aspects of Bitcoin could be posted

Are you a bot?
legendary
Activity: 1512
Merit: 1028
Threads about limited withdraws, insolvency, and such exchange-specific topics are best sequestered to the currency exchange board, as they are mostly troll-bait.

One example where discussion would be acceptable outside of the currency exchange subforum would be the speculation subforum, if you are sharing your investment theories (or misinformation) about Mtgox and how their fate may affect pricing on that exchange or elsewhere.

The topic of transaction malleability, Bitcoin protocol, and how to not fall into the trap that Mtgox did would be suitable for service discussions or general Bitcoin. Creating a new thread when there are a thousand others on that topic will wear on the nerves of other members though.
jr. member
Activity: 68
Merit: 1
I suppose everything related to the the general gox fiasco that affects other aspects of Bitcoin could be posted
legendary
Activity: 3472
Merit: 1721
I think most get moved there, especially when they're about its service problems. Maybe if the threads are about how the general gox fiasco affects other aspects of Bitcoin etc then they stay in the Bitcoin forum?

Yes, such threads may sometimes belong in Bitcoin Discussion, though there shouldn't be too many of them. When SR was hacked some topics about them were being moved to Politics & Society, Off-topic or Service Discussion, but a few could remain because:

Quote
General discussion about the Bitcoin ecosystem that doesn't fit better elsewhere. News, the Bitcoin community, innovations, the general environment, etc. Discussion of specific Bitcoin-related services usually belongs in other sections.
emphasis mine
global moderator
Activity: 3794
Merit: 2615
Join the world-leading crypto sportsbook NOW!
I think most get moved there, especially when they're about its service problems. Maybe if the threads are about how the general gox fiasco affects other aspects of Bitcoin etc then they stay in the Bitcoin forum?
sr. member
Activity: 322
Merit: 252
I guess that answers that question :-)
hero member
Activity: 658
Merit: 500
I know one thing, this thread belongs in Meta...
Yup
LOL the OP is such an idiot. What a fcking tool
legendary
Activity: 1120
Merit: 1009
I know one thing, this thread belongs in Meta...
sr. member
Activity: 322
Merit: 252
There seems to be a bit of an opaque moderation policy... Some threads get moved to service discussion, some don't regarding Mt. Gox.

Is this just an "I feel like moving this particular topic" or are there any actual rules to this?
Jump to: