<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: EsperNet 2nd Chance</title>
	<atom:link href="http://thimbron.com/2019/10/espernet-2nd-chance/feed/" rel="self" type="application/rss+xml" />
	<link>http://thimbron.com/2019/10/espernet-2nd-chance/</link>
	<description>ὁι λογοι και τα ἐργα</description>
	<pubDate>Wed, 23 Sep 2026 11:34:24 +0000</pubDate>
	<generator>http://polimedia.us</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Diana Coman</title>
		<link>http://thimbron.com/2019/10/espernet-2nd-chance/#comment-30</link>
		<dc:creator>Diana Coman</dc:creator>
		<pubDate>Fri, 18 Oct 2019 06:15:52 +0000</pubDate>
		<guid isPermaLink="false">http://thimbron.com/?p=300#comment-30</guid>
		<description>It's very hard to follow who-said-what in your transcript above. Put in the nicknames for each line, it can't work like this (for a while I was wondering if you had several nicks in there, lolz).

Other than that, there is some improvement in there. You need however to do 2 things: communication means you engage with them and *react* to what is said as well as to what is not said though it should have been; you can't just go in with a statement and a rigid expectation of specific response, getting totally stuck if the response is different. That's not communication, it's closer to bot-like "interaction". Why are you so easily stuck on this anyway?</description>
		<content:encoded><![CDATA[<p>It's very hard to follow who-said-what in your transcript above. Put in the nicknames for each line, it can't work like this (for a while I was wondering if you had several nicks in there, lolz).</p>
<p>Other than that, there is some improvement in there. You need however to do 2 things: communication means you engage with them and *react* to what is said as well as to what is not said though it should have been; you can't just go in with a statement and a rigid expectation of specific response, getting totally stuck if the response is different. That's not communication, it's closer to bot-like "interaction". Why are you so easily stuck on this anyway?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
