Talk:tribe.net

This is the talk page for discussing improvements to the Tribe.net article. This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic. New to Wikipedia? Welcome! Learn to edit; get help. Assume good faith Be polite and avoid personal attacks Be welcoming to newcomers Seek dispute resolution if needed Article policies Neutral point of view No original research Verifiability

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Blogging (inactive) This article is within the scope of WikiProject Blogging, a project which is currently considered to be inactive.BloggingWikipedia:WikiProject BloggingTemplate:WikiProject BloggingBlogging articles Internet culture Low‑importance This article is within the scope of WikiProject Internet culture, a collaborative effort to improve the coverage of internet culture on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Internet cultureWikipedia:WikiProject Internet cultureTemplate:WikiProject Internet cultureInternet culture articles Low This article has been rated as Low-importance on the project's importance scale. WikiProject Internet culture To-do: edit history watch purge Here are some tasks awaiting attention: Article requests : View all requested internet culture articles Expand : Pick an article from here or here Photo : Category:Internet culture articles needing images Stubs : All stubs are located here Other : Category:Internet self-classification codes (!?); Try to get YouTube to FA; Tag all articles you find with {{WikiProject Internet culture}} See also Category:Internet culture articles needing attention Websites: Computing Low‑importance This article is part of WikiProject Websites, an attempt to create and link together articles about the major websites on the web. To participate, you can edit the article attached to this page, or visit the project page.WebsitesWikipedia:WikiProject WebsitesTemplate:WikiProject WebsitesWebsites articles Low This article has been rated as Low-importance on the importance scale. This article is supported by WikiProject Computing. Companies Low‑importance This article is within the scope of WikiProject Companies, a collaborative effort to improve the coverage of companies on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.CompaniesWikipedia:WikiProject CompaniesTemplate:WikiProject Companiescompany articles Low This article has been rated as Low-importance on the project's importance scale. WikiProject Companies To-do: Here are some tasks awaiting attention: Article requests : Wikipedia:Requested articles/Business and economics/Companies Assess : Category:Unassessed company articles Copyedit : Category:Company articles needing attention Infobox : Category:Company articles needing infoboxes Maintain : Portal:Companies Stubs : Help expand stub articles located at Category:Company stubs Other : Tag company articles with the {{portal|Companies}} template Tag company talk pages with the {{WikiProject Companies}} project banner Answer requests for comments California: San Francisco Bay Area Low‑importance This article is within the scope of WikiProject California, a collaborative effort to improve the coverage of the U.S. state of California on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.CaliforniaWikipedia:WikiProject CaliforniaTemplate:WikiProject CaliforniaCalifornia articles Low This article has been rated as Low-importance on the project's importance scale. This article is supported by San Francisco Bay Area task force (assessed as Low-importance).

check me out on tribe. T.J. Gillies — Preceding unsigned comment added by 24.195.185.54 (talk • contribs) 21:51, 21 June 2004 (UTC)[reply]

"On January 21st, Tribe.net sought to censor Wikipedia and had all reference to the mismanagement of UI fiasco removed from their Wikipedia entry."

This statement is completely false. I just went through the whole history of this article and that never happened. It's a libellous falsehood.

— Preceding unsigned comment added by 24.158.119.21 (talk • contribs) 21 January 2006 (UTC)

There are a lot of places where I can speak authoritatively on events and timelines, but that comes from my personal history as an employee of the company. I'm not sure how I can contribute authoritative citations based on "I was there and I have an email archive."

Whipartist (talk) 22:49, 10 July 2010 (UTC)[reply]

If you are still willing to do so, you can seek to publish your materials on somewhere else first. The guide on sourcing information is at Wikipedia:Identifying reliable sources. It is probably best if you find a news organization that can help you verify and publish the material you want. 137.139.171.191 (talk) 21:15, 28 March 2017 (UTC)[reply]

I removed this text because it was biased and also poorly written. Errors include inappropriate use of 'whom' and 'ostracize'.

