Bitcoin Forum
April 25, 2024, 02:18:22 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Bitcoin Forum > Bitcoin > Bitcoin Discussion > Request For Action from Jeff Garzik on Freenode as Group Contact for #Bitcoin-*
Pages: [1]
« previous topic next topic »
  Print  
Author Topic: Request For Action from Jeff Garzik on Freenode as Group Contact for #Bitcoin-*  (Read 1349 times)
mizerydearia (OP)
Hero Member
*****
Offline Offline

Activity: 574
Merit: 507



View Profile
October 19, 2011, 05:26:27 AM
Last edit: October 19, 2011, 11:13:24 AM by mizerydearia
 #1
Update: Apparently this is not a bfd and I shall chill out.  My apologies for not being chill.

TLDR:
Jeff Garzik, Please help recover the following channels: #bitcoin-bg, #bitcoin-br, #bitcoin-es, #bitcoin-eu, #bitcoin-in, #bitcoin-lu, #bitcoin-otc-sv, #bitcoin-ru, #bitcoin-sv

Suggestion: /msg #freenode I am the group contact for Bitcoin-* namespace and would like to regain the following channels: #bitcoin-bg, #bitcoin-br, #bitcoin-es, #bitcoin-eu, #bitcoin-in, #bitcoin-lu, #bitcoin-otc-sv, #bitcoin-ru, #bitcoin-sv

More Details:
It has been twelve days since my initial request for action to Jeff Garzik and through several days of noticeable Internet (e.g. IRC) activity, he has failed to take responsibility or action in this situation where he is the sole existence on entire planet Earth that has permission to handle the #bitcoin-* namespace on Freenode IRC network to resolve this issue according to Freenode policy.

-ChanServ- Information on #bitcoin-bg:
-ChanServ- Founder    : xnljoffer
-ChanServ- Registered : Jun 07 21:06:00 2011 (19 weeks, 0 days, 08:15:43 ago)
-ChanServ- Last used  : Jun 07 21:06:00 2011 (19 weeks, 0 days, 08:15:43 ago)
-ChanServ- Mode lock  : +ntc-slk
-ChanServ- *** End of Info ***

-ChanServ- Entry Nickname/Host          Flags
-ChanServ- ----- ---------------------- -----
-ChanServ- 1     xnljoffer              +votsriRfAF [modified 19 weeks, 0 days, 08:16:14 ago]
-ChanServ- ----- ---------------------- -----
-ChanServ- End of #bitcoin-bg FLAGS listing.

-NickServ- Information on xnljoffer (account xnljoffer):
-NickServ- Registered : Jun 07 21:05:28 2011 (19 weeks, 0 days, 08:23:24 ago)
-NickServ- Last addr  : ~xnljoffer@92-247-217-213.spectrumnet.bg
-NickServ- Last seen  : Jun 07 21:54:44 2011 (19 weeks, 0 days, 07:34:08 ago)
-NickServ- Flags      : HideMail
-NickServ- *** End of Info ***




-ChanServ- Information on #bitcoin-br:
-ChanServ- Founder    : fetokun
-ChanServ- Registered : May 04 11:13:03 2011 (23 weeks, 6 days, 18:09:05 ago)
-ChanServ- Last used  : Jun 08 08:40:28 2011 (18 weeks, 6 days, 20:41:40 ago)
-ChanServ- URL        : http://meubitcoin.com.br/cotacoes
-ChanServ- Flags      : KEEPTOPIC GUARD
-ChanServ- *** End of Info ***

-ChanServ- Entry Nickname/Host          Flags
-ChanServ- ----- ---------------------- -----
-ChanServ- 1     fetokun                +votsriRfAF [modified 23 weeks, 6 days, 18:09:17 ago]
-ChanServ- ----- ---------------------- -----
-ChanServ- End of #bitcoin-br FLAGS listing.

-NickServ- Information on fetokun (account fetokun):
-NickServ- Registered : May 04 10:24:43 2011 (23 weeks, 6 days, 19:04:21 ago)
-NickServ- Last addr  : 57195294@gateway/web/freenode/session
-NickServ- Last seen  : Jun 08 08:40:28 2011 (18 weeks, 6 days, 20:48:36 ago)
-NickServ- Flags      : HideMail
-NickServ- *** End of Info ***




~6-10 in channel and no ops
-ChanServ- Information on #bitcoin-es:
-ChanServ- Founder    : tuxsoul
-ChanServ- Registered : May 01 02:15:58 2011 (24 weeks, 3 days, 03:06:25 ago)
-ChanServ- Last used  : Aug 02 01:48:17 2011 (11 weeks, 1 day, 03:34:06 ago)
-ChanServ- Mode lock  : +ntc-slk
-ChanServ- Flags      : SECURE KEEPTOPIC TOPICLOCK GUARD
-ChanServ- *** End of Info ***

