☆像穿梭在夜空的风中※

在游戏Find The Lost Ring中，我的测试结果是卡里同，下面的标志可以说明：

 

 

 

 

 

1. What Can Internet Do For Us:

"The network computer, also known as the Internet toaster, Internet appliance or Internet device, is the

low cost, no maintenance desktop device."

2.Building a POP Toaster:

"A POP toaster receives mail for authorized users and lets them pick it up through the network.

A POP toaster has three essential components:
Mailbox storage: saving incoming messages on disk.
Mailbox service: letting users pick up mail through the network.
Account management: setting passwords for authorized users. "

 

 

 

 

The FAQs of Life Online:"I heard someone hooked a toaster to the Internet?! Really?

There really was an Internet toaster. Dan Lynch, President of the Interop Internet networking show, told John Romkey at the 1989 show that he would give him star billing the following year if he connected a toaster to the Internet. Who could have resisted a challenge like that?

Working together with his friend Simon Hackett, John Romkey rose to the occasion and connected a Sunbeam Deluxe Automatic Radiant Control Toaster to the Internet, becoming the hit of the 1990 Interop.

The toaster was connected to the Internet with TCP/IP networking, and controlled with a Simple Networking Management Protocol Management Information Base (SNMP MIB). It had one control, to turn the power on, and the darkness of the toast was controlled by how long the power was kept on.

However, a human being still had to insert the bread. At the 1991 Interop a small robotic crane was added to the system, also controlled from the Internet, which picked up a slice of bread and dropped it into the toaster, automating the system from end-to-end.

 

 

Network Working Group                                       L. Masinter
Request for Comments: 2324                                 1 April 1998
Category: Informational

         Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)

Status of this Memo

  This memo provides information for the Internet community.  It does
  not specify an Internet standard of any kind.  Distribution of this
  memo is unlimited.

Copyright Notice

  Copyright (C) The Internet Society (1998).  All Rights Reserved.

Abstract

  This document describes HTCPCP, a protocol for controlling,
  monitoring, and diagnosing coffee pots.

1. Rationale and Scope

  There is coffee all over the world. Increasingly, in a world in which
  computing is ubiquitous, the computists want to make coffee. Coffee
  brewing is an art, but the distributed intelligence of the web-
  connected world transcends art.  Thus, there is a strong, dark, rich
  requirement for a protocol designed espressoly for the brewing of
  coffee. Coffee is brewed using coffee pots.  Networked coffee pots
  require a control protocol if they are to be controlled.

  Increasingly, home and consumer devices are being connected to the
  Internet. Early networking experiments demonstrated vending devices
  connected to the Internet for status monitoring [COKE]. One of the
  first remotely _operated_ machine to be hooked up to the Internet,
  the Internet Toaster, (controlled via SNMP) was debuted in 1990
  [RFC2235].

  The demand for ubiquitous appliance connectivity that is causing the
  consumption of the IPv4 address space. Consumers want remote control
  of devices such as coffee pots so that they may wake up to freshly
  brewed coffee, or cause coffee to be prepared at a precise time after
  the completion of dinner preparations.

  This document specifies a Hyper Text Coffee Pot Control Protocol
  (HTCPCP), which permits the full request and responses necessary to
  control all devices capable of making the popular caffeinated hot
  beverages.

  HTTP 1.1 ([RFC2068]) permits the transfer of web objects from origin
  servers to clients. The web is world-wide.  HTCPCP is based on HTTP.
  This is because HTTP is everywhere. It could not be so pervasive
  without being good. Therefore, HTTP is good. If you want good coffee,
  HTCPCP needs to be good. To make HTCPCP good, it is good to base
  HTCPCP on HTTP.

  Future versions of this protocol may include extensions for espresso
  machines and similar devices.

2. HTCPCP Protocol

  The HTCPCP protocol is built on top of HTTP, with the addition of a
  few new methods, header fields and return codes.  All HTCPCP servers
  should be referred to with the "coffee:" URI scheme (Section 4).

2.1 HTCPCP Added Methods

