Re: [compress] BZip2 block size is invalid

[Stefan Bodewig]

On 2016-02-21, Gary Gregory wrote:

> Caused by: java.io.IOException: BZip2 block size is invalid
>   at
>   
> org.apache.commons.compress.compressors.bzip2.BZip2CompressorInputStream.init(BZip2CompressorInputStream.java:251)

Are you sure this is a valid bzip2 file - i.e. can command line bzip2
uncompress it?

If so, please open a JIRA ticket and attach the file in question (or
directly create a unit test from it :-)

Cheers

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

RE: [crypto][chimera] Next steps

[Chen, Haifeng]

Thanks Benedikt, Uma, Gary, Ole, and Emmanuel Bourg for your support! It's 
great to have Chimera to be part of Apache Commons. 

>>[ Emmanuel Bourg] Define the scope of the project? Do we go after Bouncy 
>>Castle and aim for an equivalent feature set?
Agree to make a clear scope of the project. The original Chimera scope is not 
go after a Bouncy Castle style of library. It targets the gap between the 
application and the under cipher implementations. For example, applications 
uses a lot of InputStream/OutputStream or Channel concepts to read / write a 
stream of data. Application can share these Crypto streams/channel 
implementations abstracting various input and output types. Chimera also 
targets to very important performance optimizations on AES which is used 
worldwide. I suggest this module to be still lightweight and clear in 
involving, which is the same ideology of Apache Commons.

>> [Uma] Here I would like to introduce Haifeng, who lead the efforts in 
>> Chimera github project.
Thanks Uma for introduction.

>> [Uma] Me and Haifeng had some discussion yesterday for the list to get 
>> commit prevs. May be he could probably get list. Then I think Commons PMC 
>> can make a decision on it.
Chimera has 5 long standing contributors on github. We can also invite those 
who contributed the HDFS encryption feature (HDFS-6134 and HADOOP-10150) to 
continue participate the involution of this project if they want.

Thanks,
Haifeng

-Original Message-
From: Gangumalla, Uma [mailto:uma.ganguma...@intel.com] 
Sent: Sunday, February 21, 2016 3:07 AM
To: Commons Developers List 
Subject: Re: [crypto][chimera] Next steps

Hi Benedikt,

 Thank you for the Next steps discussion. I thought of pinging you on this
:-)
  
 Here I would like to introduce Haifeng, who lead the efforts in Chimera github 
project. 
 
I think Apache Commons Crypto looks good and self descriptive IMO.
 I am +1

Me and Haifeng had some discussion yesterday for the list to get commit prevs. 
May be he could probably get list. Then I think Commons PMC can make a decision 
on it.


>move code to an Apache repo (probably git?!)
+1 for git

>- setup maven build
If this point is just about maven build alone, then we should set up Jenkins CI 
build boat as well right, may be we can add this point?

Regards,
Uma 

On 2/20/16, 8:29 AM, "Gary Gregory"  wrote:

>Who are the committers comming along for this component?
>
>Do we have enough of them?
>
>I like Apache Commons Crypto.
>
>Gary
>On Feb 20, 2016 3:15 AM, "Benedikt Ritter"  wrote:
>
>> Hi,
>>
>> I'd like to discuss the next steps for moving the Chimera component 
>>to  Apache Commons. So far, none of the other PMC members has 
>>expressed his or  her thoughts about this. If nobody brings up 
>>objections about moving the  component to Apache Commons, I'm assuming 
>>lazy consensus about this.
>>
>> So the next steps would be:
>> - decide on a name for the new component (my proposal was Apache 
>> Commons
>> Crypto)
>> - move code to an Apache repo (probably git?!)
>> - request a Jira project
>> - setup maven build
>> - setup project website
>> - work on an initial release under Apache Commons coordinates
>>
>> Anything missing?
>>
>> Regards,
>> Benedikt
>>
>> --
>> http://home.apache.org/~britter/
>> http://twitter.com/BenediktRitter
>> http://github.com/britter
>>


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [crypto][chimera] Next steps

[Gary Gregory]

Would Commons Crypto focus only on AES? If so, Commons Crypto AES or Commons
AES would be a better name.

Gary

On Sun, Feb 21, 2016 at 6:28 PM, Chen, Haifeng 
wrote:

> Thanks Benedikt, Uma, Gary, Ole, and Emmanuel Bourg for your support! It's
> great to have Chimera to be part of Apache Commons.
>
> >>[ Emmanuel Bourg] Define the scope of the project? Do we go after Bouncy
> Castle and aim for an equivalent feature set?
> Agree to make a clear scope of the project. The original Chimera scope is
> not go after a Bouncy Castle style of library. It targets the gap between
> the application and the under cipher implementations. For example,
> applications uses a lot of InputStream/OutputStream or Channel concepts to
> read / write a stream of data. Application can share these Crypto
> streams/channel implementations abstracting various input and output types.
> Chimera also targets to very important performance optimizations on AES
> which is used worldwide. I suggest this module to be still lightweight and
> clear in involving, which is the same ideology of Apache Commons.
>
> >> [Uma] Here I would like to introduce Haifeng, who lead the efforts in
> Chimera github project.
> Thanks Uma for introduction.
>
> >> [Uma] Me and Haifeng had some discussion yesterday for the list to get
> commit prevs. May be he could probably get list. Then I think Commons PMC
> can make a decision on it.
> Chimera has 5 long standing contributors on github. We can also invite
> those who contributed the HDFS encryption feature (HDFS-6134 and
> HADOOP-10150) to continue participate the involution of this project if
> they want.
>
> Thanks,
> Haifeng
>
> -Original Message-
> From: Gangumalla, Uma [mailto:uma.ganguma...@intel.com]
> Sent: Sunday, February 21, 2016 3:07 AM
> To: Commons Developers List 
> Subject: Re: [crypto][chimera] Next steps
>
> Hi Benedikt,
>
>  Thank you for the Next steps discussion. I thought of pinging you on this
> :-)
>
>  Here I would like to introduce Haifeng, who lead the efforts in Chimera
> github project.
>
> I think Apache Commons Crypto looks good and self descriptive IMO.
>  I am +1
>
> Me and Haifeng had some discussion yesterday for the list to get commit
> prevs. May be he could probably get list. Then I think Commons PMC can make
> a decision on it.
>
>
> >move code to an Apache repo (probably git?!)
> +1 for git
>
> >- setup maven build
> If this point is just about maven build alone, then we should set up
> Jenkins CI build boat as well right, may be we can add this point?
>
> Regards,
> Uma
>
> On 2/20/16, 8:29 AM, "Gary Gregory"  wrote:
>
> >Who are the committers comming along for this component?
> >
> >Do we have enough of them?
> >
> >I like Apache Commons Crypto.
> >
> >Gary
> >On Feb 20, 2016 3:15 AM, "Benedikt Ritter"  wrote:
> >
> >> Hi,
> >>
> >> I'd like to discuss the next steps for moving the Chimera component
> >>to  Apache Commons. So far, none of the other PMC members has
> >>expressed his or  her thoughts about this. If nobody brings up
> >>objections about moving the  component to Apache Commons, I'm assuming
> >>lazy consensus about this.
> >>
> >> So the next steps would be:
> >> - decide on a name for the new component (my proposal was Apache
> >> Commons
> >> Crypto)
> >> - move code to an Apache repo (probably git?!)
> >> - request a Jira project
> >> - setup maven build
> >> - setup project website
> >> - work on an initial release under Apache Commons coordinates
> >>
> >> Anything missing?
> >>
> >> Regards,
> >> Benedikt
> >>
> >> --
> >> http://home.apache.org/~britter/
> >> http://twitter.com/BenediktRitter
> >> http://github.com/britter
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

RE: [crypto][chimera] Next steps

[Chen, Haifeng]

Thanks Gary.

>> Would Commons Crypto focus only on AES? If so, Commons Crypto AES or Commons 
>> AES would be a better name.
Currently, this module supports only AES modes. To help folks with information 
for making decision, a little further clarification from me may help. 

The project doesn't implement directly the cryptographic algorithms. It 
provides:
1.  It provides a thin layer of Cipher to abstract the under-layer Cipher 
implementations. (currently support JCE Cipher or OpenSSL Cipher 
implementations). This is for optimization purposes, for example OpenSSL Cipher 
implementation provides 17+x performance for AES/CTR comparing with JDK 6 and 
5x comparing JDK 7/8.
2.  It provides a layer of stream and channel implementations abstracting Input 
source and Output target utilizing the Cipher layer. The layer can be used 
easily by applications that needs to encrypt/decrypt data streams or channels.
3.  Additionally, it provides a secure random utility classes to help generate 
TRUE random numbers for key generation. 

While there is no technical barrier for it to support other algorithms such as 
RC4 through JCE or OpenSSL. Just depends how widely this is required.

Thanks,
Haifeng

-Original Message-
From: Gary Gregory [mailto:garydgreg...@gmail.com] 
Sent: Monday, February 22, 2016 11:36 AM
To: Commons Developers List 
Subject: Re: [crypto][chimera] Next steps

Would Commons Crypto focus only on AES? If so, Commons Crypto AES or Commons 
AES would be a better name.

Gary

On Sun, Feb 21, 2016 at 6:28 PM, Chen, Haifeng 
wrote:

> Thanks Benedikt, Uma, Gary, Ole, and Emmanuel Bourg for your support! 
> It's great to have Chimera to be part of Apache Commons.
>
> >>[ Emmanuel Bourg] Define the scope of the project? Do we go after 
> >>Bouncy
> Castle and aim for an equivalent feature set?
> Agree to make a clear scope of the project. The original Chimera scope 
> is not go after a Bouncy Castle style of library. It targets the gap 
> between the application and the under cipher implementations. For 
> example, applications uses a lot of InputStream/OutputStream or 
> Channel concepts to read / write a stream of data. Application can 
> share these Crypto streams/channel implementations abstracting various input 
> and output types.
> Chimera also targets to very important performance optimizations on 
> AES which is used worldwide. I suggest this module to be still 
> lightweight and clear in involving, which is the same ideology of Apache 
> Commons.
>
> >> [Uma] Here I would like to introduce Haifeng, who lead the efforts 
> >> in
> Chimera github project.
> Thanks Uma for introduction.
>
> >> [Uma] Me and Haifeng had some discussion yesterday for the list to 
> >> get
> commit prevs. May be he could probably get list. Then I think Commons 
> PMC can make a decision on it.
> Chimera has 5 long standing contributors on github. We can also invite 
> those who contributed the HDFS encryption feature (HDFS-6134 and
> HADOOP-10150) to continue participate the involution of this project 
> if they want.
>
> Thanks,
> Haifeng
>
> -Original Message-
> From: Gangumalla, Uma [mailto:uma.ganguma...@intel.com]
> Sent: Sunday, February 21, 2016 3:07 AM
> To: Commons Developers List 
> Subject: Re: [crypto][chimera] Next steps
>
> Hi Benedikt,
>
>  Thank you for the Next steps discussion. I thought of pinging you on 
> this
> :-)
>
>  Here I would like to introduce Haifeng, who lead the efforts in 
> Chimera github project.
>
> I think Apache Commons Crypto looks good and self descriptive IMO.
>  I am +1
>
> Me and Haifeng had some discussion yesterday for the list to get 
> commit prevs. May be he could probably get list. Then I think Commons 
> PMC can make a decision on it.
>
>
> >move code to an Apache repo (probably git?!)
> +1 for git
>
> >- setup maven build
> If this point is just about maven build alone, then we should set up 
> Jenkins CI build boat as well right, may be we can add this point?
>
> Regards,
> Uma
>
> On 2/20/16, 8:29 AM, "Gary Gregory"  wrote:
>
> >Who are the committers comming along for this component?
> >
> >Do we have enough of them?
> >
> >I like Apache Commons Crypto.
> >
> >Gary
> >On Feb 20, 2016 3:15 AM, "Benedikt Ritter"  wrote:
> >
> >> Hi,
> >>
> >> I'd like to discuss the next steps for moving the Chimera component 
> >>to  Apache Commons. So far, none of the other PMC members has 
> >>expressed his or  her thoughts about this. If nobody brings up 
> >>objections about moving the  component to Apache Commons, I'm 
> >>assuming lazy consensus about this.
> >>
> >> So the next steps would be:
> >> - decide on a name for the new component (my proposal was Apache 
> >> Commons
> >> Crypto)
> >> - move code to an Apache repo (probably git?!)
> >> - request a Jira project
> >> - setup maven build
> >> - setup project website
> >> - work on an initial release under Apache Commons coordinates
> >>
> >> Anything missing?
> >>
> >> Regards,
> >> Benedikt
> >>
> >> --

Re: [crypto][chimera] Next steps

[Gary Gregory]

Curious: How to you get to OpenSSL, JNI? JNA?

Gary

On Sun, Feb 21, 2016 at 10:51 PM, Chen, Haifeng 
wrote:

> Thanks Gary.
>
> >> Would Commons Crypto focus only on AES? If so, Commons Crypto AES or
> Commons AES would be a better name.
> Currently, this module supports only AES modes. To help folks with
> information for making decision, a little further clarification from me may
> help.
>
> The project doesn't implement directly the cryptographic algorithms. It
> provides:
> 1.  It provides a thin layer of Cipher to abstract the under-layer Cipher
> implementations. (currently support JCE Cipher or OpenSSL Cipher
> implementations). This is for optimization purposes, for example OpenSSL
> Cipher implementation provides 17+x performance for AES/CTR comparing with
> JDK 6 and 5x comparing JDK 7/8.
> 2.  It provides a layer of stream and channel implementations abstracting
> Input source and Output target utilizing the Cipher layer. The layer can be
> used easily by applications that needs to encrypt/decrypt data streams or
> channels.
> 3.  Additionally, it provides a secure random utility classes to help
> generate TRUE random numbers for key generation.
>
> While there is no technical barrier for it to support other algorithms
> such as RC4 through JCE or OpenSSL. Just depends how widely this is
> required.
>
> Thanks,
> Haifeng
>
> -Original Message-
> From: Gary Gregory [mailto:garydgreg...@gmail.com]
> Sent: Monday, February 22, 2016 11:36 AM
> To: Commons Developers List 
> Subject: Re: [crypto][chimera] Next steps
>
> Would Commons Crypto focus only on AES? If so, Commons Crypto AES or
> Commons AES would be a better name.
>
> Gary
>
> On Sun, Feb 21, 2016 at 6:28 PM, Chen, Haifeng 
> wrote:
>
> > Thanks Benedikt, Uma, Gary, Ole, and Emmanuel Bourg for your support!
> > It's great to have Chimera to be part of Apache Commons.
> >
> > >>[ Emmanuel Bourg] Define the scope of the project? Do we go after
> > >>Bouncy
> > Castle and aim for an equivalent feature set?
> > Agree to make a clear scope of the project. The original Chimera scope
> > is not go after a Bouncy Castle style of library. It targets the gap
> > between the application and the under cipher implementations. For
> > example, applications uses a lot of InputStream/OutputStream or
> > Channel concepts to read / write a stream of data. Application can
> > share these Crypto streams/channel implementations abstracting various
> input and output types.
> > Chimera also targets to very important performance optimizations on
> > AES which is used worldwide. I suggest this module to be still
> > lightweight and clear in involving, which is the same ideology of Apache
> Commons.
> >
> > >> [Uma] Here I would like to introduce Haifeng, who lead the efforts
> > >> in
> > Chimera github project.
> > Thanks Uma for introduction.
> >
> > >> [Uma] Me and Haifeng had some discussion yesterday for the list to
> > >> get
> > commit prevs. May be he could probably get list. Then I think Commons
> > PMC can make a decision on it.
> > Chimera has 5 long standing contributors on github. We can also invite
> > those who contributed the HDFS encryption feature (HDFS-6134 and
> > HADOOP-10150) to continue participate the involution of this project
> > if they want.
> >
> > Thanks,
> > Haifeng
> >
> > -Original Message-
> > From: Gangumalla, Uma [mailto:uma.ganguma...@intel.com]
> > Sent: Sunday, February 21, 2016 3:07 AM
> > To: Commons Developers List 
> > Subject: Re: [crypto][chimera] Next steps
> >
> > Hi Benedikt,
> >
> >  Thank you for the Next steps discussion. I thought of pinging you on
> > this
> > :-)
> >
> >  Here I would like to introduce Haifeng, who lead the efforts in
> > Chimera github project.
> >
> > I think Apache Commons Crypto looks good and self descriptive IMO.
> >  I am +1
> >
> > Me and Haifeng had some discussion yesterday for the list to get
> > commit prevs. May be he could probably get list. Then I think Commons
> > PMC can make a decision on it.
> >
> >
> > >move code to an Apache repo (probably git?!)
> > +1 for git
> >
> > >- setup maven build
> > If this point is just about maven build alone, then we should set up
> > Jenkins CI build boat as well right, may be we can add this point?
> >
> > Regards,
> > Uma
> >
> > On 2/20/16, 8:29 AM, "Gary Gregory"  wrote:
> >
> > >Who are the committers comming along for this component?
> > >
> > >Do we have enough of them?
> > >
> > >I like Apache Commons Crypto.
> > >
> > >Gary
> > >On Feb 20, 2016 3:15 AM, "Benedikt Ritter"  wrote:
> > >
> > >> Hi,
> > >>
> > >> I'd like to discuss the next steps for moving the Chimera component
> > >>to  Apache Commons. So far, none of the other PMC members has
> > >>expressed his or  her thoughts about this. If nobody brings up
> > >>objections about moving the  component to Apache Commons, I'm
> > >>assuming lazy consensus about this.
> > >>
> > >> So the next steps would be:
> > >> - decide on a name for the new component (my propo

RE: [crypto][chimera] Next steps

[Chen, Haifeng]

Given the current scope and if we don't see significant value adding other 
algorithms, Commons Crypto AES or Commons AES does be a better descriptive name.

Thanks,
Haifeng

-Original Message-
From: Chen, Haifeng 
Sent: Monday, February 22, 2016 2:52 PM
To: Commons Developers List 
Subject: RE: [crypto][chimera] Next steps

Thanks Gary.

>> Would Commons Crypto focus only on AES? If so, Commons Crypto AES or Commons 
>> AES would be a better name.
Currently, this module supports only AES modes. To help folks with information 
for making decision, a little further clarification from me may help. 

The project doesn't implement directly the cryptographic algorithms. It 
provides:
1.  It provides a thin layer of Cipher to abstract the under-layer Cipher 
implementations. (currently support JCE Cipher or OpenSSL Cipher 
implementations). This is for optimization purposes, for example OpenSSL Cipher 
implementation provides 17+x performance for AES/CTR comparing with JDK 6 and 
5x comparing JDK 7/8.
2.  It provides a layer of stream and channel implementations abstracting Input 
source and Output target utilizing the Cipher layer. The layer can be used 
easily by applications that needs to encrypt/decrypt data streams or channels.
3.  Additionally, it provides a secure random utility classes to help generate 
TRUE random numbers for key generation. 

While there is no technical barrier for it to support other algorithms such as 
RC4 through JCE or OpenSSL. Just depends how widely this is required.

Thanks,
Haifeng

-Original Message-
From: Gary Gregory [mailto:garydgreg...@gmail.com]
Sent: Monday, February 22, 2016 11:36 AM
To: Commons Developers List 
Subject: Re: [crypto][chimera] Next steps

Would Commons Crypto focus only on AES? If so, Commons Crypto AES or Commons 
AES would be a better name.

Gary

On Sun, Feb 21, 2016 at 6:28 PM, Chen, Haifeng 
wrote:

> Thanks Benedikt, Uma, Gary, Ole, and Emmanuel Bourg for your support! 
> It's great to have Chimera to be part of Apache Commons.
>
> >>[ Emmanuel Bourg] Define the scope of the project? Do we go after 
> >>Bouncy
> Castle and aim for an equivalent feature set?
> Agree to make a clear scope of the project. The original Chimera scope 
> is not go after a Bouncy Castle style of library. It targets the gap 
> between the application and the under cipher implementations. For 
> example, applications uses a lot of InputStream/OutputStream or 
> Channel concepts to read / write a stream of data. Application can 
> share these Crypto streams/channel implementations abstracting various input 
> and output types.
> Chimera also targets to very important performance optimizations on 
> AES which is used worldwide. I suggest this module to be still 
> lightweight and clear in involving, which is the same ideology of Apache 
> Commons.
>
> >> [Uma] Here I would like to introduce Haifeng, who lead the efforts 
> >> in
> Chimera github project.
> Thanks Uma for introduction.
>
> >> [Uma] Me and Haifeng had some discussion yesterday for the list to 
> >> get
> commit prevs. May be he could probably get list. Then I think Commons 
> PMC can make a decision on it.
> Chimera has 5 long standing contributors on github. We can also invite 
> those who contributed the HDFS encryption feature (HDFS-6134 and
> HADOOP-10150) to continue participate the involution of this project 
> if they want.
>
> Thanks,
> Haifeng
>
> -Original Message-
> From: Gangumalla, Uma [mailto:uma.ganguma...@intel.com]
> Sent: Sunday, February 21, 2016 3:07 AM
> To: Commons Developers List 
> Subject: Re: [crypto][chimera] Next steps
>
> Hi Benedikt,
>
>  Thank you for the Next steps discussion. I thought of pinging you on 
> this
> :-)
>
>  Here I would like to introduce Haifeng, who lead the efforts in 
> Chimera github project.
>
> I think Apache Commons Crypto looks good and self descriptive IMO.
>  I am +1
>
> Me and Haifeng had some discussion yesterday for the list to get 
> commit prevs. May be he could probably get list. Then I think Commons 
> PMC can make a decision on it.
>
>
> >move code to an Apache repo (probably git?!)
> +1 for git
>
> >- setup maven build
> If this point is just about maven build alone, then we should set up 
> Jenkins CI build boat as well right, may be we can add this point?
>
> Regards,
> Uma
>
> On 2/20/16, 8:29 AM, "Gary Gregory"  wrote:
>
> >Who are the committers comming along for this component?
> >
> >Do we have enough of them?
> >
> >I like Apache Commons Crypto.
> >
> >Gary
> >On Feb 20, 2016 3:15 AM, "Benedikt Ritter"  wrote:
> >
> >> Hi,
> >>
> >> I'd like to discuss the next steps for moving the Chimera component 
> >>to  Apache Commons. So far, none of the other PMC members has 
> >>expressed his or  her thoughts about this. If nobody brings up 
> >>objections about moving the  component to Apache Commons, I'm 
> >>assuming lazy consensus about this.
> >>
> >> So the next steps would be:
> >> - decide on a name for the new com

Re: [crypto][chimera] Next steps

[Benedikt Ritter]

Hi again,

2016-02-20 12:15 GMT+01:00 Benedikt Ritter :

> Hi,
>
> I'd like to discuss the next steps for moving the Chimera component to
> Apache Commons. So far, none of the other PMC members has expressed his or
> her thoughts about this. If nobody brings up objections about moving the
> component to Apache Commons, I'm assuming lazy consensus about this.
>
> So the next steps would be:
> - decide on a name for the new component (my proposal was Apache Commons
> Crypto)
> - move code to an Apache repo (probably git?!)
> - request a Jira project
> - setup maven build
> - setup project website
> - work on an initial release under Apache Commons coordinates
>
> Anything missing?
>

Given the recent discussion, I'd like to update to above list:

- Define the scope of the new Component (in our wiki? in the repo on
github?)
- Define the group of initial committers
- Decide on a name
- Think about IP clearance - The code seems to belong to Intel. What do we
have to do to move the code the the ASF? Go through the Incubator?
- Move code to Apache Commons
- request Jira project
- setup maven build
- setup project website
- work on an initial release

Thoughts?
Benedikt


>
> Regards,
> Benedikt
>
> --
> http://home.apache.org/~britter/
> http://twitter.com/BenediktRitter
> http://github.com/britter
>



-- 
http://home.apache.org/~britter/
http://twitter.com/BenediktRitter
http://github.com/britter