-ChanServ- Entry Nickname/Host          Flags
-ChanServ- ----- ---------------------- -----
-ChanServ- 1     tuxsoul                +votsriRfAF [modified 24 weeks, 3 days, 03:06:29 ago]
-ChanServ- ----- ---------------------- -----
-ChanServ- End of #bitcoin-es FLAGS listing.

-NickServ- Information on tuxsoul (account tuxsoul):
-NickServ- Registered : Oct 22 05:39:27 2004 (6 years, 51 weeks, 5 days, 23:49:43 ago)
-NickServ- Last addr  : ~tuxsoul@189.226.100.47
-NickServ- Last seen  : Aug 04 20:18:49 2011 (10 weeks, 5 days, 09:10:21 ago)
-NickServ- Flags      : HideMail
-NickServ- *** End of Info ***




-ChanServ- Information on #bitcoin-IN:
-ChanServ- Founder    : dishwara
-ChanServ- Registered : May 05 09:26:49 2011 (23 weeks, 5 days, 19:55:40 ago)
-ChanServ- Last used  : May 05 09:26:49 2011 (23 weeks, 5 days, 19:55:40 ago)
-ChanServ- Mode lock  : +ntc-slk
-ChanServ- *** End of Info ***

-ChanServ- Entry Nickname/Host          Flags
-ChanServ- ----- ---------------------- -----
-ChanServ- 1     dishwara               +votsriRfAF [modified 23 weeks, 5 days, 19:55:43 ago]
-ChanServ- ----- ---------------------- -----
-ChanServ- End of #bitcoin-IN FLAGS listing.

-NickServ- Information on dishwara (account dishwara):
-NickServ- Registered : Feb 04 15:37:47 2011 (36 weeks, 4 days, 13:51:30 ago)
-NickServ- Last addr  : ~dishwara@unaffiliated/dishwara
-NickServ- Last seen  : Jun 22 02:21:07 2011 (17 weeks, 0 days, 03:08:10 ago)
-NickServ- Flags      : HideMail
-NickServ- *** End of Info ***




-ChanServ- Information on #bitcoin-lu:
-ChanServ- Founder    : delpes
-ChanServ- Registered : Jun 20 17:43:24 2011 (17 weeks, 1 day, 11:39:11 ago)
-ChanServ- Last used  : Jun 20 23:00:49 2011 (17 weeks, 1 day, 06:21:46 ago)
-ChanServ- Mode lock  : +ntc-slk
-ChanServ- Flags      : GUARD
-ChanServ- *** End of Info ***

-ChanServ- Entry Nickname/Host          Flags
-ChanServ- ----- ---------------------- -----
-ChanServ- 1     delpes                 +votsriRfAF [modified 17 weeks, 1 day, 11:39:15 ago]
-ChanServ- ----- ---------------------- -----
-ChanServ- End of #bitcoin-lu FLAGS listing.

-NickServ- Information on delpes (account delpes):
-NickServ- Registered : Jun 18 23:06:35 2011 (17 weeks, 3 days, 06:22:50 ago)
-NickServ- Last addr  : bc63e27c@gateway/web/freenode/ip.188.99.226.124
-NickServ- Last seen  : Jul 08 10:02:50 2011 (14 weeks, 4 days, 19:26:35 ago)
-NickServ- Flags      : HideMail
-NickServ- *** End of Info ***




~5 in channel and no ops
-ChanServ- Information on #bitcoin-otc-sv:
-ChanServ- Founder    : crouge
-ChanServ- Registered : Jun 08 21:51:24 2011 (18 weeks, 6 days, 07:31:29 ago)
-ChanServ- Last used  : Oct 16 18:17:13 2011 (2 days, 11:05:40 ago)
-ChanServ- Mode lock  : +ntc-slk
-ChanServ- *** End of Info ***

-ChanServ- Entry Nickname/Host          Flags
-ChanServ- ----- ---------------------- -----
-ChanServ- 1     crouge                 +votsriRfAF [modified 18 weeks, 6 days, 07:31:35 ago]
-ChanServ- ----- ---------------------- -----
-ChanServ- End of #bitcoin-otc-sv FLAGS listing.