2.1.1 The BREW method, and the use of POST

  Commands to control a coffee pot are sent from client to coffee
  server using either the BREW or POST method, and a message body with
  Content-Type set to "application/coffee-pot-command".

  A coffee pot server MUST accept both the BREW and POST method
  equivalently.  However, the use of POST for causing actions to happen
  is deprecated.

  Coffee pots heat water using electronic mechanisms, so there is no
  fire. Thus, no firewalls are necessary, and firewall control policy
  is irrelevant. However, POST may be a trademark for coffee, and so
  the BREW method has been added. The BREW method may be used with
  other HTTP-based protocols (e.g., the Hyper Text Brewery Control
  Protocol).

2.1.2 GET method

  In HTTP, the GET method is used to mean "retrieve whatever
  information (in the form of an entity) identified by the Request-
  URI." If the Request-URI refers to a data-producing process, it is
  the produced data which shall be returned as the entity in the
  response and not the source text of the process, unless that text
  happens to be the output of the process.

  In HTCPCP, the resources associated with a coffee pot are physical,
  and not information resources. The "data" for most coffee URIs
  contain no caffeine.

2.1.3 PROPFIND method

  If a cup of coffee is data, metadata about the brewed resource is
  discovered using the PROPFIND method [WEBDAV].

2.1.4 WHEN method

  When coffee is poured, and milk is offered, it is necessary for the
  holder of the recipient of milk to say "when" at the time when
  sufficient milk has been introduced into the coffee. For this
  purpose, the "WHEN" method has been added to HTCPCP. Enough? Say
  WHEN.

2.2 Coffee Pot Header fields

  HTCPCP recommends several HTTP header fields and defines some new
  ones.

2.2.1 Recommended header fields

2.2.1.1 The "safe" response header field.

  [SAFE] defines a HTTP response header field, "Safe", which can be
  used to indicate that repeating a HTTP request is safe. The inclusion
  of a "Safe: Yes" header field allows a client to repeat a previous
  request if the result of the request might be repeated.

  The actual safety of devices for brewing coffee varies widely, and
  may depend, in fact, on conditions in the client rather than just in
  the server. Thus, this protocol includes an extension to the "Safe"
  response header:

         Safe                = "Safe" ":" safe-nature
         safe-nature         = "yes" | "no" | conditionally-safe
         conditionally-safe  = "if-" safe-condition
         safe-condition      = "user-awake" | token

  indication will allow user agents to handle retries of some safe
  requests, in particular safe POST requests, in a more user-friendly
  way.

2.2.2 New header fields

2.2.2.1 The Accept-Additions header field

  In HTTP, the "Accept" request-header field is used to specify media
  types which are acceptable for the response. However, in HTCPCP, the
  response may result in additional actions on the part of the
  automated pot. For this reason, HTCPCP adds a new header field,
  "Accept-Additions":

      Accept-Additions = "Accept-Additions" ":"
                         #( addition-range [ accept-params ] )

       addition-type   = ( "*"
                         | milk-type
                         | syrup-type
                         | sweetener-type
                         | spice-type
                         | alcohol-type
                         ) *( ";" parameter )
       milk-type       = ( "Cream" | "Half-and-half" | "Whole-milk"
                         | "Part-Skim" | "Skim" | "Non-Dairy" )
       syrup-type      = ( "Vanilla" | "Almond" | "Raspberry"
                         | "Chocolate" )
       alcohol-type    = ( "Whisky" | "Rum" | "Kahlua" | "Aquavit" )

2.2.3 Omitted Header Fields

  No options were given for decaffeinated coffee. What's the point?

2.3 HTCPCP return codes

  Normal HTTP return codes are used to indicate difficulties of the
  HTCPCP server. This section identifies special interpretations and
  new return codes.

2.3.1 406 Not Acceptable

  This return code is normally interpreted as "The resource identified
  by the request is only capable of generating response entities which
  have content characteristics not acceptable according to the accept
  headers sent in the request. In HTCPCP, this response code MAY be
  returned if the operator of the coffee pot cannot comply with the
  Accept-Addition request. Unless the request was a HEAD request, the
  response SHOULD include an entity containing a list of available
  coffee additions.

  In practice, most automated coffee pots cannot currently provide
  additions.

2.3.2 418 I'm a teapot

  Any attempt to brew coffee with a teapot should result in the error
  code "418 I'm a teapot". The resulting entity body MAY be short and
  stout.

