<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jm)</title>
    <link>https://pinboard.in/u:jm/public/</link>
    <description>recent bookmarks from jm</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://nostalebots.xyz/"/>
	<rdf:li rdf:resource="https://link.springer.com/chapter/10.1007/978-3-030-91017-4_8"/>
	<rdf:li rdf:resource="https://www.theatlantic.com/magazine/archive/2022/05/social-media-democracy-trust-babel/629369/"/>
	<rdf:li rdf:resource="https://www.eff.org/deeplinks/2022/03/telegram-harm-reduction-users-russia-and-ukraine"/>
	<rdf:li rdf:resource="https://blogs.bmj.com/bmj/2021/09/13/covid-19-and-the-new-merchants-of-doubt/"/>
	<rdf:li rdf:resource="https://idlewords.com/talks/hk_stanford.html"/>
	<rdf:li rdf:resource="https://chelseatroy.com/2018/03/29/why-do-remote-meetings-suck-so-much/"/>
	<rdf:li rdf:resource="https://launchdarkly.com/blog/the-time-our-provider-screwed-us/"/>
	<rdf:li rdf:resource="https://theoutline.com/post/2437/who-banned-roger-stone"/>
	<rdf:li rdf:resource="https://en.wikipedia.org/wiki/Allen_curve"/>
	<rdf:li rdf:resource="https://www.reddit.com/r/Competitiveoverwatch/comments/4u9w4v/a_guide_to_communication_shotcalling_and/"/>
	<rdf:li rdf:resource="http://ipads4autism-ie.blogspot.ie/"/>
	<rdf:li rdf:resource="https://whispersystems.org/blog/the-ecosystem-is-moving/"/>
	<rdf:li rdf:resource="http://instagram-engineering.tumblr.com/post/117889701472/emojineering-part-1-machine-learning-for-emoji"/>
	<rdf:li rdf:resource="http://silverwraith.com/blog/2014/12/the-case-for-distributed-teams/"/>
	<rdf:li rdf:resource="https://stripe.com/blog/scaling-email-transparency"/>
	<rdf:li rdf:resource="http://zachholman.com/talk/move-fast-break-nothing/"/>
	<rdf:li rdf:resource="http://wingedpig.com/2014/09/23/introducing-groups-io/"/>
	<rdf:li rdf:resource="http://www.schneier.com/blog/archives/2013/09/the_nsa_is_brea.html"/>
	<rdf:li rdf:resource="http://ceasefiremagazine.co.uk/indymedia-its-time-move/"/>
	<rdf:li rdf:resource="http://shackspace.de/wiki/doku.php?id=project:hgg:faq"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://nostalebots.xyz/">
    <title>No More Stale Bots</title>
    <dc:date>2023-09-25T08:47:47+00:00</dc:date>
    <link>https://nostalebots.xyz/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[A heartfelt plea to stop autoclosing issues/bug reports based on "staleness":

"On github, there has been an increasing trend of using "Staleness detector bots" that will auto-close issues that have had no activity for X amount of time.  In concept, this may sound fine, but the effects this has, and how it poisons the core principles of Open Source, have been damaging and eroding projects for a long time, often unknowingly."