-ChanServ- Information on #bitcoin-sv:
-ChanServ- Founder    : crouge
-ChanServ- Registered : Jun 09 09:28:52 2011 (18 weeks, 6 days, 01:36:49 ago)
-ChanServ- Last used  : Jun 09 12:48:51 2011 (18 weeks, 5 days, 22:16:50 ago)
-ChanServ- Mode lock  : +ntc-slk
-ChanServ- *** End of Info ***

-ChanServ- Entry Nickname/Host          Flags
-ChanServ- ----- ---------------------- -----
-ChanServ- 1     crouge                 +votsriRfAF [modified 18 weeks, 6 days, 01:36:51 ago]
-ChanServ- ----- ---------------------- -----
-ChanServ- End of #bitcoin-sv FLAGS listing.

-NickServ- Information on crouge (account crouge):
-NickServ- Registered : May 28 21:57:38 2011 (20 weeks, 3 days, 07:31:59 ago)
-NickServ- Last addr  : ~matthew@user211.77-105-227.netatonce.net
-NickServ- Last seen  : Oct 16 18:17:13 2011 (2 days, 11:12:24 ago)
-NickServ- Flags      : HideMail
-NickServ- *** End of Info ***




~4 in channel and no ops
-ChanServ- Information on #bitcoin-ru:
-ChanServ- Founder    : Akinava
-ChanServ- Registered : May 18 05:36:02 2011 (21 weeks, 6 days, 23:47:00 ago)
-ChanServ- Last used  : Oct 11 15:17:03 2011 (1 week, 0 days, 14:05:59 ago)
-ChanServ- Mode lock  : +ntc-slk
-ChanServ- *** End of Info ***

-ChanServ- Entry Nickname/Host          Flags
-ChanServ- ----- ---------------------- -----
-ChanServ- 1     Akinava                +votsriRfAF [modified 21 weeks, 6 days, 23:47:03 ago]
-ChanServ- ----- ---------------------- -----
-ChanServ- End of #bitcoin-ru FLAGS listing.

-NickServ- Information on Akinava (account Akinava):
-NickServ- Registered : May 12 06:45:28 2011 (22 weeks, 5 days, 22:44:15 ago)
-NickServ- Last addr  : ~lis@pff.eltel.net
-NickServ- Last seen  : Oct 11 15:17:35 2011 (1 week, 0 days, 14:12:08 ago)
-NickServ- Flags      : HideMail
-NickServ- *** End of Info ***
Even in the event that an attacker gains more than 50% of the network's computational power, only transactions sent by the attacker could be reversed or double-spent. The network would not be destroyed.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
mizerydearia (OP)
Hero Member
*****
Offline Offline

Activity: 574
Merit: 507



View Profile
October 19, 2011, 09:11:18 AM
 #2
Quote
<ircdearia> According to one freenode staff member and in combination with previous discussion in this channel, one must wait 70 days of inactivity before a replacement token is provided to file for a replacement GRF.  My question concerning replacement of group contact is one in which the group contact is active on freenode, but not active in taking responsibilty or following up on concerns for a particular established group on freenode.  The particular group contact is not authoritative figure for group (beyond scope of freenode), but merely the first-come-first-serve person to have taken iniitiative to register the group (but again has since abandoned all further responsibilities/actions).  I would like to know if the 70-day inactivity is based on their logging in to freenode account or is based on some other measurement such as even if they are active on freenode that perhaps 70 days have passed in which they have not taken any responsibility in relation to the group or if the 70 days is in response to not taking responsibility or action (accepting or rejecting) for one or more particular issues in which only a group contact can take action (according to freenode policy).
<christel> ircdearia: that's news to me, it sounds like someone has managed to confuse channel expiry and replacement of gc and thus provided you with somewhat inaccurate information
<ircdearia> christel, the 70 days reference was suggested by Corey.
<christel> then i suspect he's managed to confuse himself, it happens Smiley
<ircdearia> Ah, in that case, can you better explain what can be done in the case of a group contact avoiding further responsibility/action in managing a group on freenode?
<christel> well, someone (preferrably someone senior within the project) may contact us and explain that they need to file for replacement, we may ask a question or two to make sure we understand and to enable us to pull the previous contact in a not too unpleasant manner, we provide a token for use on the form and off you go
<christel> it's pretty simple
<christel> Smiley
<ircdearia> christel, Okay, thanks.  Also, in what way do you determine seniority?  Perhaps git commits or forum account registration dates?  Maybe contacting one or more people involved in the community for verification or approval of seniority?
<christel> it varies from project to project, some have a founder/project lead which can act in that role
Pages: [1]
  Print  
Bitcoin Forum > Bitcoin > Bitcoin Discussion > Request For Action from Jeff Garzik on Freenode as Group Contact for #Bitcoin-*
 « previous topic next topic »
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!