ThoughtStreams is a publishing platform that lets you quickly capture and share thoughts, ideas, experiments and observations.
It's perfect for public notes that are more than a tweet and less than a blog post.
There's no restriction on the length of each post and Markdown is fully supported (as is media upload on paid plans) but at the same time, ThoughtStreams encourages you to post thoughts as you have them without feeling the pressure to fully polish your ideas before sharing them like you would in a blog post.
Thoughts can be reposted between streams (including reposting other people's thoughts into your own streams) and combined streams can aggregate different people's thoughts on a topic.
The site is FREE for up to three streams. Monthly plans available if you need more.
After a day or so, look at your previous day's tweets. Take the replies you made and look to see if there are any faves, retweets or replies to those tweets. If not, store in a database the name of the person who you replied to with the the tweet in question. At the end of the month, tally up the usernames you replied to and rank them. Send an email with a report of the replies that went ignored.
The people with the most ignored tweets are ignoring you, so maybe you can spend the energy more usefully. Also, use the data to evaluate which replies got ignored. Maybe those aren't funny, insightful, etc.
Github recently announced they're moving to Timezone-aware contribution graphs.
It sounds like they're doing it right by recording the timezone of the contribution rather than normalizing it and localizing it on display.
The short answer is "war and golf" but here is a longer version, gleaned from various articles online and a little prior knowledge on the topic.
While Benjamin Franklin is sometimes credited with the idea of setting clocks differently in the summer, his idea was well before its time as there wasn't a notion of standard time in his day. The notion that clocks would be set according to the "real time" (i.e. based on the Sun) of some other location has its origin with the railroad system. In November 1840, the Great Western Railway in England adopted London Time for all their schedules. The US and Canada followed suit with their own Standard Time in November 1883.
While Standard Time was initially for the railroads, it began to be adopted across the board, eventually being enacted into law in the US by the Standard Time Act of 1918.
An Englishman, William Willet made the observation, a century after Ben Franklin had done the same, that people were wasting the early hours of the day in summer by sleeping in. He was also an avid golfer who was frustrated at dusk cutting short his game. So he started campaigning for clocks to be advanced during the summer months. The idea was ridiculed and he died in 1915 without seeing his idea adopted.
In April 1916, however, Germany started advancing the clock an hour to reduce electricity usage and hence fuel consumption during the war. Many European countries immediately followed suit and Britain started in May 1916. When the US joined the war, they too adopted this daylight saving measure.
US Congress repealed the law in 1919, but Woodrow Wilson (incidentally also an avid golfer) vetoed the repeal. Congress overrode the veto and so daylight saving stopped, although was adopted locally in some places.
In World War II, it was reintroduced, this time all year around. The US had daylight saving from February 1942 to September 1945. After the war, it went back to being a local issue.
It was a controversial issue through the early 1960s but the confusion caused by so many local differences resulted in the US passing the Universal Time Act in 1966 which reintroduced it across the country unless overridden by state law.
I started Shadowrun: Dragonfall after dinner last night.
What a mistake! The game is hugely compelling and the storyline is broken down into neat little chunks in the context of larger story arcs. Hours literally flew by in a mixture of mystery uncovering, tactical combat, RPG character unlocks, upgrades and tweaks.
The worse thing is that I was often tearing through the background conversations rather than taking the time to enjoy them.
It also seems a much tougher, replayable campaign in that a lot of options require high skill levels to unlock so its hard to be a generalist with lots of flexibility now.
And biotech now seems to be important for clues and conversations making it much more valuable that a simple healthkit boost.
In scala and some other functional languages you can create a lambda using placeholder syntax, like
(_ + _) means something like
(_1,_2) -> _1 + _2
This seems handy for very small functions like this one, where you are basically creating a function from a simple expression.
I do wonder whether we're buying much here, given you're basically saving one character from
x -> x + 1 vs
-> $ + 1. And the version with a named parameter could have a meaningful named parameter, too. BUT if we're relying on these quick lambdas to support currying and bound methods, it might be worth it. Or if the syntax can be shortened even more.
It seems like these would almost always need to be wrapped in parentheses so perhaps a variation on parentheses would be good like ‘%(.bla())‘ means ‘x,y->x.bla(y)‘