100% agree...]]></description>
<dc:subject>bots communication community issues github bug-reports cadt software open-source</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:2c17863cb4de/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bots"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:community"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:issues"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bug-reports"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cadt"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:open-source"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://link.springer.com/chapter/10.1007/978-3-030-91017-4_8">
    <title>Pandemic Communication Without Argumentative Strategy in the Digital Age: A Cautionary Tale and a Call to Arms</title>
    <dc:date>2022-07-11T17:14:20+00:00</dc:date>
    <link>https://link.springer.com/chapter/10.1007/978-3-030-91017-4_8</link>
    <dc:creator>jm</dc:creator><description><![CDATA["argumentation theory" is an interesting idea in the age of weaponised memes:

<blockquote>The Covid-19 pandemic has offered some notable examples of how public communication may backfire, in spite of the best intentions of the actors involved, and what role poor argumentative design plays in such failures, in the context of the current digital media ecology. In this chapter, I offer some preliminary considerations on the ongoing struggle to make sense of the new communication technologies in our media reality, analyze a concrete example of argumentative failure in anti-Covid vaccine communication in the European Union, and leverage this case study to issue a call to arms to argumentation scholars: argumentative competence is sorely needed for an effective response to the pandemic, yet argumentation theory will need to join forces with other areas of expertise to realize its societal impact. When it comes to arguments, self-isolation is not a viable strategy to fight Covid-19.</blockquote>

]]></description>
<dc:subject>memes social-media medicine public-health argumentation communication covid-19 society</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:acf09c3ff457/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:memes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:social-media"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:medicine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:public-health"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:argumentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:covid-19"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:society"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.theatlantic.com/magazine/archive/2022/05/social-media-democracy-trust-babel/629369/">
    <title>Why the Past 10 Years of American Life Have Been Uniquely Stupid - The Atlantic</title>
    <dc:date>2022-04-19T10:19:14+00:00</dc:date>
    <link>https://www.theatlantic.com/magazine/archive/2022/05/social-media-democracy-trust-babel/629369/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>What changed in the 2010s? [..] A mean tweet doesn’t kill anyone; it is an attempt to shame or punish someone publicly while broadcasting one’s own virtue, brilliance, or tribal loyalties. It’s more a dart than a bullet, causing pain but no fatalities. Even so, from 2009 to 2012, Facebook and Twitter passed out roughly 1 billion dart guns globally. We’ve been shooting one another ever since.</blockquote>

]]></description>
<dc:subject>communication culture democracy politics social-media facebook twitter trolls</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:06a2ad42f8ab/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:democracy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:social-media"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:facebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trolls"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.eff.org/deeplinks/2022/03/telegram-harm-reduction-users-russia-and-ukraine">
    <title>Telegram Harm Reduction for Users in Russia and Ukraine</title>
    <dc:date>2022-03-07T12:37:55+00:00</dc:date>
    <link>https://www.eff.org/deeplinks/2022/03/telegram-harm-reduction-users-russia-and-ukraine</link>
    <dc:creator>jm</dc:creator><description><![CDATA[The EFF's position on "should you use Telegram in Ukraine".]]></description>
<dc:subject>apps communication eff encryption ukraine russia war security</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:51ce53aa1ace/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:apps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:eff"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:encryption"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ukraine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:russia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:war"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blogs.bmj.com/bmj/2021/09/13/covid-19-and-the-new-merchants-of-doubt/">
    <title>Covid-19 and the new merchants of doubt</title>
    <dc:date>2021-09-14T08:39:05+00:00</dc:date>
    <link>https://blogs.bmj.com/bmj/2021/09/13/covid-19-and-the-new-merchants-of-doubt/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>How best can scientists push back against [science denialists]? There is a range of evidence-based strategies. These include:

“Public inoculation”–warning people about the risk of being misled and drawing attention to who is pushing the contentious information and their financial competing interests;
Highlighting scientific consensus; and
Mapping the institutional networks who are pushing controversial information and then using political and legal strategies to counter them.

For physicians, scientists, and public health officials to be effective countering efforts like the [Great Barrington declaration], it will be absolutely critical for them to realize that they are not dealing with an orthodox scientific debate based on sound data and evidence, but a well-funded sophisticated science denialist campaign based on ideological and corporate interests.</blockquote>

]]></description>
<dc:subject>denialism climate-change covid-19 science communication astroturf fakes evidence fake-news</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:7f0213363f87/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:denialism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:climate-change"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:covid-19"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:science"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:astroturf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fakes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:evidence"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:fake-news"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://idlewords.com/talks/hk_stanford.html">
    <title>Observations on Technology Use in Hong Kong Protests</title>
    <dc:date>2019-09-19T16:12:46+00:00</dc:date>
    <link>https://idlewords.com/talks/hk_stanford.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Very interesting. Good to see Telegram in the app list:

'Telegram is the preferred messenger app among protesters. It’s used for one-on-one messaging between people, among small groups of people to coordinate, and among very large groups to amplify and disseminate information. The polls feature in Telegram is also a way of affirming consensus in group decision making. Several features of Telegram make it attractive to protesters:

Disappearing messages. If the police force you to unlock your phone, you don’t give up your friends.

Groups with very large membership (tens of thousands, or even a hundred thousand members). This allows for quick, rapid amplification of news.

Built-in polls. Since the protest is decentralized, some mechanism is needed for decisionmaking. 
Polls in practice are used to ratify decisions where a consensus has become clear.
Ease of use.']]></description>
<dc:subject>china communication hong-kong protests protesting privacy telegram future messaging</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:d171a80f0dd1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:china"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hong-kong"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:protests"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:protesting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:telegram"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:future"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:messaging"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://chelseatroy.com/2018/03/29/why-do-remote-meetings-suck-so-much/">
    <title>Why do remote meetings suck so much?</title>
    <dc:date>2019-03-06T21:46:42+00:00</dc:date>
    <link>https://chelseatroy.com/2018/03/29/why-do-remote-meetings-suck-so-much/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Unstructured, "caucus"-style meetings suck particularly badly for remote workers.

<blockquote>When audio/visual delays exacerbate the caucus problem for people who always get the floor in meetings, it looks to them like a new problem. It’s not new; it’s just normally experienced by people in meetings with lower caucus scores. Leadership doesn’t notice because people in leadership positions tend to have higher caucus scores, and being in a position of leadership also tends to boost your caucus score (basically because people interrupt you less). But that’s a weakness of the way we identify decision-makers: good ideas come from everywhere, and especially from people who do a lot of thinking and observing before they say anything.

Making meetings more accessible to remote employees doesn’t just make meetings more accessible to remote employees; it makes meetings more accessible to everyone. </blockquote>

]]></description>
<dc:subject>team meetings remote communication management caucus-score remote-work</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:950e2f460bdf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:team"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:meetings"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:remote"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:caucus-score"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:remote-work"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://launchdarkly.com/blog/the-time-our-provider-screwed-us/">
    <title>The Time Our Provider Screwed Us</title>
    <dc:date>2018-11-19T11:47:20+00:00</dc:date>
    <link>https://launchdarkly.com/blog/the-time-our-provider-screwed-us/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Good talk (with transcript) from Paul Biggar about what happened when CircleCI had a massive security incident, and how Jesse Robbins helped them do incident response correctly.

'On the left, Jesse pointed out that we needed an incident commander. That’s me, Paul. And this is very good, because I was a big proponent, I think lots of were around the 2013 mark, of flat organizational structures, and so I hadn’t really got a handle of this whole being in charge thing. The fact that someone else came in and said, “No, no, no, you are in charge”: extremely useful. And he also laid out the order of our priorities. Number one priority; safety of customers. Number two priority: communicate with customers. Number three priority: recovery of service.

I think a reasonable person could have put those in a different order, especially under the pressure and time constraints of the potential company-ending situation. So I was very happy to have those in order. If this is ever going to happen to you, I’d memorize them, maybe put it on an index card in your pocket, in case this ever happens.

The last thing he said is to make sure that we log everything, that we go slow, and that we code review and communicate. His point there is that if we’re going to bring our site back up, if we’re going to do all the things that we need to do in order to save our business and do the right thing for our customers and all that, we can’t be making quick, bad decisions. You can’t just upload whatever code is on your computer now, because I have to do this now, I have to fix it. So we set up a Slack channel … This was pre-Slack; it was a HipChat channel, where all of our communications went. Every single communication that we had about this went in that chatroom. Which came in extremely useful the next day, when I had to write a blog post that detailed exactly what had happened and all the steps that we did to fix it and remediate this, and I had an exact time stamps of all the things that had happened.']]></description>
<dc:subject>incidents incident-response paul-biggar circleci security communication outages</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:7d2cf5e786da/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:incidents"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:incident-response"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:paul-biggar"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:circleci"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:outages"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://theoutline.com/post/2437/who-banned-roger-stone">
    <title>Rich &quot;Lowtax&quot; Kyanka on Twitter's abuse/troll problem</title>
    <dc:date>2017-11-01T22:47:20+00:00</dc:date>
    <link>https://theoutline.com/post/2437/who-banned-roger-stone</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>how did you solve this problem at Something Awful? You said you wrote a bunch of rules but internet pedants will always find ways to get around them.

The last rule says we can ban you for any reason. It's like the catch-all. We can ban you if it's too hot in the room, we can ban you if we had a bad day, we can ban you if our finger slips and hits the ban button. And that way people know that if they're doing something and it's not technically breaking any rules but they're obviously trying to push shit as far as they can, we can still ban them. But, unlike Twitter, we actually have what's called the Leper's Colony, which says what they did and has their track record. Twitter just says, “You're gone.”</blockquote>

]]></description>
<dc:subject>twitter communication discussion history somethingawful lowtax</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:e4b003aa86a8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:discussion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:somethingawful"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:lowtax"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://en.wikipedia.org/wiki/Allen_curve">
    <title>Allen curve - Wikipedia</title>
    <dc:date>2017-08-15T10:50:12+00:00</dc:date>
    <link>https://en.wikipedia.org/wiki/Allen_curve</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>During the late 1970s, [Professor Thomas J.] Allen undertook a project to determine how the distance between engineers’ offices affects the frequency of technical communication between them. The result of that research, produced what is now known as the Allen Curve, revealed that there is a strong negative correlation between physical distance and the frequency of communication between work stations. The finding also revealed the critical distance of 50 meters for weekly technical communication.

With the fast advancement of internet and sharp drop of telecommunication cost, some wonder the observation of Allen Curve in today's corporate environment. In his recently co-authored book, Allen examined this question and the same still holds true. He says[2]

"For example, rather than finding that the probability of telephone communication increases with distance, as face-to-face probability decays, our data show a decay in the use of all communication media with distance (following a "near-field" rise)." [p. 58]</blockquote>

Apparently a few years back in Google, some staff mined the promotion data, and were able to show a Allen-like curve that proved a strong correlation between distance from Jeff Dean's desk, and time to getting promoted.]]></description>
<dc:subject>jeff-dean google history allen-curve work communication distance offices workplace teleworking remote-work</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:bf2c2dec3140/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:jeff-dean"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:allen-curve"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:work"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:distance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:offices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:workplace"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:teleworking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:remote-work"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.reddit.com/r/Competitiveoverwatch/comments/4u9w4v/a_guide_to_communication_shotcalling_and/">
    <title>A Guide to Communication, Shotcalling, and Etiquette in Competitive Overwatch</title>
    <dc:date>2016-10-21T11:23:09+00:00</dc:date>
    <link>https://www.reddit.com/r/Competitiveoverwatch/comments/4u9w4v/a_guide_to_communication_shotcalling_and/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Excellent post on team voice comms tactics.  Many tips here]]></description>
<dc:subject>voice voice-comms gaming overwatch communication strats</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:3bcb681032db/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:voice"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:voice-comms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:gaming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:overwatch"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:strats"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ipads4autism-ie.blogspot.ie/">
    <title>iPhones4Autism</title>
    <dc:date>2016-09-25T14:35:09+00:00</dc:date>
    <link>http://ipads4autism-ie.blogspot.ie/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[great idea -- donate old, obsolete iPhone 4/4s phones to a charity which repurposes them for autistic/non-verbal kids]]></description>
<dc:subject>autism communication health phones recycling charity iphones</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:74beb830c13d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:autism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:health"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:phones"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:recycling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:charity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:iphones"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://whispersystems.org/blog/the-ecosystem-is-moving/">
    <title>Open Whisper Systems &gt;&gt; Blog &gt;&gt; Reflections: The ecosystem is moving</title>
    <dc:date>2016-05-11T16:00:18+00:00</dc:date>
    <link>https://whispersystems.org/blog/the-ecosystem-is-moving/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Very interesting post on federation vs centralization for new services:

<blockquote>One of the controversial things we did with Signal early on was to build it as an unfederated service. Nothing about any of the protocols we've developed requires centralization; it's entirely possible to build a federated Signal Protocol based messenger, but I no longer believe that it is possible to build a competitive federated messenger at all.</blockquote>

]]></description>
<dc:subject>development encryption communication network-effects federation signal ip protocols networking smtp platforms</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:2a437dbfac96/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:encryption"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:network-effects"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:federation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:signal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ip"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:protocols"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:networking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:smtp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:platforms"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://instagram-engineering.tumblr.com/post/117889701472/emojineering-part-1-machine-learning-for-emoji">
    <title>Emojineering Part 1: Machine Learning for Emoji Trends - Instagram Engineering</title>
    <dc:date>2015-05-04T12:15:24+00:00</dc:date>
    <link>http://instagram-engineering.tumblr.com/post/117889701472/emojineering-part-1-machine-learning-for-emoji</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Instagram figuring out meanings from Emoji usage contexts using ML. 😮]]></description>
<dc:subject>instagram emoji cool language text internet web speech communication trends machine-learning analysis</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:f5a514bc4d6e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:instagram"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:emoji"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cool"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:text"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:speech"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:trends"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:machine-learning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:analysis"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://silverwraith.com/blog/2014/12/the-case-for-distributed-teams/">
    <title>Avleen Vig on distributed engineering teams</title>
    <dc:date>2015-01-05T11:05:39+00:00</dc:date>
    <link>http://silverwraith.com/blog/2014/12/the-case-for-distributed-teams/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This is a really excellent post on the topic, rebutting Paul Graham's Bay-Area-centric thoughts on the topic very effectively.   I've worked in both distributed and non-distributed, as well as effective and ineffective teams ;), and Avleen's thoughts are very much on target.

<blockquote>I've been involved in the New York start up scene since I joined Etsy in 2010. Since that time, I've seen more and more companies there embrace having distributed teams. Two companies I know which have risen to the top while doing this have been Etsy and DigitalOcean. Both have exceptional engineering teams working on high profile products used by many, many people around the world. There are certainly others outside New York, including Automattic, GitHub, Chef Inc, Puppet... the list goes on.

So how did this happen? And why do people continue to insist that distributed teams lower performance, and are a bad idea?