3. The "coffee" URI scheme

  Because coffee is international, there are international coffee URI
  schemes.  All coffee URL schemes are written with URL encoding of the
  UTF-8 encoding of the characters that spell the word for "coffee" in
  any of 29 languages, following the conventions for
  internationalization in URIs [URLI18N].

coffee-url  =  coffee-scheme ":" [ "//" host ]
               ["/" pot-designator ] ["?" additions-list ]

coffee-scheme = ( "koffie"                      ; Afrikaans, Dutch
                 | "q%C3%A6hv%C3%A6"          ; Azerbaijani
                 | "%D9%82%D9%87%D9%88%D8%A9" ; Arabic
              | "akeita"                   ; Basque
              | "koffee"                   ; Bengali
              | "kahva"                    ; Bosnian
              | "kafe"                     ; Bulgarian, Czech
              | "caf%C3%E8"                ; Catalan, French, Galician
                 | "%E5%92%96%E5%95%A1"       ; Chinese
                 | "kava"                     ; Croatian
              | "k%C3%A1va                 ; Czech
              | "kaffe"                    ; Danish, Norwegian, Swedish
              | "coffee"                   ; English
              | "kafo"                     ; Esperanto
                 | "kohv"                     ; Estonian
              | "kahvi"                    ; Finnish
              | "%4Baffee"                 ; German
              | "%CE%BA%CE%B1%CF%86%CE%AD" ; Greek
              | "%E0%A4%95%E0%A5%8C%E0%A4%AB%E0%A5%80" ; Hindi
              | "%E3%82%B3%E3%83%BC%E3%83%92%E3%83%BC" ; Japanese
              | "%EC%BB%A4%ED%94%BC"       ; Korean
              | "%D0%BA%D0%BE%D1%84%D0%B5" ; Russian
              | "%E0%B8%81%E0%B8%B2%E0%B9%81%E0%B8%9F" ; Thai
              )

  pot-designator = "pot-" integer  ; for machines with multiple pots
  additions-list = #( addition )

  All alternative coffee-scheme forms are equivalent.  However, the use
  of coffee-scheme in various languages MAY be interpreted as an
  indication of the kind of coffee produced by the coffee pot.  Note
  that while URL scheme names are case-independent, capitalization is
  important for German and thus the initial "K" must be encoded.

4. The "message/coffeepot" media type

  The entity body of a POST or BREW request MUST be of Content-Type
  "message/coffeepot". Since most of the information for controlling
  the coffee pot is conveyed by the additional headers, the content of
  "message/coffeepot" contains only a coffee-message-body:

  coffee-message-body = "start" | "stop"

5. Operational constraints

  This section lays out some of the operational issues with deployment
  of HTCPCP ubiquitously.

5.1 Timing Considerations

  A robust quality of service is required between the coffee pot user
  and the coffee pot service.  Coffee pots SHOULD use the Network Time
  Protocol [NTP] to synchronize their clocks to a globally accurate
  time standard.

  Telerobotics has been an expensive technology. However, with the
  advent of the Cambridge Coffee Pot [CAM], the use of the web (rather
  than SNMP) for remote system monitoring and management has been
  proven.  Additional coffee pot maintenance tasks might be
  accomplished by remote robotics.

  Web data is normally static. Therefore to save data transmission and
  time, Web browser programs store each Web page retrieved by a user on
  the user's computer. Thus, if the user wants to return to that page,
  it is now stored locally and does not need to be requested again from
  the server. An image used for robot control or for monitoring a
  changing scene is dynamic. A fresh version needs to be retrieved from
  the server each time it is accessed.

5.2 Crossing firewalls

  In most organizations HTTP traffic crosses firewalls fairly easily.
  Modern coffee pots do not use fire. However, a "firewall" is useful
  for protection of any source from any manner of heat, and not just
  fire. Every home computer network SHOULD be protected by a firewall
  from sources of heat. However, remote control of coffee pots is
  important from outside the home. Thus, it is important that HTCPCP
  cross firewalls easily.

  By basing HTCPCP on HTTP and using port 80, it will get all of HTTP's
  firewall-crossing virtues. Of course, the home firewalls will require
  reconfiguration or new versions in order to accommodate HTCPCP-
  specific methods, headers and trailers, but such upgrades will be
  easily accommodated. Most home network system administrators drink
  coffee, and are willing to accommodate the needs of tunnelling
  HTCPCP.

