Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Slaking. An app for lazy guys. An app for me. You give it a message, and it will share it everywhere.
Ruby
branch: master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
bin
lib
README
TODO
slacking.gemspec

README

Slacking. An app for lazy guys. An app for me. You give it a message, and it will share it everywhere.
Copy bin/config where you want, and copy its path in the 19th row of bin/slacking.
Then, build the gem, install it and edit the config file following these 
tips.

twitter tokens => http://dev.twitter.com/apps
	Create a new application (fill Name, Description, Website how you want, leave Callback URL blank);
	Accept the terms, compile captcha and create the application;
	In your application page, go to Settings tab and check Read and Write checkbox and update the new settings;
	In Details tab create new token clicking the button;
	Copy the relative tokens.
	
facebook tokens
	When Slacking gives you the link to Facebook, open it in a web browser;
	The URL of the page will be similar to "https://www.facebook.com/connect/login_success.html#access_token=LONGCODE";
	Paste LONGCODE in Slacking to send a post to Facebook;
	In order to not paste LONGCODE in each Slacking session, copy it in config file `facebook=>APP_CODE:LONGCODE`;
	If you have problems with the Facebook post sending in Slacking, LONGCODE can be expired: Repeat the procedure;
	As APP_ID you can use whatever Facebook app with r/w permission you want, but I suggest you 179745182062082.

nerdz=>username:password
twitter=>consumer_key:consumer_secret:oauth_token:oauth_token_secret
facebook=>app_code:access_token
debug=>yes
options=>--no-nerdz:--no-twitter

other ways
	debug=>not
	options=>
	options=>--no-nerdz
config options will be overriden by eventually command line options (as the follow)

USAGE: slacking "Hi :D #slacking"
	[OPTIONS] --no-nerdz --no-facebook --no-twitter
Something went wrong with that request. Please try again.