View allAll Photos Tagged github

github.com/aaronpk/Wordpress-IRC-Notification

 

Receive notifications to an IRC channel when posts are published or comments are posted. Configuration page allows for customizing the text sent to the IRC channel. Use this with the MediaWiki RecentChanges IRC Bot.

sometimes coding late into the night is counter-productive. This is a snapshot of our git repository (a system for allowing multiple programmers to work on some code without overwriting each other's work). An orderly 'checkout - change - check-in' looks like the area on the left. We were looking good until sometime around 2am when we tied a knot in our code that took a half hour to get undone again

 

wuipdesign.github.io

 

Free photos. Set 16.

Use it freely in personal and commercial projects.

 

CC-License

 

Photos: Anthony Clochard / wuipdesign.github.io

Camera Tools - Otis_inf GitHub

ReShade

It takes a digital village: An empirical and analytical look at what grows strong communities across GitHub.com

Ben Balter (GitHub)

Screen-shot form Rails project. Look at it yourself, it’s dynamic: dmitry.baranovskiy.com/work/github/

7 June 2017 - OECD Forum 2017: BLI: Coding the Law with Alain Hélaïli, Solutions Engineer, Github www.oecd.org/bli

 

Photo: OECD/ Salome Suarez

wuipdesign.github.io

 

Free photos. Set 10.

Use it freely in personal and commercial projects.

 

CC-License

 

Photos: Anthony Clochard / wuipdesign.github.io

previous movies are here youtube.com/danpaluska, no webcam on those. starting webcam add today.

 

github.com/danpaluska/OneMinutePerDay/blob/master/capture.sh

 

#! /bin/sh

 

# THIS VERSION TAKES A WEBCAM PIC AND BLENDS IT WITH SCREENSHOT

# ***************************************

# ******OMPD - One Minute Per Day - Voluntary Anthropology

# ******public timelapse wall

# need to install ffmpeg and imagemagick for this to work

# maybe wacaw too

# **************

# **************

 

# whatever you want to be your directory of files

cd ~/Pictures/OMPD

# make a subdirectory with today's date, then go to it.

mkdir `date +%Y-%m`

cd `date +%Y-%m`

 

screencapture -m -x -t jpg last.jpg

 

DDDATE=`date +%Y%m`

DATETIME=`date +%Y%m%d%H%M%S`

 

RAMP=9

counter=10000

# at 15 seconds per shot, 4/min, 240/hr, 10 hours = 2400 shots

# while [ $counter -ne 3400 ] # run a fixed number of shots.

#while [ `date +%H` -lt 23 ] # if it's less that 11pm

while [ 1 ] # run all the time

do

DATETIME=`date +%Y%m%d%H%M%S`

 

NOWDATE=`date +%Y%m`

if [ $NOWDATE -gt $DDDATE ]

then

echo "month change"

counter=100000

for f in screen*.jpg; do

let "counter+=1"

mv $f renum${counter:1}.jpg

done

# convert *.jpg ~/Movies/AUTOUPLOAD/OMPD-$DDDATE-$DATETIME.mp4

# for f in *.jpg; do let "counter+=1"; mv $f screen${counter:1}.jpg ; done

#done

# -g sets keyframes. useful if you ever edit the file later

ffmpeg -r 20 -b 5000 -g 1 -i renum%05d.jpg -sameq -s 720x450 ~/Movies/AUTOUPLOAD/OMPD-$DDDATE.mp4

#ffmpeg -r 10 -sameq -i webcam%04d.jpg ~/Movies/AUTOUPLOAD/camTL-$DDDATE.mp4

#ffmpeg -r 15 -b 5000 -i webcam%04d.jpg ~/Movies/AUTOUPLOAD/`

# -b 5000 to limit movie size.

cd ~/Pictures/OMPD

mkdir `date +%Y-%m-%d`

cd `date +%Y-%m-%d`

sleep 1

screencapture -m -x -t jpg last.jpg

screencapture -m -x -t jpg new.jpg

screencapture -m -x -t jpg middle.jpg

counter=10000

DDDATE=`date +%Y%m`

fi

 

#let "counter+=1"

echo $DATETIME

#echo $counter # if you want to see the progression on the terminal window

# capture a JPG screenshot

 

let "RAMP%=6"

let "RAMP+=1"

echo $RAMP

#screencapture -m -x -t jpg screen${counter:1}.jpg

screencapture -m -x -t jpg new.jpg

#composite /Users/danielpaluska/Pictures/OMPD/wave_gradient6.png new.jpg -displace 3x3 middle.jpg #screen$DATETIME.jpg

composite -blend 35 new.jpg last.jpg -matte middle.jpg

 

wacaw --jpeg -n 4 webcam

 

composite -blend 50 webcam.jpeg middle.jpg last.jpg

#composite -blend 50 -gravity center /Users/danielpaluska/OneMinutePerDay/label.gif middle.jpg middle.jpg

#cp middle.jpg last.jpg

#mv temp.jpg screen$DATETIME.jpg

convert last.jpg -resize %50 screen$DATETIME.jpg

 

#wacaw --jpeg -n 4 webcam${counter:1}.jpg

echo "captured images"

# resize images using imagemagick here?

 

#mogrify screen$DATETIME.jpg -resize 720x450

 

# add additional imagemagick filters that intentionally art-ify the images?

echo "made screen smaller"

# convert webcam${counter:1}.jpg.jpeg -resize 95% webcam${counter:1}.jpg

# mv webcam$DATETIME.jpg.jpeg webcam$DATETIME.jpg

   

#convert screen${counter:1}.jpg -resize 50% screen${counter:1}.jpg

 

# capture an image from the webcam using wacaw package. get from sourceforge

#

# download zip file. unzip. run these two things at command line

# sudo cp wacaw /usr/local/bin; sudo chmod +x /usr/local/bin/wacaw

echo yofool

# number of seconds between shots

sleep 20

# make a beep here? display a shot onscreen?

done

# one shot/15sec, played at 10 fps = 150x speedup. 150min(2.5hr) = 1 min vid. 10hrs = 4min

# about mac cron jobs on laptops and sleep times

# www.thexlab.com/faqs/maintscri...

A little parallax scrolling on the 404 image. It's pretty clever.

wuipdesign.github.io

 

Free photos. Set 12.

Use it freely in personal and commercial projects.

 

CC-License

 

Photos: Anthony Clochard / wuipdesign.github.io

wuipdesign.github.io

 

Free photos. Set 14.

Use it freely in personal and commercial projects.

 

CC-License

 

Photos: Anthony Clochard / wuipdesign.github.io

wuipdesign.github.io

 

Free photos. Set 17.

Use it freely in personal and commercial projects.

 

CC-License

 

Photos: Anthony Clochard / wuipdesign.github.io

It used to be that forking the code was interpreted as a failure in leadership. Forking would split the code, community, and users into competing factions and generally make life more confusing for everyone (see XEmacs).

 

In the world of distributed revision control systems like Git, forking means something different. These systems were designed to support a web of related revisions. Forking is just the way you roll. A multiplicity of forks is a sign of a healthy developer community. In fact, GitHub advertises the "5 Most Forked Projects" on their home page.

What is this?

This is a stacked graph displaying Tweets associated with the #eComm and #arconf hashtags during the three days of San Francisco's Emerging Communications Conference and the Augmented Reality Conference in April 2010. The data is taken from 4/19/10-4/21/10.

 

What is a stacked Graph?

The stacked graph method is one way of displaying buzz around speakers and topics at conferences.

 

The conversation bursts work just like sine waves as an audience begins to engage with the material of each new speaker. As memorable quotes are released into the audience, a lot of tweeting and retweeting coverage occurs, melding some of the terms into like-groups. The graph shows that people tweeted about the speaker during the middle of the speech as opposed to at the beginning or end of the speech.

 

The interesting part about visualizing data in this way is that it shows that there is an inherent difference between what a speaker says and the audience “hears”. Hearing, in this case, is defined by how the speaker’s name, company, and words are picked up by microbloggers and re-tweeted online.

 

In a way, the stacked graph is a more organic version of a bar graph, because it can be used to show an increase and decrease in volumes of conversation around a subject.

 

This project was originally inspired by the Neoformix Twitter Stream graph. It was a clunky, limited machine programmed in Java. After several requests for the source code, we were forced to make our own. The result is a much better, lighter, and faster loading system that has a linear time scale.

 

After looking at the full graph of the conference over three days, @anthropunk commented that while the streamgraph for #arconf was significantly larger than those for the other days, it did not necessarily mean that the first two days of the conference were not interesting, but that there were simply more people tweeting during the last day of the conference.

 

---

 

Stacked Graph History

Here's a link to Lee Byron's original Stacked Graph paper, “Stacked Graphs – Geometry & Aesthetics” www.leebyron.com/else/streamgraph/

 

“streamgraph_generator” can be checked out from github.

 

---

 

Credits:

This image was created by @natronics and @aaronpk. Aaron took data from the Twitter API and passed it through Nathan's Python Twitter stacked graph library. This image excludes the actual "#ecomm" and &quote;#arconf" terms leaving more room for the other terms to show through.

 

You can make these as well by downloading @natronic's Python Stream Graph Library on GitHub.

I hooked GitHub's stoplight up to their build system via Arduino, some relays, and an ethernet shield. Read about the process here:

 

www.urbanhonking.com/ideasfordozens/2010/05/the_github_st...

'Daid' (github.com/daid) explaining the finer points of Skeinforge vs Cura (?)...

 

The KamerMaker (RoomBuilder), capable of 3D printing large architectural objects with an epic 2x2x3.5m build area!

 

Launch party for kamermaker.com, a project by DUS Architects (dusarchitects.com), at Tolhuistuin, Amsterdam.

 

www.faberdashery.co.uk

“Harry Melling had an entirely different character to his son Tom. If he got too much to drink at the Mason’s Arms he used to sleep under the hedges. The more religious Tom became the more likely his father was to turn the air blue with expletives in his son’s company.”

[Joe Taylor, in Part 2, “Billinge History (the book)”, 3rd ed, 2003]

 

The date-stone “H/F/S 1779” commemorates the year of construction and the identities of the builders – Henry and Sarah Fairhurst- of two stone cottages which, together with the adjoining building of later date on the south side (right of photograph), now comprise “The Masons Arms”. The Fairhursts had leased the land from John Rothwell, innkeeper, of Windle – and the building is in fact identified as “Rothwells” on the 1st edition 6" OS map of 1850. Its later renaming is said to reflect the main occupation (per the 1861 and 1871 census returns) of the Fairhursts' grandson, Robert Rigby. Robert's widow Mary is described as, successively, “Beer Retailer”, “Publican” and “Beerhouse-Keeper” of Billinge Chapel End on the 1891, 1901 and 1911 census returns. According to the Licensing Registers of the Wigan Division Petty Sessional Court at Wigan Archives ref. PS/Wi/1, Mary was shortly thereafter replaced as licensee of The Masons Arms by T[homas?] Berry and then (from 1917) by his widow, Margaret.

 

The photograph was taken on 29 May 2020.

I've been hanging out for a Ninefold sticker since I joined the company. And now we have them.

 

Come get some!

 

See my previous update for what all the others are and where I got them.

I hooked GitHub's stoplight up to their build system via Arduino, some relays, and an ethernet shield. Read about the process here:

 

www.urbanhonking.com/ideasfordozens/2010/05/the_github_st...

1 2 ••• 33 34 36 38 39 ••• 79 80