6. System management considerations

  Coffee pot monitoring using HTTP protocols has been an early
  application of the web.  In the earliest instance, coffee pot
  monitoring was an early (and appropriate) use of ATM networks [CAM].

  The traditional technique [CAM] was to attach a frame-grabber to a
  video camera, and feed the images to a web server. This was an
  appropriate application of ATM networks. In this coffee pot
  installation, the Trojan Room of Cambridge University laboratories
  was used to give a web interface to monitor a common coffee pot.  of
  us involved in related research and, being poor, impoverished
  academics, we only had one coffee filter machine between us, which
  lived in the corridor just outside the Trojan Room. However, being
  highly dedicated and hard-working academics, we got through a lot of
  coffee, and when a fresh pot was brewed, it often didn't last long.

  This service was created as the first application to use a new RPC
  mechanism designed in the Cambridge Computer Laboratory - MSRPC2. It
  runs over MSNL (Multi-Service Network Layer) - a network layer
  protocol designed for ATM networks.

  Coffee pots on the Internet may be managed using the Coffee Pot MIB
  [CPMIB].

7. Security Considerations

  Anyone who gets in between me and my morning coffee should be
  insecure.

  Unmoderated access to unprotected coffee pots from Internet users
  might lead to several kinds of "denial of coffee service" attacks.
  The improper use of filtration devices might admit trojan grounds.
  Filtration is not a good virus protection method.

  Putting coffee grounds into Internet plumbing may result in clogged
  plumbing, which would entail the services of an Internet Plumber
  [PLUMB], who would, in turn, require an Internet Plumber's Helper.

  Access authentication will be discussed in a separate memo.

8. Acknowledgements

  Many thanks to the many contributors to this standard, including Roy
  Fielding, Mark Day, Keith Moore, Carl Uno-Manros, Michael Slavitch,
  and Martin Duerst.  The inspiration of the Prancing Pony, the CMU
  Coke Machine, the Cambridge Coffee Pot, the Internet Toaster, and
  other computer controlled remote devices have led to this valuable
  creation.

9. References

  [RFC2068] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., and T.
  Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2068,
  January 1997.

  [RFC2186] Wessels, D., and K. Claffy, "Internet Cache Protocol (ICP),
  version 2," RFC 2186, September 1997

  [CPMIB] Slavitch, M., "Definitions of Managed Objects for Drip-Type
  Heated Beverage Hardware Devices using SMIv2", RFC 2325, 1 April
  1998.

  [HTSVMP] Q. Stafford-Fraser, "Hyper Text Sandwich Van Monitoring
  Protocol, Version 3.2". In preparation.

  [RFC2295] Holtman, K., and A. Mutz, "Transparent Content Negotiation
  in HTTP", RFC 2295, March 1998.

  [SAFE] K. Holtman. "The Safe Response Header Field", September 1997.

  [CAM] "The Trojan Room Coffee Machine", D. Gordon and M. Johnson,
  University of Cambridge Computer Lab,
  <http://www.cl.cam.ac.uk/coffee/coffee.html>

  [CBIO] "The Trojan Room Coffee Pot, a (non-technical) biography", Q.
  Stafford-Fraser, University of Cambridge Computer Lab,
  <http://www.cl.cam.ac.uk/coffee/qsf/coffee.html>.

  [RFC2235] Zakon, R., "Hobbes' Internet Timeline", FYI 32, RFC 2230,
  November 1997.  See also
  <http://www.internode.com.au/images/toaster2.jpg>

  [NTP] Mills, D., "Network Time Protocol (Version 3) Specification,
  Implementation and Analysis", RFC 1305, March 1992.

  [URLI18N] Masinter, L., "Using UTF8 for non-ASCII Characters in
  Extended URIs" Work in Progress.

  [PLUMB] B. Metcalfe, "Internet Plumber of the Year: Jim Gettys",
  Infoworld, February 2, 1998.

  [COKE] D. Nichols, "Coke machine history", C. Everhart, "Interesting
  uses of networking", <http://www-
  cse.ucsd.edu/users/bsy/coke.history.txt>.

10. Author's Address

  Larry Masinter
  Xerox Palo Alto Research Center
  3333 Coyote Hill Road
  Palo Alto, CA 94304

  EMail: masinter@parc.xerox.com