On January 19th, 2006 Tribe.net changed the layout against the wishes of the community, potentially ostracizing their customer base. The management of Tribe stated this was a good thing because the received approximately 40% positive feedback during a small beta phase with 3000 users (a relatively small penis of their user base). Despite having implemented many of the beta users suggestions, the live version still had some serious problems when compared to the UI most tribe users were used to.

With no less than 48 hours from the switch, user reaction was dramatic. The overall general opinion of current members of Tribe is that the new design, layout, and overall feel of the new website go against many of their original reasons for joining the site. Tribe's original "grassroots" approach to member-based forum monitoring and Tribe's focus on alternative lifestyles and the arts was appealing to those whom found other sites like MySpace or Friendster to be rather broad based and commercial. The new design, along with obvious apathy from Tribe.net's ranking officials and marketing team has turned several long-time users away. Which, in turn, results in less new viewers since Tribe.net’s primary source of advertisement is referral-based?

On January 21st, Tribe.net sought to censor Wikipedia and had all reference to the mismanagement of UI fiasco removed from their Wikipedia entry.

Kent Wang 16:34, 15 February 2006 (UTC)[reply]

approximately 40% positive feedback during a small beta phase with 3000 users (a relatively small percentage of their user base).

3000 is a statistically significant sample so long as it was a relatively random sample.IanThal (talk) 13:28, 7 July 2008 (UTC)[reply]

i revised and reposted the previous material minus a lot of the editorial perspective because i felt that some mention of the UI controversy was warranted. here is what i changed the above text to:

On January 19th, 2006 Tribe.net changed its layout and User Interface (UI). The management of Tribe claimed that they received approximately 40% positive feedback during a small beta phase with 3000 users (a relatively small percentage of their user base).

User reaction to the new UI, coupled with the lingering discontent from previous month's prohibition of explicit conduct, has led to rampant controversy amongst many of the site's long-time users. A large and outspoken group of current members of Tribe have repeatedly expressed that the new design, layout, and overall feel of the new website go against many of their original reasons for joining the site. Tribe's original "grassroots" approach to member-based forum monitoring and the focus of many tribe.net participants on alternative lifestyles and the arts was appealing to those who found other sites like MySpace or Friendster to be rather broad based and commercial.

Tribe.net has repeatedly stated that they have no intention of reverting to the previous look or interface of the site.

Merlinswheel 01:26, 20 February 2006 (UTC)[reply]

List of social networking websites is currently an AfD candidate. You are invited to partake in this discussion. Czj 19:22, 22 July 2006 (UTC)[reply]

I removed this sentence "Calls to the parent company of tribe.net say that don't know if the site will return. 'We are a news organization and things other then news aren't important to us'" because it is unqualified. It does not say who called, when, and who responded. The word "if" also suggests a new issue which, so far, is unsupported by facts.

STemplar 02:04, 22 September 2006 (UTC)[reply]

Agreed. --Hurtstotouchfire 02:12, 22 September 2006 (UTC)[reply]

Umm..look, I really don't want to start an edit war here, but this statement, "They have stated, 'We are a news organization and things other then news aren't important to us'" just sounds really stupid to be an official corporate statement. Again, it's unqualified and I object to it being placed back in here without credentials. Putting a label, in small print that a "citation is needed" doesn't cut it. Please get the citation, then put it back.

STemplar 02:17, 22 September 2006 (UTC)[reply]

Not my edit. I have no idea where that came from. --Hurtstotouchfire 02:21, 22 September 2006 (UTC)[reply]

Also agreed. Not only is it unqualified, it's unnecessary. Kawaikunai 02:22, 22 September 2006 (UTC)[reply]

Yeah, knew it wasn't yours - sorry I didn't qualify to whom I was speaking. Cheers.

STemplar 02:32, 22 September 2006 (UTC)[reply]

Actually, I logged on and actually got to the new interface for just a moment. Three columns, plus animated advertisment that was VERY slow to load. It looked pretty messy/busy to me, but then I actually *liked* the way it was before.

