- Joined
- Jan 21, 2007
- Sythe Gold
- 1,234
- Messages
- 14,211
The fact that you can't edit your own thread titles shits me too, but I presume that's a shortfall of vb.
That's a mod power and we have never wanted to give users any moderator powers.
The fact that you can't edit your own thread titles shits me too, but I presume that's a shortfall of vb.
That's a mod power and we have never wanted to give users any moderator powers.
Dafuq?
I agree but lets see what Matthew or Sythe says. I wont support or no support anything before one of them posts.
It'll be hard to post support or no support with BOTH of their dicks in your mouth TBH
Full support op. After years of "wait for vb4" and the whole NVM JK no vb4 bit I'm growing weary.
My primary issues are tagging, notifications and mobile. Though I support OPs other points as well.
I support the changes but I wont support if its too hard to update all the features. I know it sounds weird but as I said, I dont mind staying as it is so why not see their opinions before.
That's a mod power and we have never wanted to give users any moderator powers.
None of this is hard to do. Tons of website have to update their software on a regular basis and make sure they fix anything that breaks. The thing is, we've waited for so long that everything we've added onto the forums will most likely break.
It will just probably take several days of multiple people's time to do smoothly. We could start out by having a clone hosted elsewhere and mess with that and see what exactly will break, then fix those issues, and once we have the coding to fix it, we do another clone, some beta testing, and finally save a backup, go into scheduled maintenance mode and get it done. For the next week or so there could be a warning on top of the website and a bug report page that'll make sure people take extra precautions, since it is indeed a trading website, and then once it's all clear we're done, or if we run into major issues we take another backup for proof purposes in case someone posted something that would get them banned, then revert back. Not a lot can go wrong if it's done properly.
Sythe as a community is way too paranoid. I don't see how disallowing title changes really helps in our situation, though. It's not like we're Reddit. In their case, someone changing the title after garnering thousands of people's "approval" can be dangerous. The worst thing someone can do on a Sythe title is something stupid and if we just have logs of title changes it'll be fine.
Sythe as a community is way too paranoid. I don't see how disallowing title changes really helps in our situation, though. It's not like we're Reddit. In their case, someone changing the title after garnering thousands of people's "approval" can be dangerous. The worst thing someone can do on a Sythe title is something stupid and if we just have logs of title changes it'll be fine.
Apparently it will hurt the SEO but I'm not really against it.
I think we've gotten to that point in the argument before, but down time is apparently detrimental in our Google search rankings. I still think these changes should be made though.
Apparently it will hurt the SEO but I'm not really against it.
None of this is hard to do. Tons of website have to update their software on a regular basis and make sure they fix anything that breaks. The thing is, we've waited for so long that everything we've added onto the forums will most likely break.
It will just probably take several days of multiple people's time to do smoothly. We could start out by having a clone hosted elsewhere and mess with that and see what exactly will break, then fix those issues, and once we have the coding to fix it, we do another clone, some beta testing, and finally save a backup, go into scheduled maintenance mode and get it done. For the next week or so there could be a warning on top of the website and a bug report page that'll make sure people take extra precautions, since it is indeed a trading website, and then once it's all clear we're done, or if we run into major issues we take another backup for proof purposes in case someone posted something that would get them banned, then revert back. Not a lot can go wrong if it's done properly.
.
There's lots of legitimate reasons why we should and also why we haven't. Usability is a big issue never far from my mind. At the end of the day I have to do what's best for the site even if that means maintaining old code.
We will move to new software eventually -- when we find something which is appropriate.
@Rich, what about the notifications thing? Roary said it was approved and pending implementation?