11.  Full Copyright Statement

  Copyright (C) The Internet Society (1998).  All Rights Reserved.

  This document and translations of it may be copied and furnished to
  others, and derivative works that comment on or otherwise explain it
  or assist in its implementation may be prepared, copied, published
  and distributed, in whole or in part, without restriction of any
  kind, provided that the above copyright notice and this paragraph are
  included on all such copies and derivative works.  However, this
  document itself may not be modified in any way, such as by removing
  the copyright notice or references to the Internet Society or other
  Internet organizations, except as needed for the purpose of
  developing Internet standards in which case the procedures for
  copyrights defined in the Internet Standards process must be
  followed, or as required to translate it into languages other than
  English.

  The limited permissions granted above are perpetual and will not be
  revoked by the Internet Society or its successors or assigns.

  This document and the information contained herein is provided on an
  "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
  TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
  BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
  HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
  MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

 

 

2007年9月3日，大巴载着兴奋的我在雨后山林的公路上穿行，新的旅途总是让我找回独自上路旅行的新鲜好奇和对下一站的生活的向往。这一天,我来到了广西的沙田柚之乡容县，开始了我为期2个月的分局见习生活。

虽然这是我第一次来到容县，但无论是这儿的城市面格局，还是周围的人的融洽气氛，都给了我一种熟悉亲切的感觉。容县是个和我的家乡贺州八步差不多大的县城，但却有着更悠久的历史和更浓重的岁月沉淀。有着镂花石栏的一座老桥下，涓涓秀江分割了城区南北。江北是由过去的老城区发展而来的商业中心，但可爱的是，有一条窄而深长的老街两旁仍保全着建于民国时期的青砖骑楼宅群。斑驳的墙角和石柱上泛出的苔绿和蕨类植物无声地诉说着岁月的沧桑。白天一个人走在这安静的老街巷里，仿佛自己成了那久远年代中的过客。

容县的人，我把他们缩影到我们单位了。马局长给我强烈的亲切感，感觉上他太像我姑丈了！矮胖敦实的他就像是水果摊老板，一对铜玲眼前挡了两块四方玻璃倒也勉强增加几分知识分子的形象。他衣着朴实，讲话爽直，不摆领导架子，一副实干家模样。后来发现果真如我所想，马局和容县很多有点钱的人一样自己开有家庭式小工厂，有小车有好房，属于有财不外露的精干型企业家。营业厅的营业员也都很好说话，特别是领班黄姐有着富有感染力的乐观精神，乐呵呵地和我们说着家常闲话、单位里名人佚事；她读小学四年纪的女儿也每天到营业厅来等妈妈下班，我们陪她写作业、聊天，童心无忌，活泼可爱。看到她们幸福和谐的家庭气氛，自己也感觉到那份温暖。带我们出工的师傅和我们一样都是二十五岁以下的年轻小伙子，而且同住一栋楼，个性爽快的他们更是无话不说，呵呵。

单位在江南都峤小学附近的居民区有一栋6层楼的普通家庭式住房，1楼是车库和仓库，2楼是机房，3楼住了领班黄姐一家三口，往上住的就是我、同来见习的小胡和两个师傅。这让我想起在海南旅游时住过的家庭式小旅馆。我有幸一个人住在了顶楼的独户小房间，宽敞整洁。推开前窗旁的铁门，出去就是铺有隔热转的晒台，在这里可以眺望到不远处的工业园区和一级公路旁青葱的山林。我很感激能有这样一个不易受干扰的空间，既能轻易接触到室外流畅空气又有开阔视野，使我下班后得以在这里安静地看书、思考生活，将那份信念擦拭得更为明亮。有时，感觉到夜风如同匆匆过客般从前后窗穿过我的房间，窗帘、日历和铁丝上挂着的衣服如钟摆轻轻晃动，敲响时间的钟声。

突然就觉得，生命是如此的短暂。

如果生命是一场旅途，那就好好欣赏沿途的每道风景吧。    

       2007年6月23日晚，骑着自行车穿行在这个城市的流光溢彩中。
       一个人的周末。为了习惯这感觉，还是选择陷入陌生的环境、陌生的人群中，看看世界上的另一个陌生人有着怎么样的生活。因为看着别人的生活，就暂时忘记了自己的生活吧。
       区图书馆报告厅里有着浓重的黑暗和冷气；从那扇厚重的门进来的我，一下觉得视线朦胧，脚步发飘；身体一下子碰到了墙壁。索性就缓下来，闭上眼深呼吸了一口。再张开眼时，我看到了黑白光影的人和整齐的椅子；光的来源，是大厅前方幕布上那幅会动的画面。
       法国影片《薇诺妮卡的双重生命》。
       盯着这暖色调的电影画面，声音这才钻进了耳朵。到感觉坐姿有点累了的时候，才发现已经不知不觉坐下来沉浸在影片中良久了。
       影片的整体色调，用某人的原话来说，是“从天空到大地一体都是浓得化不开的金黄色，而这种金黄色在现实中是不存在的，所以这部片带着浓重的幻想色彩。”偏偏我就是个超喜欢这种色调的人。咖啡厅从吊顶上悬吊下来的那种灯金黄的灯光，明秀校区后门街道路灯那种金黄的灯光，床头那盏可调亮度大小的台灯金黄的灯光。看了就让人很舒服，觉得即使一个人也可以很宁静生活的。
       还看过另一部类似的法国影片《天使爱米莉》。也发现，越来越喜欢法国的文艺、剧情电影。感觉就像是看一盘斯诺克，白球潇洒地在彩色球中穿行，轻轻地碰撞后又轻巧打个转，退回合适的位置。剧情就这样不紧不慢而吸引人地发展着。靠在商店橱窗上往里看时会呵一口气让玻璃变得朦胧，对面公寓年轻的邻居会用闪光的镜子来和你打招呼，你收到另一个国家的人寄来的一个空的雪茄盒子……法国人的浪漫主义，让你在看到这些小细节时会心一笑，然后向往。真是会享受幻想的民族……若是他们的生活里少了幻想和种种希望与期待，我怀疑他们是否真的可以忍受？
       薇诺妮卡感到突然的难过和孤独，因为世界上的另一个薇诺妮卡死了，心电感应告诉她她失去了自己生命的一部分；尽管她不知道那部分生命是什么，但她感觉到了孤独。我们感到孤独的时候，是不是我们生命的一部分也离我们而去了？世界上是否还有另一个样貌、生活轨迹都像自己一样的人呢？世界上应该还有很多和我们这样的个体想法相似的人吧？他们的生活是怎么样的？如果能透过他们的生活看到自己可以成为的种种未来，我们就能更好地选择自己的生活方式了吧？
      ……
      生活有时候给人幻想，有时候又现实得让人害怕。你是选择让灵魂来奴役你的身体，还是选择让身体奴役你的灵魂呢？
      我要去听GreenDay的“Jesus of Suburbia”了。

得从下午说起吧。

 

下午3点，广州发展银行在明秀外语楼报告厅开专场的招聘会，很多大四的同学都是为投简去的（不知其中是否也有像我这样已经落实了工作，好奇跑去看热闹的），所以坐了满满一堂的人。（题外话：因为是招就处的人负责布置会场，在门口似乎看到v薇薇v在热情地招呼同学们入场；之后似乎又见到奶茶MM也来了……以上是时空师院版的两水友）虽然是招客服，而且专业不限，但和南宁一般的公司待遇比起来，广发的待遇挺不错的，听得我也有些心动。不过我觉得男生还是先学点技术的好，而且我入的电信业近两年看似也还蛮有搞头的，所以对自己说，还是安心去自己的单位干吧！

 

完了遇到系党支部副书记梁老师，和我们说了一通道理，肯定是怕我们安不下心来找工作而弄得他完成不了上面给的就业指标…… BS！！ 讲耶酥讲完了，嘿嘿刚好走到学校超市，9个学生每人小宰了他一支雪糕  

 

5点整，在电话里和小谢打了声招呼，就背着吉他（没错，吉他是我一早预谋好就带来了滴，甚至还带到了报告厅的招聘会现场了嘿嘿）去他家找他一起玩琴…… Building Blocks的两把吉他终于又重现江湖！ 激动得,再次感叹年轻真好啊，so Let's rock baby~

 

