This blog is rated 🔞, viewer discretion is advised

打劫别人的botnet

这年头,botnet都可以被人打劫。。。来自Google Tech Talk

  1. 屏蔽botnet控制服务器的ip
  2. 破解botnet的fastflux算法
  3. 抢注一个肉鸡即将切换到的 fastflux 的域名
  4. ???
  5. ALL YOUR BOTNET ARE BELONG TO ME

演讲里这个家伙打劫到的这个Torpig botnet有17Gbps带宽的DoS能力。。。

via

Posted

archive

海地360°视频

CNN提供的海地视频,360°拍摄的。1, 2, 3

技术是Immersive Media提供的。Google Street View以前也是Immersive Media的技术

via

Posted

archive

[zz]原来文曲星还能这么用 = =

发信人: bblalala (miaomiao), 信区: WebGame
标  题: Re: 本来琢磨着是不是用JS写个套利的东西…
发信站: 水木社区 (Fri Jan 22 18:36:35 2010), 站内

中学的时候正流行文曲星,比较新的款都带qb编程的 我那时候编了一个输入两个人名字看般配度的程序 然后传给全班人玩 其实那个程序偷偷做了个后门,把输过的名字存下来了 传回我手上就能看到谁输了什么。。。爆出不少八卦呢。。。

Posted

archive

差别对待

一方面

百度理应受到搜索引擎避风港原则的保护。

另一方面又说:

谷歌在内的外资企业应尊重承担相应的社会责任

真TMD佩服当年WTO谈判的家伙,把洋大人忽悠得团团转啊。

常见段子对还有:

经济总量 – 人均值

国际接轨 – 特殊国情

有了这些段子对,几乎就是万能借口了。

今天又看到领导的秘密一文:

不管是动物还是人,都有一种本能:把自己置于一个头领的统治之下。

所以,作为领导,你要动员群众,只需要做两件事就可以了:断言重复

Posted

archive

中国人与狗不得上twitter

今天看到ISS上宇航员已经开始直接发twitter了

ISS twitter

前几个月NASA在地面帮助宇航员@Astro_Mike更新tweet,总部SB还报道了这个事情,前些天还说ISS上收发email是通过定时交换Outlook的.ost文件做到的,没想到现在都可以直接实时发tweet了。估计NASA的带宽也不便宜啊。呵呵。

早就厌烦被当作墙的技术支持和客服了。每当别人问我twitter怎么上的时候。一般都一句话回答:中国人与狗不得上twitter。

Posted

archive

whitehouse.gov 的造价是 $20,000,000

【免责申明】我不是50分RMB党,下面的内容仅供参考。

Disclaimer: The content below is FYI only

关于最近鳖帝当局那个破网站几百万升级费的事情,以前也写过相关话题。

whitehouse.gov 的造价是$20,000,000,而且是被波音公司承包做的。用老外的话说就是

yes.. boeing and other “military” contractors win website contracts over established firms because they know how to play the goverment contracting game

另外一个网站recovery.gov使用了Drupal开源CMS系统,据传重新设计页面(redesign)花了$18,000,000

米帝和鳖帝都很彪悍~~~呵呵。。。

Posted

archive

LiquidMetal™的玻璃合金

不锈钢 vs LiquidMetal™玻璃合金 vs 钛

http://video.google.com/videoplay?docid=-939151540119819530

a material which can store a very high density of elastic energy, becomes the premier material when that performance benchmark is critical. Any material which can efficiently store elastic energy up to very high densities which is superior to other materials in that respect will be the premier material for those kinds of applications.

这玩意儿真orz。。。。最后那钢珠跳动声音越来越密集听起来很有趣。。。

via

Posted

archive

2.0 version of theSixtyOne is awesome!

My favorite online music website theSixtyOne.com, just released a new version. It was awesome!

theSixtyOne 2.0

theSixtyOne 2.0

I really love the innovative way of how it displays artists photos slides with the music on :)

This is something you can never experience from MTVs or mp3’s. It is great revolution of music from a corporate product, to good old times when you actually watch and listening to others singing their stories, but with digital artistic expressions.

That’s what music all about!

Posted

archive

yo2要等到5月份才能确定是否继续开放了

网友咨询yo2得到的回复:

