Advertisement
Drakia

Untitled

Feb 28th, 2012
85
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 21.13 KB | None | 0 0
  1. <+NuclearW> mbaxter, do new version of VanishNoPacket not use Spout?
  2. <+NuclearW> Or is that just a goal?
  3. <+mbaxter> Goal.
  4. <+NuclearW> I'm catching up with my znc buffer, still reading through #spout
  5. <+NuclearW> You get a lot of nay-sayers?
  6. <+mbaxter> No, just the occasional user who says spout doesn't work.
  7. <+NuclearW> Ah
  8. <+NuclearW> I'm wondering how much we can learn from the "noobs" who complain about Bukkit on the Spout forums...
  9. <+NuclearW> Some common complaints, but I have no solutions.
  10. <+mbaxter> Not much, honestly. They're all there following hype, with very few solid rational arguments. Yes, there are some issues with bukkit but the spout forums are not going to be a reliable source of discussion on the topic
  11. <+NuclearW> Nah not talking about the hype as much
  12. <+NuclearW> Talking about people like this: http://forums.getspout.org/threads/want-to-start-developing.633/
  13. <+NuclearW> The people who are learning, but seem to have issues with Bukkit while learning.
  14. <+NinjaGrinch> lol
  15. <+NuclearW> Now, in that case I suppose it's that he doesn't know Java, and that's bad enough. But fact of the matter is people do learn Java for Bukkit, so I wonder...
  16. <+NuclearW> Hi NinjaGrinch
  17. <+NinjaGrinch> Hiya :p
  18. <+NuclearW> Just wondering aloud here
  19. <+NuclearW> It's sort of nice to see people who go to the spout forums to complain, as to them it's a more open place to do just that. People complain about Bukkit there, people complain about Spout here.
  20. <+NuclearW> I suppose it makes for more honest feedback, but that's just a thought.
  21. <+NinjaGrinch> I find that people like to complain for the sake of complaining.
  22. <+NinjaGrinch> Doesn't matter what it is.
  23. <+NinjaGrinch> or what they are complaining about.
  24. <+NuclearW> Oh naturally
  25. <+NuclearW> But that doesn't mean we have to discard all complaints out of hand.
  26. <+NuclearW> I think there's something to be learned here, and I intend to learn it.
  27. <+NinjaGrinch> :p
  28. <+SwearWord> I don't get it
  29. <+SwearWord> Why are people using Bukkit forums to talk about spout
  30. <+SwearWord> It's like going onto getspout.org and posting about Bukkit features
  31. <+SwearWord> Just awkward.
  32. <+mbaxter> SwearWord: You really don't see why?
  33. <+NuclearW> People do it because they feel safer.
  34. <+mbaxter> It's to gather more people to go over to spout.
  35. <+SwearWord> Well
  36. <+NinjaGrinch> Talking about it and bitching about it are not the same thing :p
  37. <+NuclearW> Someone goes to Spout to complain about Bukkit because Bukkit staff (excepting MonsieurApple) aren't there.
  38. <+NuclearW> And vice-versa
  39. <+SwearWord> mbaxter: I guess that question was me sarcastically asking the people posting
  40. <+SwearWord> Someone go register EvilSeph's nick
  41. <+SwearWord> and start spamming SPOUT SUCKS
  42. <+NinjaGrinch> LOL
  43. <+SwearWord> Or better yet
  44. <+SwearWord> do it with Tahg's
  45. <+NuclearW> Is there even a Spout user with that username?
  46. <+NinjaGrinch> If I were stupid enough to try that I'd use Grum's (sorry Grum).
  47. <+SwearWord> I checked the other day
  48. <+SwearWord> And it was available
  49. <+NuclearW> Hmm
  50. <+NuclearW> I almost feel like to stop idiots we ought to register ourselves there...
  51. <+NuclearW> Oh well, trolls will be trolls
  52. <+SwearWord> Naw if it happens it will be done unsubtly
  53. <+SwearWord> and it will be hilarious
  54. <+NuclearW> Perhaps
  55. <+NuclearW> Anyway, community degradation. Commonly used line from people on Spout, something I sort of agree with. Is it a valid issue we should consider taking on?
  56. <+SwearWord> I blame not using bukkitdev
  57. <+SwearWord> It just gives everything an in limbo, senioritis feel to it
  58. <+NuclearW> I've been blaming it mostly on dilution with non-developers
  59. <+NuclearW> People see Spout as a much more mature and intellectual community because at the moment it is, it's mostly developers. Sort of like people say Bukkit was back in the beginning.
  60. <+NuclearW> And BukkitDev needs to get fixed
  61. <+SwearWord> Oh well.
  62. <+NinjaGrinch> BukkitDev.. I do not really care for it. It feels half-assed to me. Thats just my opinion though.
  63. <+SwearWord> I don't get how it can seem half-assed when we previously had forum threads
  64. <+NuclearW> I think if we set up our new tag system fairly soon we can perhaps foster a more intellectual area of the forums, even if just Plugin Development and Bukkit+
  65. <+NuclearW> SwearWord, people like the forum system.
  66. <+SwearWord> Just like people like the old facebook
  67. <+NuclearW> I like the forum system (not maintaining it, mind you)
  68. <+NuclearW> But BukkitDev has valid issues
  69. <+SwearWord> Everytime there's an update
  70. <+SwearWord> yeah it does
  71. <+SwearWord> But it's better than the forums
  72. <+NuclearW> So those need to be fixed.
  73. <+SwearWord> Considering it HAS the forums
  74. <+NuclearW> At the moment I don't feel it is better.
  75. <+NinjaGrinch> I agree with NuclearW, I do not feel it is better at the moment either.
  76. <+NuclearW> It lacks the alerts and a proper subscription system, to very important features of the forums.
  77. <+NuclearW> Administrators will subscribe to threads of plugins they use, and developers literally get an alert for everything realted to their plugins.
  78. <+NuclearW> These are very important things to have
  79. <+NuclearW> I know you've given up on plugin development SwearWord, but I know I don't prefer BukkitDev for my plugins.
  80. <+SwearWord> Well I had auto pushing from jenkins to bukkitdev setup, and issue tracker in github
  81. <+SwearWord> I preferred that over forums
  82. <+NuclearW> Not everyone knows how to nor has the resources for that.
  83. <+NuclearW> And if that's what makes it so great then why isn't that part of BukkitDev itself?
  84. <+SwearWord> So the problem with BukkitDev is people don't know how to use it. I get the alerts are shitty, that's why I had to close the forum section
  85. <+SwearWord> bleh oh well
  86. <+SwearWord> I still thinking moving to BukkitDev NOW is better than what we have now
  87. <+NuclearW> We need alerts before we can move over.
  88. <+SwearWord> Random limbo here some stuff is on BukkitDev
  89. <+SwearWord> and some is on forums
  90. <+NuclearW> I would also love to force Forum mode on
  91. <+SwearWord> No idea where you're supposed to look
  92. <+NuclearW> We've put off moving to BukkitDev completely because of no alerts.
  93. <+SwearWord> That coupled with no more new and exciting MC updates has been pretty bad
  94. <+NuclearW> We have no alerts because Curse isn't adding them.
  95. <+SwearWord> Yeah I know
  96. <+SwearWord> the alerts is a problem
  97. <+NuclearW> So we need to communicate that we're waiting for Curse.
  98. <+SwearWord> No we don't
  99. <+SwearWord> Guess what that's gonna start
  100. <+SwearWord> :P
  101. <+NinjaGrinch> I think we do, and should.
  102. <+NuclearW> And I really have no idea of the money involved, but if Curse can't be bugged to do things that we need for our community, we should strongly consider moving from Curse.
  103. <+NinjaGrinch> Why keep everything so secretive, especially since its something that people should know.
  104. <+SwearWord> "Guys we're stuck in limbo because we're waiting for curse"
  105. <+NuclearW> NinjaGrinch, the problem is all we really have to say is "Well, we're waiting on Curse"
  106. <+SwearWord> -> "ffffucckkkk curssseeee evillll"
  107. <+SwearWord> nty
  108. <+NuclearW> Spout is doing a lot of work, but do we really want their killer app being "Working plugin management system"?
  109. <+NinjaGrinch> I suppose. At least remove that damn header in the plugin section that says we are phasing out the forum system since I don't think thats happening any time soon.
  110. <+NuclearW> It's still in the plan, it just needs to specify that we're waiting, and that we can't really do anything
  111. <+NinjaGrinch> Well Spout does do one thing better in my opinion, they are more open about things. They keep people more aware of whats going on. At least thats how I feel.
  112. <+NuclearW> Our hands are tied, and that's a bad situation to be in
  113. <+NuclearW> NinjaGrinch, I fear that a feeling may be all it is.
  114. <+NuclearW> I mean, I can't know.
  115. <@Rigby> FYI -- We have a staff section on the forum for you to voice these concerns.
  116. <+NinjaGrinch> I know.
  117. <+NuclearW> Rigby, would you prefer we post on the forums over conversations in IRC?
  118. <@Rigby> If it was one or the other then yes.
  119. <@Rigby> However both would be nice.
  120. <+SwearWord> How is yes an anser to that question LOL
  121. <+NuclearW> At any rate, I'm not so sold on Spout, but that's my personal opinion.
  122. <@Rigby> Because he asked if I'd prefer posting on the forums to talking on IRC...
  123. <@Rigby> Soooo my response is 'Yes'
  124. <@Rigby> Thats how it's an answer to his question.
  125. <+NuclearW> I also fear their current structure will not stand under the amount of users we have
  126. <+SwearWord> Rigby: oops misread over as or
  127. <+NuclearW> Well I suppose I can better formulate some of my thoughts and post this a bit later.
  128. <@Rigby> Well NuclearW last time I saw they struggled to keep their site and services up when just running a plugin...
  129. <@Rigby> They intend to make spout auto report crash reports and stacktraces to their site...
  130. <@Rigby> The amount of traffic that would involve...
  131. <+NinjaGrinch> They've gotten that under control I believe. It was more or less their hoster bailed.
  132. <+SwearWord> They have good web people
  133. <+SwearWord> I know that.
  134. <+SwearWord> Just bad timing
  135. <+NinjaGrinch> I believe they hit 2TB traffic and their hoster bailed on them, they found someone who was willing to take it.
  136. <+NuclearW> Rigby, indeed. But I'm more talking about their administrative and staff policies.
  137. <+NuclearW> If they are going to be competition, even if a friendly sort, I see no reason we staff should be a reason for someone to pick Spout over Bukkit or vice versa
  138. <+NinjaGrinch> Huh?
  139. <+NuclearW> If Spout is going to be competition, then complaints about us staff should be reduced by as much as possible.
  140. <+NinjaGrinch> Publicly yes.
  141. <+NuclearW> We don't want people to say "Well the staff at Bukkit are jerks, I will use Spout"
  142. <+NinjaGrinch> Well I don't know.
  143. <+NinjaGrinch> Everyone, including staff should be able to voice their opinions.
  144. <+NinjaGrinch> As long as its in a nice manner.
  145. <+NuclearW> Yes, I agree.
  146. <+NinjaGrinch> Something like "Spout just sucks, don't bother using them" isn't exactly friendly.
  147. <+NuclearW> I've never said that we shouldn't?
  148. <+NuclearW> I never said we should say that either?
  149. <+NinjaGrinch> I never said you did now did I?
  150. <+NinjaGrinch> Why are you implying that I did say you did.
  151. <+NuclearW> Because I'm confused now
  152. <+NuclearW> Anyway.
  153. <+NinjaGrinch> >.>
  154. <+NuclearW> When I'm blabbing like this it's because I'm openly thinking.
  155. <+NuclearW> My general point is that if there is something we can learn from Spout, we should. And that as staff we should strive to be the best we can be. However
  156. <+NuclearW> However I don't know what exactly we can do to help facilitate that.
  157. <+NuclearW> Perhaps, we aren't even doing much anything wrong, but first we need to identify any issues we might be having.
  158. <+SwearWord> Why bother with ANY of it
  159. <+SwearWord> just ignore
  160. <+NuclearW> And the point I was making was that perhaps by looking at the Spout forums we can identify some of the things we're doing wrong, if we are.
  161. <+SwearWord> Giving attention is so bad
  162. <@EvilSeph> NinjaGrinch, why are you making excuses for them?
  163. <+NuclearW> Because you don't learn by ignoring it.
  164. <+NinjaGrinch> EvilSeph, I am voicing my opinion. Nothing more.
  165. <+NuclearW> We can't very well wish Spout away.
  166. <+NinjaGrinch> If that is not alright then please say so.
  167. <+SwearWord> What?
  168. <+SwearWord> Just ignore it
  169. <+SwearWord> And it'll be fine
  170. <+NuclearW> SwearWord, why ignore Spout?
  171. <+NuclearW> Because ignoring something and hoping it goes away isn't how you deal with something.
  172. <+SwearWord> Because if they keep posting about their theoritical features and no one says "buttttt" they go away
  173. <+SwearWord> If we address it somehow, then we're taking them seriously
  174. <+NuclearW> We don't have to publicly state anything we're doing.
  175. <+NuclearW> But to simply ignore them seems immature at best.
  176. <@EvilSeph> NinjaGrinch, how is making excuses for them voicing your opinion?
  177. <@EvilSeph> you're clearly defending them - that's not an opinion
  178. <+SwearWord> Spy
  179. <+NinjaGrinch> In your eyes I was defending them, in mine I was simply voicing my opinion. Last I checked I was allowed to do that.
  180. <+NuclearW> To be honest I don't see the defense he's making for them?
  181. <@EvilSeph> you haven't been here the whole day actively reading
  182. <+NuclearW> I've been away here and there, but I don't recall...?
  183. <+NinjaGrinch> I've barely spoken in here today aside from this current conversation.
  184. <+SwearWord> I remember Grum telling you to hit ninjazidane in real life
  185. <+NinjaGrinch> Yeah :p
  186. <+NuclearW> Okay I remember that
  187. <+NinjaGrinch> That was when he asked why we were on the same IP.
  188. <@EvilSeph> every time we talk about Spout, you're there defending them
  189. <+NinjaGrinch> Everytime we talk about spout I say what I think.
  190. <+NinjaGrinch> Again, last I checked I was allowed to.
  191. <@EvilSeph> we fuck up with the website all the time, and we take responsibility for it...I've never made an excuse for our incompetence
  192. <@EvilSeph> the fact is, Spout are ill-equipped to handle being large
  193. <+NuclearW> I agree on that last point
  194. <@EvilSeph> this is pretty much undisputable - just look at their handling of things
  195. <@EvilSeph> and yet you blindly defend them
  196. <@EvilSeph> I am also entitled to say whatever I think, by the way.
  197. <+NinjaGrinch> That you are. :p
  198. <+SwearWord> I'm not :/
  199. <@EvilSeph> it just seems like you're such a fanboy whenever Spout comes up
  200. <@Rigby> In that case I'm entitled to say the following -
  201. <@Rigby> _-_-_-_-_,------,
  202. <@Rigby> -_-_-_-_-| /\_/\
  203. <@Rigby> _-_-_-_-~|__( ^ .^)
  204. <@Rigby> -_-_-_-_-"" ""
  205. <+NinjaGrinch> But it was true that they hit 2TB and their hoster bailed.
  206. <@EvilSeph> that's irrelevant...
  207. <+NinjaGrinch> Its the truth.
  208. <@EvilSeph> we've hit much more and nothing went down
  209. <@EvilSeph> because we were prepared
  210. <@Rigby> NinjaGrinch -- Is it? I heard something completely different :P
  211. <+SwearWord> Well you take responsibility for it either way
  212. <+NinjaGrinch> I'm going on what I was told but nothing more.
  213. <@EvilSeph> 'their web guys are good' sounds like blindly defending them
  214. <@Rigby> One of their scripts was taking up more than it should on a shared box :P
  215. <+SwearWord> That was me who said that
  216. <+NinjaGrinch> I never said 'their web guys are good'.
  217. <+SwearWord> I was talking about top_cat
  218. <+SwearWord> he does nice css/js
  219. <+NinjaGrinch> Where and when did I say that?
  220. <@EvilSeph> my apologies, I was mistaken about that
  221. <+SwearWord> Basically I'm a fanboy.
  222. <+SwearWord> http://spoutcraft.org/ it's shitty for user friendliness, but attention to detail is nice
  223. <+SwearWord> You can even drag around the window
  224. <@EvilSeph> I just grow wary of people who vehemently defend what could be our competition
  225. <@Rigby> SwearWord -- A screenshot and 3 mouse overs? :P
  226. <+NinjaGrinch> I cannot like Bukkit's competition?
  227. <+SwearWord> Rigby: it's a lot more than that :P
  228. <@Rigby> + thats months old when SpoutCraft was first started.
  229. <@Rigby> and has never been completed ;P
  230. <@Rigby> like Fill ;)
  231. <+SwearWord> Yeah I know
  232. <+SwearWord> It's still cool
  233. <@EvilSeph> it can and usually does cause a rift among the team, which leads to a disrupt in productivity and morale
  234. <@EvilSeph> I never said that, please don't put words in my mouth
  235. <+NinjaGrinch> I didn't. It was a question.
  236. <@EvilSeph> why is it that everything you're saying seems filled with attitude...
  237. <+NinjaGrinch> You are the one who jumped on me with fanboy accusations and saying I always defend them.
  238. <+NinjaGrinch> When all I do is speak my opinion.
  239. <+SwearWord> You do though
  240. <@EvilSeph> you're the one who admitted that you're a fanboy... and you do always defend them
  241. <+NinjaGrinch> I never said I was a fanboy..
  242. <+NinjaGrinch> Unless you are referring to my comment to Grum.
  243. <+NuclearW> SwearWord is the fanboy
  244. <+SwearWord> C# <3
  245. <+NuclearW> The Top_Cat fanboy
  246. <@EvilSeph> I am referring to your comment to Grum
  247. <+NinjaGrinch> If I recall right, I said I am surprised he didn't call me a fanboy over anything.
  248. <@EvilSeph> you basically said "I'm not a fanboy, I just x" which is posturing
  249. * @EvilSeph shrugs
  250. <+NinjaGrinch> Just what?
  251. <@EvilSeph> it's not important, you're not going to change your mind
  252. <+NuclearW> Well.
  253. <+NinjaGrinch> Nor are you.
  254. <@Rigby> "Quit (Quit: ~ InspireNXE.com - Inspiring New eXperiences | getspout.org - Improving Minecraft every day! ~)"
  255. <+NinjaGrinch> This conversation seems pointless due to both facts.
  256. <@EvilSeph> but I don't appreciate the lack of respect and attitude you're showing towards us
  257. * @Rigby whistles
  258. <+SwearWord> Rigby: wwho was that?
  259. <+NuclearW> I still think we can try to learn something from the people who've jumped ship or are picking Spout as a starting point. If only for what started them down that path.
  260. <@Rigby> That's Ninjas quit message :P
  261. <+SwearWord> LOL
  262. <@EvilSeph> NuclearW, naturally.
  263. <+SwearWord> He's a prostitue
  264. <+SwearWord> Are people really jumping ship for reasons other than "it's new" and new opportunity to be someone in a community?
  265. <+NinjaGrinch> EvilSeph, I wouldn't have given you an attitude or shown you any disrespect if you didn't just jump in out of nowhere and bash on me.
  266. <+NuclearW> I should also note I've taken to reading the Spout forums for people who are like that and messaging them privately.
  267. <@EvilSeph> I asked you a simple question and you got defensive
  268. <+NuclearW> I really thing the "safety" feeling people get from just being on a different site helps to get more accurate feedback
  269. <+NinjaGrinch> I felt like my right to my opinion was being violated.
  270. <+SwearWord> Safety?
  271. <+NinjaGrinch> Because is sure felt that way.
  272. <+NuclearW> SwearWord, the feeling of safety fostered by a different staff set.
  273. <+SwearWord> Oh oh
  274. <+NinjaGrinch> When I joined I was told I was a community member first, staff member second.
  275. <+SwearWord> I get it
  276. <@EvilSeph> your right to opinion?
  277. <@EvilSeph> I already stifle that...
  278. <+NuclearW> NinjaGrinch, that's a rare example of EvilSeph being sarcastic.
  279. <+SwearWord> I still think it's just...hype and seeming opportunity
  280. <@EvilSeph> no, I am being serious
  281. <+NuclearW> SwearWord, a lot of it is.
  282. <@EvilSeph> you all agreed to represent the project appropriately
  283. <@EvilSeph> that's your 'right to opinion' already stifled
  284. <+NuclearW> But there are some gems to be had.
  285. <+NinjaGrinch> I can voice my opinion and still be approrpiate about it.
  286. <+NinjaGrinch> appropriate*
  287. <+NuclearW> Ah, that. Well I don't see that as really stifling opinion, I just get a different set of people to complain to
  288. <+SwearWord> Like, omg I can pull request something and be staff omfg!
  289. <@EvilSeph> you can't, actually..that's for me to decide
  290. <+SwearWord> Or, I can talk about it a lot and become staff!
  291. <+NinjaGrinch> Right..
  292. <@EvilSeph> there are obviously some things I forbid staff from getting involved in - like Drakia drama
  293. <+NuclearW> SwearWord, that's the sort of thing we don't want to so much take into consdieration.
  294. <+NinjaGrinch> I do not believe I was around when that unfolded.
  295. <+NuclearW> It's stuff like what I linked before, people choosing Spout for a "starting" point
  296. <+SwearWord> Either way if Spout becomes a problem, my cousin knows a guy
  297. <+NuclearW> His name is Vinnie, right?
  298. <@EvilSeph> nothing any staff member can say will probably be appropriate when it comes to Drakia drama
  299. <@EvilSeph> but I generally don't stop you from speaking your mind
  300. <+NuclearW> Well to be fair there isn't much left to be said on that particular issue
  301. <@EvilSeph> however, when doing so agitates several people on staff...and you don't have a foundation for your statements...
  302. <+NinjaGrinch> So in essence you are saying..?
  303. <@EvilSeph> I simply asked a question and made an observation. The only reason this discussion has been so drawn out is because you got really defensive
  304. <+NuclearW> NinjaGrinch, you agreed when you signed up that in public you are the face of the project, you're expected in public to act as such.
  305. <+NuclearW> We all did
  306. <+NinjaGrinch> Yes, in public.
  307. <@EvilSeph> which made me wonder if it might become a problem
  308. <@EvilSeph> there's that attitude again
  309. <+NinjaGrinch> No attitude, I was simply pointing that part out.
  310. <+NinjaGrinch> This IRC is not public so I haven't gone against that have I?
  311. <@Rigby> So hows the weather been lately?
  312. <@EvilSeph> ...
  313. <@Rigby> Whats peoples plans for the new year?
  314. <@Rigby> Hows christmas been?
  315. <@Rigby> Steam deals are good...
  316. <+SwearWord> Christmas was very christy, the weather has been weathery
  317. <@EvilSeph> you just don't get it
  318. <+NuclearW> I got a pair of noise-cancelling headphones. Love them
  319. <@Rigby> Shame it doesn't cancel out this racket NuclearW
  320. <+SwearWord> I read racist
  321. <+NuclearW> Rigby, it cancels out my roommate, which I thought could not be done
  322. <+SwearWord> Shame it doesn't cancel out all the racists
  323. <@Rigby> :(
  324. <@EvilSeph> I feel like no matter what I say, you're going to snap at me
  325. <@EvilSeph> so I'm done
  326. <@EvilSeph> you can decide if you want to take what has been said to heart or not
  327. <@EvilSeph> I didn't mean to jump on you, I was simply asking a question and making an observation, nothing more. I needed to know if I could depend on you to keep your composure.
  328. <+NinjaGrinch> Alrighty :p
  329. <@EvilSeph> ...
  330. <@EvilSeph> anyway, I'm strongly for watching the competition or anything involved in Bukkit
  331. <@EvilSeph> it's why I keep such a close eye on Drakia's forums
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement