Public Notes by chase_ats Tagged #%40to_do

Notes publicly shared by our members.
"Using this gem, whenever a Capybara test in Cucumber, Rspec or Minitest fails, the HTML for the failed page and a screenshot (when using capybara-webkit, Selenium or poltergeist) is saved into $APPLICATION_ROOT/tmp/capybara. This is a huge help when trying to diagnose a problem in your failing steps as you can view the source code and potentially how the page looked at the time of the failure." _Can also have it run manually on demand_ ##dynamic_screen_scraping #screenshots #project #capybara #phantomjs #ruby #javascript #testing #@to_do #pub
"SPECIAL OFFER! .COM just C$0.99*!" _What does C$ mean?_ _Should buy them on two or three accounts_ #Godaddy #domains #coupons #@to_do #pub
"Read this book and change your life. There's finally a solution for information overload. Bit Literacy, the new book by Mark Hurst, describes how to manage e-mail, todos, photos, a media diet, and other sources of stress for people today. Bit Literacy is written for normal, non-techie users, and it doesn't require any special software or computer skills. Read the book and you'll start working more productively, so as to live a fuller life outside of work." #change-your-life #books #@to_do #pub
maebert.github.io
"jrnl jrnl is a simple journal application for your command line. Journals are stored as human readable plain text files - you can put them into a Dropbox folder for instant syncing and you can be assured that your journal will still be readable in 2050, when all your fancy iPad journal applications will long be forgotten. jrnl also plays nice with the fabulous DayOne and can read and write directly from and to DayOne Journals." #Day_One #journaling #cli #open_source #plain_text #Writing #mindfulness #introspection #ideas #code #@to_do #python #pub
Just a reminder bookmark that searching diffbot yields potentially interesting information #research #web_crawling #text_extraction #text_analysis #text_parsing #@to_do #pub
"All email for your app in one place - Send segmented newsletters without bugging developers - Change transactional emails without re-deploying your app - Create lifecycle emails to activate more customers" #SaaS #freemium #email #ideas #aggregator #@to_do #pub
This might be what Ryan Biggs uses for the logs subdomain on his site #@to_do #open_source #parsing #logs #irc #pub
"USER COMMUNICATION WITH ONE TOOL INSTEAD OF FOUR A smarter way to do lifecycle marketing, customer development, newsletters, support" #@to_do #SaaS #freemium #trial #monthly #one_price #$AFMA_umbrella #$project_2018_ecommerce #live_chats #customer_retainment #customer_support #customer_acquisition #pub
"Here’s what we need when you contact us for an OSS account for Lighthouse or Tender: A link to your code source that contains your OSS license from an OSI-approved license list. NOTE: We’re often asked if a Creative Commons license works and unfortunately, no and we defer to the reasons that Creative Commons themselves give for using OSI licenses. Done. Here’s what you’ll get: Lighthouse - You’ll get the equivalent to a Bronze-level plan that includes: 10 projects 15 members 2GB of file space Priority state for projects" _Also the $9/month Tender plan with the custom css and single sign-on features of higher plans_ #@to_do #open_source #free #deals #pub
"This something I’ve been using for quite a while without bad consequences and suggested by Linus Torvalds on the git mailing list. araqnid’s solution is the proper one for bringing code into your repository… but when you, like me, have multiple equivalent authoritative upstreams (I keep some of my more critical projects cloned to both a private upstream, GitHub, and Codaset), it can be a pain to push changes to each one, every day. Long story short, git remote add all of your remotes individually… and then git config -e and add a merged‐remote. Assuming you have this repository config: [remote "GitHub"] url = [email protected]:elliottcable/Paws.o.git fetch = +refs/heads/*:refs/remotes/GitHub/* [branch "Master"] remote = GitHub merge = refs/heads/Master [remote "Codaset"] url = [email protected]:elliottcable/paws-o.git fetch = +refs/heads/*:refs/remotes/Codaset/* [remote "Paws"] url = [email protected]:Paws/Paws.o.git fetch = +refs/heads/*:refs/remotes/Paws/* … to create a merged‐remote for "Paws" and "Codaset", I can add the following after all of those: [remote "Origin"] url = [email protected]:Paws/Paws.o.git url = [email protected]:elliottcable/paws-o.git Once I’ve done this, when I git push Origin Master, it will push to both Paws/Master and Codaset/Master sequentially, making life a little easier." #@to_do #simple #git #hacks #good_to_know #version_control #pub
"My Tiny Habits™ program can create new behaviors in your life. Let me explain . . . I’ve studied human behavior for 18 years, mostly at Stanford University. Here’s what I’ve learned: Only three things will change behavior in the long term. Option A. Have an epiphany Option B. Change your environment (what surrounds you) Option C. Take baby steps Creating an epiphany is difficult. You should rule out Option A unless you have mystical powers (I don’t). But here’s the good news: The other two options are practical. And they can lead to lasting change if you follow the right program. However, few winning programs exist. In December of 2011, I created a new way to tap the power of environment and baby steps. Over 14,700 people have since joined in. The results are the best I’ve ever seen in any program. My method is surprisingly simple, but the impact is big. See what people say. I invite you to join a future session of Tiny Habits. Go here --> http://tinyhabits.com/join --BJ" "BJ Fogg, PhD Director, Persuasive Tech Lab Stanford University" #habits #@to_do #@to_use #small_steps #psychology #behavior #inspirational #pub
"An API into your person could be quick and useful. Nothing sensitive need be contained, just something that could list out your social accounts (all of them), tell me where you're currently located, where you've been, etc. It would be cool to expose some dynamic data like calculated age, latest blog/social media post, or other non-private data. So, I made one. You can access my personal API at /api. It's got everything listed above, plus a little extra about my usual languages and frameworks. It supports JSONP with an optional callback parameter (/api?calback=foo). No keys required, possible uses for an API like this (especially if others implement something similar) include: dynamically calculated ages for operators of a 'personal API' statistics on languages and frameworks graphing operating locations dynamically display latest blog posts operating a repository of users' associated social accounts ?" #geeky #@to_do #APIs #quantified_self #personal_APIs #@to_check_out #interesting #suggestions #lists #pub
"Personable Personable is a personal API service that everybody can use. Inspired by Joshua Beckman's Personal API(http://www.bckmn.com/blog/how-to-access-my-personal-api), I wanted to put something together that everybody could have, quickly and easily, and without too much headache. Personable is written in Python/Django, Angular and Bootstrap." #python #geeky #javascript #@to_do #APIs #quantified_self #personal_APIs #@to_check_out #Django #interesting #open_source #suggestions #pub
core.telegram.org
Again, references to Telegram APIs. #APIs #personal #life #friends #luugs #chatting #@to_do #pub