目前,绑定域名和免费用户都已经恢复(但需要翻墙访问,使用VPN或者代理服务器的形式)。用户可以用代理登录到Yo2进行博客内容备份,如需要下载上传的图片文件,请email联系。我们会及时处理~

2010年的网络审核一直会持续到5月,在此期间Yo2的国内服务器无法提供服务。5月后需要看实际情况,再考虑国内服务器的加入,全面恢复访问。 Yo2 也将停止域名备案的审核事宜,请不要使用Yo2的服务器信息进行备案。我们已无法协助大家审核备案的事情,还请见谅

太杯具了。

Posted

archive

LuaJIT2成为Google内部新宠?

今天Google Opensource官方博客专门发贴赞美了LuaJIT

We use Lua internally at Google

Joshua Haberman在gmane.comp.lang.lua.general里提到过:

Our Lua usage isn’t too widespread at the moment; it’s really one infrastructure project in particular that uses Lua to allow user-defined functions to run within a tightly controlled container. Lua was the best choice, because of its low overhead, fast execution, and the ability to set limits on execution time.

Unfortunately I cannot be more specific, since the project is not public.

看来google要推Lua了。Google目前LuaJIT Project赞助商,而且在支持x86-64版本的移植开发工作。

LuaJIT2的牛牛牛牛牛牛牛牛牛牛牛牛牛牛逼大家都见过了吧。。。云风的BLOG上有跟踪系列报道。

Unladen Swallow已经正式提交PEP-3146准备merge到CPython,sw-python既没有达到5x性能提升的目标,也没有移除GIL,连Q4都没有发布。

via

Posted

archive

data.gov.uk rocks

有点长,想tl;dr的就自己去玩吧。 http://data.gov.uk/data/tag。以下博文带博主主观色彩,不喜勿看。

第一次关注 英帝gov网站 是因为n年前一个很有意思的新闻:英国将关闭90%以上的政府网站 大刀阔斧搞瘦身

[...] 到2003年初,含有英国政府域名.gov.uk的各类网站已突破3000个,每年投资费用达到140亿英镑 [...] 951个政府网站当中只有26个会确定保留,551个网站将被关闭,而其余几百个在重新评估后,也将大部分关闭。 [...] 今后英国政府的信息将主要通过direct.gov.uk和Business Link这两个网站提供

不知道PRC有多少个。有兴趣的可以做个 site:gov.cn 搜索结果页面数数。

今天在 R/W Web上读到 UK Launches Open Data Site; Puts Data.gov to Shame

data.gov.* 是主要面向API应用的网站,也就是面向程序员和开发者,里面提供了SPARQL查询接口,这个 SPARQL 是语义互联网标准RDF的重要单元,我是前几个月看到Zed Shaw在玩BBC的 music ontology才发现SPARQL这个玩意儿的重要性的。

这里有个app例子,就是显示1996-2009房价

英帝的data.gov.uk有3,000个数据集,相比之下米帝的data.gov只有1,000个,而且还比别人早开6个月。看来Obama竞选是吼得凶做得少啊。

不过这个data.gov.uk也有灌水嫌疑,有些数据集是链接到其他 .gov.uk 的网页,并没有实际查询和IO功能。

不仅如此,英帝还万恶的鼓励大众使用和展示这里面的数据,Show Us A Better Way,用更好的方式展示数据,让更多普通人如何容易地接受数据。还有£20,000的奖励。这也是virtualization的一个比较好的商业化渠道啊。

data.gov.uk是Guardian一手发起和推动的。Guardian这报纸真反动啊,怎么能为百姓说话,而不为英帝工党说话呢?

After a long-running campaign by the Guardian which began in March 2006 demanding that the government make the non-personal data it collects available for unrestricted reuse, the launch marks a significant victory – especially together with plans announced by Gordon Brown in November to make Ordnance Survey mapping data and some postcode data also available for free.

WWW之父 Tim Berners-Lee 也被雇用参与了 data.gov.uk 的设计和发布。

Berners-Lee was hired last June by Gordon Brown, to ensure “that government information is accessible and useful for the widest possible group of people”.

Tim在TED也有相关演讲

科学量化+现代社会 == WIN。大不列颠又一次走在了人类文明最前面。宝宝在炒作物联网概念的时候,别人已经在,就像当年米帝gov带头推动信息高速公路那样,实实在在一步一步推动semantic web的发展了。

via

btw 我知道你们要在下面评论 @aiww 一直在做的那个统计,那个事情就不要提了,了解就行,麻烦不要写在这里,免得触发big brother的敏感神经。

Posted

archive

tg的逻辑啊。。。

话说啊这人一心虚啊,嘴就打哆嗦,尽说些让人摸不着头脑的话。例如

To combat terrorism after the “9/11″ terrorist attack, the U.S. has permitted police to search civilian emails and even monitor their communications without permission.

截图作为证据

太牛了。

好多人在GRE作文才是人生第一次上逻辑课。。。

via

Posted

archive

Password FFFFFFUUUUUUU

Does anybody else think it’s a general usability issue?

For the best user experience, it’s necessary for an application to steal focus when busy typing.

via

Posted

archive

qq理论上已经实现实名制[zz]

发信人: ENV (白天图生存,晚上谋发展), 信区: ITExpress
标 题: 今天听闻QQ已经间接实现实名制了
发信站: 水木社区 (Wed Jan 20 15:43:02 2010), 站内

刚才跟一个据称圈内人士的说,qq根据用户对好友添加的别名(备注姓名)信息进行统计,91%的活跃用户都可以追查到真实姓名

发信人: superisaac (宅男总动员), 信区: ITExpress
标 题: Re: 今天听闻QQ已经间接实现实名制了
发信站: 水木社区 (Wed Jan 20 15:44:37 2010), 站内

是阿,同学群里一般都用真名阿

发信人: fly2never (逆飞的鱼), 信区: ITExpress
标 题: Re: 今天听闻QQ已经间接实现实名制了
发信站: 水木社区 (Wed Jan 20 15:48:56 2010), 站内

群里确实是真名,备注一般都是外号

Posted

archive

靠,不要说Google真把全球网民当枪使了

看到 《消息人士称陈永正将接管谷歌中国》

不得不说,如果这是真的,这Google的全球营销手段太牛了。。。。

首先说,Google官方并没有明确表态说一定会撤出,官方原文说的是a new approach,就是说新的方式,并没有说bye bye China。

We recognize that this may well mean having to shut down Google.cn, and potentially our offices in China.

这句话被媒体和网民潜意识感觉无限放大了。

不过这个战略动作真的是一石n鸟啊。。。扇tg一耳光,让国内网民肉搏tg,国外炒作,然后百度出丑,微软出丑,Yahoo出丑,然后自己光荣革命,重返大陆,瞬间提升全球好感。。。。

Google 所有属性+1, 攻击+1,防御+1,名声+1
Baidu 防御 -1 名声-1
CCAV 攻击 -1 防御 -1 名声-1
Diang 攻击-1,防御-1,名声 -1

谁TMD想的这烂点子啊。。。太绝了。。。。CCAV还一个劲儿批Google,看来都被当枪使了。。。。

如果上面的假设被后来的事实证明,这Google简直就是长得性感一点的FRJJ啊。。。。

从某种角度来说,Diang在做的封锁啊屏蔽啊,只是增加了一种市场落差,给以后的drama增加了更大的自由程度和发挥空间。。。而对保持power稳定起不到任何作用。。。Diang每解决一个问题,总是习惯的带来10个更大更严重的问题。。。。。Diang咋就不明白这个道理呢。。。。。

Posted

archive

Tesla的白炽灯已经亮了109年了

爱迪生的对手,Tesla制造的白炽灯灯泡,现在著名得都有一个名称了,Centennial Light,在Fire Station 6, in Livermore, northern California,从1901年开始已经亮了109年了。这是Guinness世界纪录里最古老的还在工作的灯泡。

全世界的Tesla fans还专门制作了一个网站 http://www.centennialbulb.org/。MythBusters 在 December 13, 2006 对这个灯泡做了个节目。

现在国内买的无论节能灯还是白炽灯的寿命真的很短。。。

via

Posted

archive

这些单词你认识么。。。

aes. ees, ef, gee, aitches, ies, jy, kay, ell, em, en, oes, pee, cue, ar, esses, ues, exes, wye

连续看可能你懂,但是有的时候上下文突然冒一个出来就楞了。。。

Posted

archive

Look Around You

BBC有一个Look Around You系列。。。。英式冷笑话太有才了。。。捶地啊。。。laugh

这一集是讲化学符号为 H20 的元素。。。。 (Unicode写法:H₂₀)

Thants! Blants!

Posted

archive

查词典的经常遭遇

redditor们在下面的评论也是各尽所长专挑罕见词来装逼。。。。。FFFFFFFFFFFFFFFFFFFFFFFFUUUUUUUUUUUUUUUUUUUUUU

Posted

archive

sitcom的秘密

有人把美剧 The Big Bang Theory 的背景笑声去掉了,结果就是这样子的:

从中可以看出sitcom的秘密,comedies are all about pacing and timing: laughter breaks.

See also:

The Wire with a laugh track

可以看出,气氛是全靠渲染的。。。五毛的舆论引导其实就是一种气氛渲染。

感觉生活中的acting也不少啊,汉人都讲个委婉和含蓄。

via

Posted

archive

好吧。。。yo2.cn算是完蛋了

最近快被各个地方的网友逼疯了。。。都在问 initiative.yo2.cn 这个blog怎么了。。。汗死。。。都不去看yo2.cn主页上的公告么?其实任何 *.yo2.cn 都打不开好久了。

我现在才发现一个很神奇的事情,那就是好多人都是直接输入 initiative.yo2.cn 这个网址来访问我的blog的。。。很震惊。。。我的blog都值得直接记住域名了。。。大家太看起小弟了。。。。

这里提供一个围观yo2.cn遗迹的方法,还是编辑hosts文件

60.29.250.75    initiative.yo2.cn

然后 ipconfig /flushdns 然后重启浏览器就可以看 yo2.cn 上的博客了。

那么blog也就[b]正式独立[/b]出来了。yo2.cn导出的Wordpress WXR有9MB大,import比较困难,所以就不准备搬家了,本地把内容和评论和附件存个档备份就行了。大家凑合着Google Cache和上面的hosts方法看吧。呵呵。

那么这里的blog也就准备开放Google索引和继续母语写作了。如果被河蟹了那只能说明不幸。。。。

hosting用的是Dreamhost的 $9 促销空间,域名也是今年7月份到期,到时候是否renew再看着办吧 :)

本blog备用网址/IP:

http://initiative.dreamhosters.com/

http://☯.dreamhosters.com/

Wherever we are, it’s alright here:

Posted

archive

Hans Rosling on poverty

Ever wondered why we still living in a third world country in poverty both materially and spiritually, and we can’t have nice things?

Hans Rosling on poverty, from TED

                    Means     Goal
  Human Rights       +         +++
  Environment        +         ++
  Governance         ++        +
  Economic growth    +++       0
  Education          ++        ++
  Health             +         ++
  Culture            +         +++

from zeuux-universe

Posted

archive

Technology behind G StreetView

Vehicles:

first generation

second generation

third generation

  • 6 cameras aimed in 360 degree spaced equally
  • There was one camera facing the sky, that helped correct light settings of other cameras to get a good shot.
  • They shot 30fps video
  • the driver has a Monitor/Keyboard int the front, to stop, pause, mark wildlife on side of road (lots of deer, elk, etc), something scenic, points of interest.
  • Typical 7-10 hour a day would go through a 1 Terabyte Hard Drive
  • The cars with the LARGE setups are the newer cameras. Under the camera, there are 3 white devices, one straight forward, and two to the sides. These are 3d imaging devices recording the shape of everything the car is going by.
  • Driver’s job is 75 unique miles per day. 40 hours per week but no weekends, getting $15 per hour
  • They only shot public highways and roads. No gravel roads (damage to camera from gravel kicking up), no private roads, no military roads, and no private property roads.
  • They don’t have a schedule, routes are random and up to driver for most part

via

Posted

archive

The brain codes nouns in 3 ways

Scientists crack brain’s codes for noun meanings

the three codes or factors concern basic human fundamentals:

  1. how you physically interact with the object (how you hold it, kick it, twist it, etc.);
  2. how it is related to eating (biting, sipping, tasting, swallowing);
  3. how it is related to shelter or enclosure.

This is quit significant suggestion for how to optimize learning knowledge process, especially for quick understanding of abstract concepts.

via

Posted

archive

“wild wild west” aspect of the internet

From TFA:

Fun fact: Google’s security team managed to penetrate one of the servers being used by the attackers, which was how the full extent of the attack—more than 30 companies—was revealed.

redditor Dax420 says:

This is why I have always loved the “wild wild west” aspect of the internet. When shit happens you don’t simply call the internet police, you do your own detective work and if necessary take action to stop it.

Posted

archive

The regional Internet matrix

I am trying to sum up the dimensions of regional Internet

Regional = [ timezone | geo-region | language ]

which can be defined in

  • browser settings, thus HTTP request headers
  • browser components, like toLocaleDateString(), toLocaleTimeString, tolocaleLowerCase(), tolocaleUpperCase(), toLocaleString() in Javascript, and any browser specific or vendor specific scriptable interface.
  • cookie
  • session
  • Flash cookie (aka LocalSharedObject)
  • URL (like hl=zh_CN&)
  • profile website and product specific profile. Example in Google profile your language is English(US) while your in Google Calendar settings you choose English(UK)
  • target website ccTLD
  • DNS settings
  • third party data provision like oAuth or OpenID
  • IP address and other lower-level or higher-level network identifiers, most maliciously, RTT combined with a accurate route table
  • (to be added)

This is why making comparison and getting conclusions are hard to be scientific complete and correct.

To protect network neutrality, fuck all kinds of regional Internet.

Viva la Résistance!

Posted

archive

music genre [PIC]

Which body parts different genres of music sing about

via 1, 2, 3

Posted

archive

Zeroday.Scene.Rules.v2010-RULES

Zeroday.Scene.Rules.v2010-RULES

      ______      _______ ______    _______    _____      _____    _______
    _/   _  )__ _/  _   /_\     \ _/  _   /_ _/     \_   /   _/_ _/  _   /__
    \   _/     \\  -\___\ \\     \\  -\___\ \\   _\   \--\___   \\  -\___\  \
   /    \       ? _/      ?     ? _/      ?  \     ?  :/    ? _/      _\
 ?_____:\_____/____________\      \________/____:\_____\_______/___________\ 
                            /______/                                          
                        _______
   _______   _____ _____\      \   __________    _____
  /   __  )__\    \\    \\      \ /    _    /   /   _/____
 /   /_      \     \     \       \\   -\____\---\___      \   0day scene 2010
/      \      ?    \     .       .   _/      .   :/       \
\______:\______\___________\       \___________\___________/?----------------+
.                          /_______/                       .                  


This is intended as an addendum to the existing 0day rules. All the old rules 
are still valid, unless they have been altered or updated by this addendum.

The 0day scene has gone through major changes in this decade. As technologies 
have changed, so have we, but our adaptations have left many grey areas in the 
current rules. The last rules update was years ago when programs were much 
smaller and transfer speeds much lower. The existing 0day rules did not address 
problems of software encountered today, simply because at that date it did not 
exist. These changes have led to a series of loopholes which groups have been 
taking advantage of. The new rules we constructed aim to close these loopholes,
as well as increase the general quality level of releases in the scene.

This document covers a new ruleset for 0day.  These rules and guidelines are
intended for release-groups in the first place, and sites secondary. We hope 
that in time many sites will take over the majority of these rules. The 
following groups have signed and committed to following these rules:

     ACME AiR AGAiN ALiAS ARN BACKLASH BEAN BLiZZARD BRD CORE CRD 
        CROSSFiRE DIGERATI DVT EMBRACE FALLEN FAS iNViSiBLE LND
             MESMERiZE NGEN NULL ORiON OUTLAWS RiTUEL ROGUE
                   SHOCK SSG TBE UNLEASHED VACE ZWT 

These rules will go into effect starting January 31st, 2010.

* Release Name
~~~~~~~~~~~~~~

[<Developer.name>.]<Program.name>.v<Version>[.<Language>][.<OS>][.<CPU>]
[.<Release.Type>][.<Additional.Tags>]-<Groupname>

Developer.Name is only mandatory if the application name is not unique enough
for duping. Groups should use some common sense to keep the directory name 
reasonable length.

The program name should be the "official" name of the application. Do not omit
dashes, think of your dupe results.

The Language tag must be used only on NON english releases. Multilingual and
bilingual are optional.

Currently valid OS tags are: 
        - Win98, WinME, WinNT, Win2k, WinXP, Win2k3, Vista, Win2k8, Win7
          (can have an optional tag for more specific edition)
        - [Distribution.]Linux
        - MacOSX
        - [Free|Net|Open]BSD
        - [Open]Solaris
        - AIX
        - HPUX
        - Open.Enterprise.Server (NetWare)

The Operating.System tag should be omitted when WinAll (= NT5 based windows 
and optionally earlier, always with latest official service pack). Using a 
UnixAll (= all of the operating systems above, excluding Windows, Linux or 
MacOSX) or a WinAll tag means your app *must* run on *all* of the operating 
systems that fall under it.

CPU should be omitted when x86, must be x64 for x86_64/EM64T, but not IA64!
Currently valid CPU tags are: 
        - x86, x64, IA64, PPC, SPARC, SPARC64, RISC, Alpha

Release.Type can be omitted for Crack/Regged, but is mandatory for keygen
releases. Possible tags are:
        - Keygen.Only Keymaker.Only
        - Incl.Keygen Incl.Keymaker
        - Incl.Keygen.and.Patch Incl.Keymaker.and.Patch
        - Cracked
        - Regged

Additional.Tags like READ.NFO, DIRFIX, NFOFIX.. must go as follows:
  - DevelopersName.ProgramName.v1.2.Regged.READ.NFO-GROUP
  - DevelopersName.ProgramName.v1.2.Regged.DIRFIX-GROUP

You can use underscores or dots as seperator in the releasename, but do not mix
them if there is no reason for it (e.g. a program name contains underscores and
your seperator is a dot is a valid reason to mix)

The lists in this section are by no means complete. They are here to serve as a
guideline for proper dirname construction.

* Packaging:
~~~~~~~~~~~~

Filenames must be named up to a maximum of 8.3 characters (filename/extension).

Acceptable compression format at this time is any compression method that
supports multiple volumes and long file names, followed by the traditional
PKZIPing. Compressions other than RAR should include an extract utility or be a
self-extracting archive.

The traditional packaging methods (zip/diz) shall be maintained, with a diz 
file being present in each zip. The diz file should contain as a bare minimum 
the number of the current disk and the maximum number of disks. 

Suggested file_id.diz layout is as follows:
  [xx/??], where ?? is the total nr of disks in the release. The total number 
  of lines of your diz should not exceed 30.

On a side note: using ridiculous compressions that will save 10 disks but takes
10 hours to unpack are not an acceptable solution.

* Release Size:
~~~~~~~~~~~~~~~

Allowed split volume sizes are:
        - 1,444,000 bytes
        - 2,888,000 bytes
        - 5,000,000 bytes
        - 10,000,000 bytes
        - 50,000,000 bytes

The utils disk limit is as of now 70 x 5,000,000 bytes or 35 x 10,000,000 bytes. 
This equates to a total of 350,000,000 bytes of compressed data. Oversize 
releases are allowed when no ISO release exists and the group (or an iso group 
they work with) is not in possession of the iso to release. In other words, 
there is NO size limit for 0day apps, except when an iso exists!

The games disk limit is as of now 80 x 5,000,000 bytes or 40 x 10,000,000 bytes.
This equates to a total of 400,000,000 bytes of compressed data.

Any release should have less than 100 volumes. In case 10,000,000 bytes do not
suffice, you are allowed to use volumes of larger size; up to 50,000,000 bytes.

A size proper is valid when a group manages to reduce the size of the original 
release by at least 30% without sacrificing essential content:

 - Documentation, help files, and other non functional items can be ripped from 
   a release to decrease size. No functional parts of an application may be 
   ripped.
 - C++ redistributables, .NET framework, and other common operating system 
   components may be ripped. The nfo should note what has been ripped and 
   optionally include an url where it can be downloaded.
 - A documentation addon is only allowed if the documentation cannot be 
   downloaded freely and publicly (without registration) from the developer's 
   website.

* Specific Release Type:
~~~~~~~~~~~~~~~~~~~~~~~~

All of these releases should provide functionality identical to that of a fully
licensed copy.

- Cracked: The program file has been altered to register the program. Any 
  nags/trial limitations should be removed. Any remnants of "Trial" in the app
  need to be removed. Any "phone-home" checks should be disabled!

- Regged: Any way to make an application "registered" without requiring
  modification of any of the applications executables/libraries. Must include
  a text file with the required information, serials should not be put in the
  release nfo. Please name this file carefully, as to deter possible 
  webspiders looking for serial information.

- Keygen: A small standalone program which generates valid serials/keyfiles
  which are based on user input or hardware id.

  Keygens can be written in any language but they should be native executables
  for the OS the application is meant for: Linux keygens for Linux applications,
  Mac keygens for Mac applications, etc. This means that if you do not follow
  this suggestion, you could get propered. However, you won't be nuked if there
  is no native keygen available.

  A keygen that generates a system-dependant serial must explicitly warn the
  user of this fact, either in the nfo OR at runtime.

  Windows keygens in java are allowed if the the program is coded in java or 
  uses java. Same with any other interpreter language. If a library is included
  with the latest windows install, as is the case for VB6/.NET/VBScript 
  currently, then keygens written in these languages are allowed without 
  question. The motivation here is that a scene release should run on a clean
  OS install, introducing no additional dependencies other than those imposed
  by the application being released.

  A console-based application that usually runs on headless systems (servers, 
  etc) requires a console-based keygen.

  Generic Keygens (All.Products) are allowed and dupe full releases for as long
  as the generic keygen continues to work for *every* application it was
  intended for.

  Keygen.Only releases are releases that only contain the actual keygen, no
  installation files. They are meant as an addition to previous Crack/Regged
  releases. 

  A Keygen.and.Patch release combines a keygen with a crack to enable full
  functionality. You are still allowed to release a keygen.only for these
  releases.

- Retail: A store-bought supply is included in this release. You are allowed to
  release a retail after a previous release if there is an added benefit to
  using the retail version. In this case you are required to add a READ.NFO tag
  to your dirname and list the benefits when compared to the previous release.

- PROPER/WORKING: a proper of a previous scene-release that was not fully 
  working should always include adequate proof and information for nukers to 
  test and confirm the validity of the proper. This means including screenshots,
  pieces of code, or clear steps to reproduce the problems that occur with
  the release you are propering.

- READ.NFO: If you label a release READ.NFO, please have a clearly stated 
  section in your nfo on what the READ.NFO is all about, dont make people guess.
  If you want people to read it for a certain reason, make sure they can.


* Operating Systems:
~~~~~~~~~~~~~~~~~~~~

If a developer has not mentioned default or minimum requirements for operating
system, the default is Windows XP, which is also a minimum.

If a program supports Windows Operating Systems before WinXP, then your crack
*should* work on them aswell.

Optional: combine multiple operating system versions for the same CPU in 1 
release if it remains within size limits, for example:
- FreeBSD5,6,7 x86 can be in a single release tagged FreeBSD
If the installers are freely downloadable (available without registration) and 
the same keygen/crack works for every version, consider only including the 
latest version of the OS.

Please keep in mind that the contents of .tar.gz, .rpm, .deb and any other
packaging system are generally identical. Please make a note in your nfo in
case of exceptions.

* Minor Updates:


MU stands for Minor Update. This term denotes an update of a previously 
released application within a certain time-period, the MU-period. Major updates
are allowed regardless of the last time a previous version was released. In
this case, the nfo should include some motivation for considering this a major
update (security- and stability-critical hotfixes for instance)

MU-period of 1 month, disregarding the number of days in a month. Examples:

- a release on 2010-01-01 will be out of mu on 2010-02-01
- a release on 2010-01-15 will be out of mu on 2010-02-15
- a release on 2010-01-29 will be out of mu on 2010-02-28
- a release on 2010-01-31 will be out of mu on 2010-02-28
- a release on 2010-02-28 will be out of mu on 2010-03-28
- a release on 2010-03-31 will be out of mu on 2010-04-30

This ensures no more than a single release of the same application per month,
while keeping duping simple. 

The minor update period is counted from the last valid release which contained 
the software itself. In other words, keymaker.only releases are not considered.