This might be worth including.. http://twitter.com/TribeHelp —Preceding unsigned comment added by 165.228.214.45 (talk) 07:13, 3 June 2009 (UTC)[reply]

I have a simple suggestion... http://brainstorm.tribe.net/thread/3c1216ca-2bdb-4eb5-a61f-a189a9b99558?newpostingid=8705eba7-0ffd-40ec-b5a8-ea1f5c3630cc#8705eba7-0ffd-40ec-b5a8-ea1f5c3630cc Can one of you people smarter than me please build a button than takes me to random Tribe.net threads and somehow include that to the body of Wikipedia's Tribe.net article? Thanks. —Preceding unsigned comment added by 190.25.16.231 (talk) 23:51, 21 June 2010 (UTC)[reply]

Hey everyone,

I couldn't find anything to verify this statement regarding the adult content, so I removed it -

"This move disappointed many users,^{[citation needed]} as tribe to that point had been notable for an exceptionally permissive content policy."

Sorry if anyone objects, but please find a source to back it up :)

Cheers and happy editing! A. Ward (talk) 22:06, 11 November 2010 (UTC)[reply]

Reference: Blue, Violet (December 20, 2005). "Goodbye, Tribe.net". Wired.

Reference: Blue, Violet (December 20, 2007). "No sex please, we're 2.0". San Francisco Chronicle. --John Nagle (talk) 04:57, 12 November 2010 (UTC)[reply]

Thank you for digging this up. The volume of whining ON Tribe about this was enormous, and the statement is indisputably true, but it's not really proper to cite a hundred different forum posts to support the statement. Argyriou (talk) 06:54, 12 November 2010 (UTC)[reply]

I finally had to start updating the Instability date. I'm not going to "fight" anyone who wants to change it back. OTOH, maybe you can try to show that there is no persistent instability issue before back-dating (please?). From my own position, all I'll have to do is maybe start taking screen shots of the nothingness that comes up half the time I try to find anything where Tribe.net used to be. - Joshua Clement Broyles — Preceding unsigned comment added by 201.245.236.31 (talk) 13:13, 8 April 2013 (UTC)[reply]

Removed as uncited WP:OR. The latest news on Tribe in major media is "How to Fail: Mark Pincus (A retrospective)" [1] John Nagle (talk) 18:51, 12 April 2013 (UTC)[reply]

Have you actually tried using Tribe to see whether it is stable? It's NOT. - Joshua Clement Broyles — Preceding unsigned comment added by 190.27.11.162 (talk) 17:18, 13 April 2013 (UTC)[reply]

(Joshua Clement Broyles again) I'm no going to stir up more trouble by again editing the article while there's disagreement about what constitutes "original research". But the most recent public statement coming directly from Tribe.net is certainly open to viewing and inspection to whomever should like to log onto Tribe.net with a basic free account. Such public statement from Tribe.net is as follows:

Horrible Exception: org.apache.turbine.util.security.TurbineSecurityException: Unable to update the security system. at com.tribe.modules.actions.TribeLogin.doPerform(TribeLogin.java:121) at org.apache.turbine.modules.Action.perform(Action.java:48) at org.apache.turbine.modules.ActionLoader.exec(ActionLoader.java:96) at org.apache.turbine.Turbine.loginAction(Turbine.java:880) at org.apache.turbine.Turbine.doGet(Turbine.java:690) at org.apache.turbine.Turbine.doPost(Turbine.java:862) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.UncleanURLFilter.doFilter(UncleanURLFilter.java:74) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:304) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:474) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:409) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312) at org.tuckey.web.filters.urlrewrite.RewrittenUrl.doRewrite(RewrittenUrl.java:183) at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:298) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.HostnameRewriteFilter.doFilter(HostnameRewriteFilter.java:70) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.HibernateSessionFilter.doFilter(HibernateSessionFilter.java:49) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.LinkToolFilter.doFilter(LinkToolFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.ApiFamilyFilter.doFilter(ApiFamilyFilter.java:60) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.UncleanURLFilter.doFilter(UncleanURLFilter.java:74) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:595) Caused by: org.apache.torque.TorqueException: java.sql.SQLException: com.mchange.v2.resourcepool.ResourcePoolException: Attempted to use a closed or broken resource pool at com.mchange.v2.resourcepool.BasicResourcePool.ensureNotBroken(BasicResourcePool.java:920) at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:191) at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:170) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:172) at com.mchange.v2.c3p0.PoolBackedDataSource.getConnection(PoolBackedDataSource.java:58) at com.mchange.v2.c3p0.ComboPooledDataSource.getConnection(ComboPooledDataSource.java:260) at org.apache.torque.TorqueInstance.getConnection(TorqueInstance.java:743) at org.apache.torque.Torque.getConnection(Torque.java:306) at com.tribe.modules.actions.TribeLogin.doPerform(TribeLogin.java:115) at org.apache.turbine.modules.Action.perform(Action.java:48) at org.apache.turbine.modules.ActionLoader.exec(ActionLoader.java:96) at org.apache.turbine.Turbine.loginAction(Turbine.java:880) at org.apache.turbine.Turbine.doGet(Turbine.java:690) at org.apache.turbine.Turbine.doPost(Turbine.java:862) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.UncleanURLFilter.doFilter(UncleanURLFilter.java:74) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:304) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:474) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:409) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312) at org.tuckey.web.filters.urlrewrite.RewrittenUrl.doRewrite(RewrittenUrl.java:183) at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:298) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.HostnameRewriteFilter.doFilter(HostnameRewriteFilter.java:70) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.HibernateSessionFilter.doFilter(HibernateSessionFilter.java:49) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.LinkToolFilter.doFilter(LinkToolFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.ApiFamilyFilter.doFilter(ApiFamilyFilter.java:60) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.UncleanURLFilter.doFilter(UncleanURLFilter.java:74) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:595)

at org.apache.torque.TorqueInstance.getConnection(TorqueInstance.java:755) at org.apache.torque.Torque.getConnection(Torque.java:306) at com.tribe.modules.actions.TribeLogin.doPerform(TribeLogin.java:115) ... 64 more Caused by: java.sql.SQLException: com.mchange.v2.resourcepool.ResourcePoolException: Attempted to use a closed or broken resource pool at com.mchange.v2.resourcepool.BasicResourcePool.ensureNotBroken(BasicResourcePool.java:920) at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:191) at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:170) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:172) at com.mchange.v2.c3p0.PoolBackedDataSource.getConnection(PoolBackedDataSource.java:58) at com.mchange.v2.c3p0.ComboPooledDataSource.getConnection(ComboPooledDataSource.java:260) at org.apache.torque.TorqueInstance.getConnection(TorqueInstance.java:743) at org.apache.torque.Torque.getConnection(Torque.java:306) at com.tribe.modules.actions.TribeLogin.doPerform(TribeLogin.java:115) at org.apache.turbine.modules.Action.perform(Action.java:48) at org.apache.turbine.modules.ActionLoader.exec(ActionLoader.java:96) at org.apache.turbine.Turbine.loginAction(Turbine.java:880) at org.apache.turbine.Turbine.doGet(Turbine.java:690) at org.apache.turbine.Turbine.doPost(Turbine.java:862) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.UncleanURLFilter.doFilter(UncleanURLFilter.java:74) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:304) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:474) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:409) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312) at org.tuckey.web.filters.urlrewrite.RewrittenUrl.doRewrite(RewrittenUrl.java:183) at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:298) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.HostnameRewriteFilter.doFilter(HostnameRewriteFilter.java:70) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.HibernateSessionFilter.doFilter(HibernateSessionFilter.java:49) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.LinkToolFilter.doFilter(LinkToolFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.ApiFamilyFilter.doFilter(ApiFamilyFilter.java:60) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at net.tribe.filters.UncleanURLFilter.doFilter(UncleanURLFilter.java:74) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:186) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:595)