Partly because we've done a poor job of showing our industry how to be successful at it, and partly because it's hard. Having successful distributed teams requires special skills from management, which arent't easily learned until you have to manage a distributed team. Catch 22.</blockquote>

]]></description>
<dc:subject>business culture management communication work distributed-teams avleen-vig engineering</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:63a4aa8ccc65/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:work"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:distributed-teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:avleen-vig"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:engineering"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://stripe.com/blog/scaling-email-transparency">
    <title>Scaling email transparency</title>
    <dc:date>2014-12-09T17:40:07+00:00</dc:date>
    <link>https://stripe.com/blog/scaling-email-transparency</link>
    <dc:creator>jm</dc:creator><description><![CDATA[This is quite interesting/weird -- Stripe's protocol for mass-CCing email as they scale up the company, based around http://en.wikipedia.org/wiki/Civil_inattention]]></description>
<dc:subject>communication culture email management stripe cc transparency civil-inattention</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:6ec7214e73f1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:email"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stripe"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:transparency"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:civil-inattention"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://zachholman.com/talk/move-fast-break-nothing/">
    <title>Move Fast and Break Nothing</title>
    <dc:date>2014-10-09T15:56:46+00:00</dc:date>
    <link>http://zachholman.com/talk/move-fast-break-nothing/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Great presentation about Github dev culture and building software without breakage,  but still with real progress.]]></description>
<dc:subject>github programming communication process coding teams management dev-culture breakage</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:30418378b79d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:process"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:teams"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:dev-culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:breakage"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://wingedpig.com/2014/09/23/introducing-groups-io/">
    <title>Introducing Groups.io</title>
    <dc:date>2014-09-23T22:39:29+00:00</dc:date>
    <link>http://wingedpig.com/2014/09/23/introducing-groups-io/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Mark "ONEList" Fletcher's back, and he's reinventing the email group!  awesome.

<blockquote>email groups (the modern version of mailing lists) have stagnated over the past decade. Yahoo Groups and Google Groups both exude the dank air of benign neglect. Google Groups hasn’t been updated in years, and some of Yahoo’s recent changes have actually made Yahoo Groups worse! And yet, millions of people put up with this uncertainty and neglect, because email groups are still one of the best ways to communicate with groups of people. And I have a plan to make them even better.
So today I’m launching Groups.io in beta, to bring email groups into the 21st Century. At launch, we have many features that those other services don’t have, including:

Integration with other services, including: Github, Google Hangouts, Dropbox, Instagram, Facebook Pages, and the ability to import Feeds into your groups.
Businesses and organizations can have their own private groups on their own subdomain.
Better archive organization, using hashtags.
Many more email delivery options.
The ability to mute threads or hashtags.
Fully searchable archives, including searching within attachments.

One other feature that Groups.io has that Yahoo and Google don’t, is a business model that’s not based on showing ads to you. Public groups are completely free on Groups.io. Private groups and organizations are very reasonably priced.</blockquote>

]]></description>
<dc:subject>email groups communication discussion mailing-lists groups.io yahoo google google-groups yahoo-groups</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:1afb25ef608e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:email"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:groups"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:discussion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mailing-lists"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:groups.io"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:yahoo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:google-groups"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:yahoo-groups"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.schneier.com/blog/archives/2013/09/the_nsa_is_brea.html">
    <title>Schneier on Security: The NSA Is Breaking Most Encryption on the Internet</title>
    <dc:date>2013-09-05T22:15:21+00:00</dc:date>
    <link>http://www.schneier.com/blog/archives/2013/09/the_nsa_is_brea.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>The new Snowden revelations are explosive. Basically, the NSA is able to decrypt most of the Internet. They're doing it primarily by cheating, not by mathematics.
It's joint reporting between the Guardian, the New York Times, and ProPublica.
I have been working with Glenn Greenwald on the Snowden documents, and I have seen a lot of them. These are my two essays on today's revelations.
Remember this: The math is good, but math has no agency. Code has agency, and the code has been subverted.</blockquote>

]]></description>
<dc:subject>encryption communication government nsa security bruce-schneier crypto politics snooping gchq guardian journalism</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:2617942fe6b5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:encryption"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:government"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nsa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bruce-schneier"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:crypto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:politics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:snooping"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:gchq"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:guardian"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:journalism"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ceasefiremagazine.co.uk/indymedia-its-time-move/">
    <title>Indymedia: It’s time to move on</title>
    <dc:date>2013-02-22T16:20:00+00:00</dc:date>
    <link>http://ceasefiremagazine.co.uk/indymedia-its-time-move/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>Our decision to curtail publishing on the Nottingham Indymedia site and call a meeting is an attempt to create a space for new ideas. We are not interested in continuing along the slow but certain path to total irrelevance but want to draw in new people and start off in new directions whilst remaining faithful to the underlying principles of Indymedia.</blockquote>

]]></description>
<dc:subject>indymedia community communication web anonymity publishing left-wing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:d50f2fad54e6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:indymedia"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:community"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:anonymity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:publishing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:left-wing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://shackspace.de/wiki/doku.php?id=project:hgg:faq">
    <title>Project HGG: FAQ</title>
    <dc:date>2012-01-09T22:27:43+00:00</dc:date>
    <link>http://shackspace.de/wiki/doku.php?id=project:hgg:faq</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Hackerspace Global Grid -- 'We want to understand, build and make available satellite based communication for the hackerspace community and all of mankind.'  Space is the place!]]></description>
<dc:subject>space ccc satellite communication internet hackerspace</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:56c795595368/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:space"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ccc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:satellite"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:communication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:hackerspace"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>