* General Rules:
- If the age of the last modified file of an installed program is older than one (1) year it is not allowed to pre it without a READ.NFO or INTERNAL tag. - A group should release the newest version of the software available. Exceptions are possible when the software is not available publicly, or if it was never released before, which *must* be mentioned in the nfo-file. This means you can release an older version of an application, but *only* if it is newer than any existing release of the same app, and you have a valid reason for not releasing the latest version (for instance, it is very hard to get the supply, or the application takes months to crack). There is a grace-period of 3 days: if a new version came out in the last 3 days before your release, you will not get nuked if you release the older one. - Releases should provide the same functionality as a retail copy of the application (where possible and reasonable). Examples: - a virus scanner must be able to update - a flexlm application should include every useful feature - a keygen should provide either all, or the best license (watermarks are still allowed) - Your nfo should provide a minimum of useful information, including: - (complete) application name - (complete) version, including if it is a beta version - the release date - type of crack included - short description of the application/game - description on how to use the crack (important!) - operating systems this release will work on - pre-requisites for the application/game - url to the application's website - If you do not want your work to be used by other groups (be it documents, cracking methods, tools, or similar), then make sure you don't give it out to anyone you can't trust. It is deemed public property as soon as it is publicly available, and you lose any exclusive rights to it. - Stealing cracks/keygens from P2P, WEB, or other scene groups is clearly not allowed! - Security should be everyone's primary concern. Including nicknames or identities of people that have not given explicit permission in your nfo's is absolutely not allowed, and may result in severe repercussions. A big thanks to everyone involved in creating this document! Last modified: 10 January 2010

Posted

archive

Adobe: fuck you China

Since the Google.cn withdraw from China is hyper hot topic now, I have nothing fresh to share. Just show you guys something else:

http://blogs.adobe.com/conversations/2010/01/adobe_investigates_corporate_n.html

Adobe became aware on January 2, 2010 of a computer security incident involving a sophisticated, coordinated attack against corporate network systems managed by Adobe and other companies. We are currently in contact with other companies and are investigating the incident. At this time, we have no evidence to indicate that any sensitive information–including customer, financial, employee or any other sensitive data–has been compromised. We anticipate the full investigation will take quite some time to complete. We have and will continue to use information gained from this attack to make infrastructure improvements to enhance security for Adobe, our customers and our partners.

Looks like the GhostNet is true. I feel sorry for my past shameless defending the Party on various discussion boards and forums.

Posted

archive

Google search results batch removal

If you have your robots.txt properly configured, then visit

https://www.google.com/webmasters/tools/removal-create?siteUrl=http://your_site_domain/

Instead of

https://www.google.com/webmasters/tools/removals

Sneaky Google bastard hiding batch removal options from everyone. Well played Google!

Posted

archive

The Neurons that built civilization

or watch it on TED.com

Key points (SPOILER ALERT!):

  1. Mirror neurons makes human evolution suddenly Lamarckian instead of Darwinian. That’s why culture is the base of civilization.

  2. The second kind of mirror neurons makes empathy. But empathy is different from reality, example: you do not actually experience someone touch other’s arm, because receptors in your skin has a negative feedback to your brain. You will have a phantom touch if anesthetize your arm :)

  3. The Eastern philosophy: there is no real independent self. You are in fact, connected not just via Facebook, and Internet, you’re actually quite literally connected to everyone around you by your neurons. And there is no real distinctiveness of your consciousness from somebody else’s consciousness.

  4. The culture and civilization, is unique to all human beings. (Fuck I never thought unique could mean that)

  5. Neuroscientist Vilayanur Ramachandran’s speech was great, but I didn’t think empathy belongs to human exclusively, perhaps other animals has empathy too but with a weaker and less sophisticated degree. and I think he emphasis too much on visions. What if people are blind?

  6. Contrary evidence and opinion for mirror neurons: read this [PDF]

via

Posted

archive

Photo of Mars

what are those weird tendril thingies?

In the Martian winter, carbon dioxide freezes out of the air (and you thought it was cold where you are). In the summer, that CO2 sublimates; that is, turns directly from a solid to a gas. When that happens the sand gets disturbed, and falls down the slopes in little channels, which spreads out when it hits the bottom. But this disturbs the red dust, too, which flows with the sand. When it’s all done, you get those feathery tendrils. Note that at the tendril tips, you see blotches of red; that’s probably from the lighter dust billowing a bit before settling down.

We’ve seen this before on Mars

via

Posted

archive