at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:62) at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:174) at com.mchange.v2.c3p0.PoolBackedDataSource.getConnection(PoolBackedDataSource.java:58) at com.mchange.v2.c3p0.ComboPooledDataSource.getConnection(ComboPooledDataSource.java:260) at org.apache.torque.TorqueInstance.getConnection(TorqueInstance.java:743) ... 66 more — Preceding unsigned comment added by 190.27.11.162 (talk) 21:10, 13 April 2013 (UTC)[reply]

"an error has occurred what were you doing when this error occurred? If you're seeing this page, it means that something has gone wrong on our end.

Sorry about that. Please take a moment to help us fix this problem by giving us a brief description of what you were doing when this error occurred."

Of course, you can't actually submit an error report, since that, itself, also generates an error and a request for an error report.

F'n brilliant really. No wonder I'm not seeing any new sponsors.

Joshua Clement Broyles — Preceding unsigned comment added by 186.29.37.240 (talk) 03:37, 9 June 2013 (UTC)[reply]

aaaand... Valentines Day was a total Tribe.net meltdown which remains unfixed. But since Valentine's Day happened on a Friday, I guess that makes perfect sense. If they get it up and running again by St. Patrick's Day, I think you all know what to expect by now.

OTOH, props to Tribe on the new ads. If nothing else were making Tribe unusable, those would be the next best thing.

- Joshua Clement Broyles — Preceding unsigned comment added by 190.25.50.190 (talk) 22:28, 15 February 2014 (UTC)[reply]

It's not exactly "original research" to note that a URL is dead. At what point will it be reasonable to edit the main article to put tribe.net completely in past tense?

- Joshua Clement Broyles — Preceding unsigned comment added by 190.24.79.75 (talk) 19:47, 17 February 2014 (UTC)[reply]

The URL is functional again, but as of 23 July 2014 the site is no longer accepting any new user data. Sure, this is original research, but it's also a plain fact. When is someone more respected here going to start documenting any of this stuff in the main article? It's like you people care enough to discourage me from sloppy procedures, but not enough to acknowledge the state of the article's content as being importantly different from reality. Thanks for nothing! - Joshua Clement Broyles — Preceding unsigned comment added by 190.25.160.175 (talk) 21:48, 24 July 2014 (UTC)[reply]

Aaaand... as always, a problem that otherwise shows no sign of clearing up (I tested it a few minutes ago) suddenly resolves after I complain about it on this page. This is just getting to be too many coincidences. Thanks for reading, Tribe people! - Joshua Clement Broyles — Preceding unsigned comment added by 190.25.160.175 (talk) 21:56, 24 July 2014 (UTC)[reply]

But of course I spoke too soon. It's just like last night again. - Joshua Clement Broyles — Preceding unsigned comment added by 190.25.160.175 (talk) 01:57, 25 July 2014 (UTC)[reply]

I appreciate the more conspicuous instructions at the top of this page, thanks. It just seems to me like policing the talk page is sort of a moot point if the article isn't being kept current on things like that fact that Tribe.net is a dead URL as of today. OTOH, Wikipedia shouldn't miss the opportunity to update the article with other documented recent activity by Tribe.net management. The Wikipedia article on irony, for example, might benefit from a link to the Tribe.net article, specifically citing the offer of premium services at Tribe.net immediately before Tribe.net becoming a dead URL. Thanks for following up, Editors. - Joshua Clement Broyles — Preceding unsigned comment added by 186.29.238.61 (talk) 16:53, 11 November 2014 (UTC)[reply]

Wow.. the current article is soooo POV and does not comply to Wikipedia's standards...