听了一堆绿洲后小谢说，今晚是学校最后一次英语角了，有没兴趣啊？我说，近来有什么牛人在那里出没吗？他不屑，没有啊，不过他们想叫我出节目，如果你也去我们现在练首简单的等下一起上了为～  哈哈， 我当然爽啊！ 想当年英语角基本上成了偶们乐队的专场舞台啊，如今再Yesterday once more，是个不错的回忆！于是就选了绿洲的Merry with children狂练两小时（不行，我手指想抽筋啊）……

 

英语角是9点开始。让我很高兴的是，现在这一届英协学习部的人比较活跃，英语角上搞了电影经典对白、学唱经典英文歌、嘉宾演讲等新节目，而且主持人口语也不错，文综楼前的同学很快就聚拢过来了（不过搞那么多节目比较适合在长岗校区，明秀这边的人嘛还是老样子，直接上来见人就free talk,都不去听舞台上的主持人在说什么鸟语的 - -!）。

 

9点10分小谢把一把木吉他扛在肩上从文综楼里走出来，靠～ 竟然穿他N年前那件Pink Floyd的Tshirt喔？？ 我可是穿Giordano的有领短袖耶，明显不搭调啊谢小子！！

 

算了衰样，我上去喊住了他。拉开吉他袋，掏出我的Fender大厢木电来，两人和以前一样坐在楼前靠墙的角落做着最后的排练。感觉不错。下面不少人已经开始注意到我们（难道是我们排练声音太吵？ - -!）。主持人来请了。拍拍屁股，抓起吉他走上前去，就在Stage的台阶上坐了下来。主持人帮拿话筒。呵呵，和以前完全一样啊。我只是打节奏兼起调，小谢是主唱兼solo（妈的，谁叫我是今天才听的这首歌啊，歌词都不熟，明显不给我这个第二主唱发挥啊！）。

 

伴着右手拨片的扫动，E和弦清脆的声音响起在音箱里，show time begins.话筒消失了，观众也消失了，眼前是一片明亮的色彩，耳边是爽朗的吉他节奏。华彩进来了，像是活跃的思想现形化了的音符纽带。“There‘s no need for you to say you're sorry...”我们唱了起来，我听到了音箱里也传出了好听的声音。果然，还是不插电的效果是最好的啊！第一、第二段感觉很好，但中间不知何时开始我也有弹错，小谢有唱错或忘词，但是我们都不在意了，仍然让手中的音符流淌，彼此坏坏地笑着一副嘲弄对方的样子：SB，你这衰样啊……  嘿嘿，感觉好爽！这个，始终还是我们熟悉的Stage啊！

 

太过沉醉了，结果歌曲结尾没处理好，差点变成死循环，汗…… 主持人边寒暄边送给我们笔记本当礼物，走下来时暗爽还捞奖品了哇哈哈～  翻开笔记本一看差点吐血！是给小学生写字用的有格子的本子……

 

丢了礼品在墙角，跑到下面来闲逛，发现今晚的老外蛮多啊！有5个吧？爱尔兰的外教两夫妇，2个美国帅哥留学生，还有一个不知哪国的女生（没去搭讪所以不知道）。觉得那两个美国帅哥留学生比较可爱，人很好讲也不摆架子，而且在众女生的包围下他们似乎倾向于和我统一战线，所以超想和他们侃啊！可是已经差不多要赶车回长岗了，郁闷得～  平时老外也见了不少，但不是哪个老外都会给你这种亲切感的，要是能成为朋友就好了！ 继续怀念一下当年的Jay和Sean以及和他们一起7的日子。

 

和帅哥美女侃到9点53分，要走了。收拾好东西，回头望了一眼英语角，这片留恋了我大学3年身影的地方，同时也是留下了多少校园传奇人物的地方（至少在我眼里他们是闪耀着星光一般璀璨光亮的前辈）。在这里总算遇到了些熟面孔，但是也很多新人辈出啊！英语角办成这样，看来号召力和影响力还是蛮强的嘛，突然觉得想要向这一届的英协干部致敬，不仅因为在他们身上看到了自己当年的影子，也看到了新的有活力的团队和他们所带来的希望，青出于蓝啊！

 

希望所有人都能找到属于自己的一个圈子，开心、自信、自在书写着属于我们自己的独一无二人生。