Yes.. the site is down (I'm a user) but the tribe twitter clarifies... (we will see if it comes back up. https://twitter.com/tribehelp

i know talk is not a general discussion, my reason for posting is there are so few citations in many of the statements and the article needs a cleanup..

121.219.101.254 (talk) 06:42, 8 November 2015 (UTC)[reply]

On October 31, 2015, Tribe announced that they were going down to move to new servers.[2]. As of 9 November, they're still down. I suggest that when they hit 30 days, we change this article to the past tense, but hold off until then. John Nagle (talk) 20:45, 9 November 2015 (UTC)[reply]

I see that the article no longer even mentions instability. This is intellectually irresponsible, given that instability continues to be Tribe's core defining feature, even after all the supposed fixes a few months ago. Is whoever made the more recent edits worried that sponsors will be more scared off by mention of instability in a Wikipedia article than by trying to visit Tribe.net itself and finding nothing? Focusing on the Wikipedia article instead of focusing on Tribe's site stability would reflect the same system of priorities elsewhere demonstrated by Tribe's management. So, yes, I very much do believe they are editing this article contrary to Wikipedia policy, no matter how pointless that may be. - Joshua Clement Broyles — Preceding unsigned comment added by 190.24.79.174 (talk) 17:37, 22 May 2016 (UTC)[reply]

Tribe.net is up today. Very slow, but up. Somebody put a note in the article that it was down, but it's not. John Nagle (talk) 19:12, 1 March 2017 (UTC)[reply]

Hello fellow Wikipedians,

I have just modified one external link on Tribe.net. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive https://web.archive.org/web/20090508140018/http://markpincus.typepad.com/markpincus/2008/11/tribe-deal.html to http://markpincus.typepad.com/markpincus/2008/11/tribe-deal.html

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Y An editor has reviewed this edit and fixed any errors that were found.

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 15:35, 14 December 2017 (UTC)[reply]

Hi, I added some of the recent history at the bottom a couple of weeks ago. When I circled back to see if there'd been any editing, I noticed that the name of the website "Heavy.com" had been dropped from the text here, where the asterisks are:

tribe.net was taken offline in March 2017 after an article on ***** [10] about a Reddit thread[11] described child porn activity on the network.[10][11]

The publication name seems to still be in the coding, but it doesn't show in the article. Rather than muck it up (my html knowledge is superficial at best), I thought I'd just point it out. — Preceding unsigned comment added by 68.173.64.110 (talk) 23:06, 7 April 2018 (UTC)[reply]

If anyone cares, I saw the Reddit thing with the copied content that was considered offensive. I do not condone the conversation in question or the type of conversation in question. But anyone who would consider it to be pornographic must indeed have a very abnormal sense of what is probably intended to be erotic as compared to what is probably intended to be ironically morbid passive trolling via Google spider. The tribe that produced the thread was called "torturing boys". I was not a member or a visitor, thanks. I only saw the content as copied to sites that showed it in order to complain about it. The specific thread consisted of two users talking in not especially graphic (nor very sexual) detail about 2 pertinent crimes they claimed to have committed. I can't speak for everyone, but it caused me to form the impression that neither of them had committed such a crime. I actually have to wonder whether using that to shut down Tribe was a sincere act, opportunism, or possibly even a deliberate false flag. I know that plenty of people whose various information legitimate to copy in to Tribe in order to make such facts easier to find and assemble into coherent character sketches, I had copied in, and that they were pretty unhappy about it. I probably wasn't the only person taking advantage of the super-fast RSS indexing on Google. But the guy I had sued who had not paid up, for example, was pretty freaked out by Googling himself and seeing that someone had already connected a bunch of dots for anyone who might want to sue him next. If I discovered that Tribe was the easiest way to "hang someone with their own rope" (just an expression, OK?), then what I did may have been just the tip of a pretty big, pretty scary iceberg. Many persons lacking the clean hands with which to defend themselves by litigation probably would have been looking for any possible way to get rid of Tribe.net .

ORANGEBOXMAN — Preceding unsigned comment added by 186.31.8.42 (talk) 22:55, 23 May 2018 (UTC)[reply]