<?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: The contemplated update to the #trilema voice model</title>
	<atom:link href="http://trilema.com/2019/the-contemplated-update-to-the-trilema-voice-model/feed/" rel="self" type="application/rss+xml" />
	<link>http://trilema.com/2019/the-contemplated-update-to-the-trilema-voice-model/</link>
	<description>Moving targets for a fast crowd.</description>
	<pubDate>Wed, 29 Apr 2026 01:36:59 +0000</pubDate>
	<generator>http://polimedia.us</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: #ossasepia +m &#171; Ossa Sepia</title>
		<link>http://trilema.com/2019/the-contemplated-update-to-the-trilema-voice-model/#comment-154237</link>
		<dc:creator>#ossasepia +m &#171; Ossa Sepia</dc:creator>
		<pubDate>Sat, 12 Sep 2020 08:07:28 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=90811#comment-154237</guid>
		<description>[...] in #ossasepia! While waiting for the implementation of the more modern solution of a proper WoT-based voice model.&#160;&#8617;If you are in my WoT but don't have voice in #ossasepia just pm me please and I'll [...]</description>
		<content:encoded><![CDATA[<p>[...] in #ossasepia! While waiting for the implementation of the more modern solution of a proper WoT-based voice model.&nbsp;&#8617;If you are in my WoT but don't have voice in #ossasepia just pm me please and I'll [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Review of the Bitcoin Category on trilema.com &#171; Ossa Sepia</title>
		<link>http://trilema.com/2019/the-contemplated-update-to-the-trilema-voice-model/#comment-148134</link>
		<dc:creator>A Review of the Bitcoin Category on trilema.com &#171; Ossa Sepia</dc:creator>
		<pubDate>Fri, 27 Mar 2020 20:34:14 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=90811#comment-148134</guid>
		<description>[...] description of the proposed changes to the voice model to center them on the owner of a chan as opposed to a bot. [...]</description>
		<content:encoded><![CDATA[<p>[...] description of the proposed changes to the voice model to center them on the owner of a chan as opposed to a bot. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mircea Popescu</title>
		<link>http://trilema.com/2019/the-contemplated-update-to-the-trilema-voice-model/#comment-132662</link>
		<dc:creator>Mircea Popescu</dc:creator>
		<pubDate>Sun, 15 Dec 2019 21:20:50 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=90811#comment-132662</guid>
		<description>But look at it : person joins, is voiced. Now what ? If he leaves the machine, and it loses power / connectivity, they'll be disconnected, so no ban -- it only applies if they stay connected but not voiced. If they get unvoiced, they can just disconnect. If they leave during their half hour window, after being voiced, they're just being disrespectful, I don't care what "aunt came to visit" bs ; but that notwithstanding it takes three occurences in a day at a minimum to make the cut, because two almost-half hours don't make an hour. And, of course, in any case I can just remove a ban by issuing the equivalent oneliner, /mode -b whatever.

The problem with making it as long as a day is that it expands the watching trinque has to do. You understand, to establish something like "has been X for Y time" computers poll periodically : is it X ? every Y/k intervals. Just like digitized music works, if you sample at 44KHz, you get 44`000 note states (up ? down ?) each second. If you do it at 44MHz you get... 44`000`000 note states. This makes the difference between 44 Kbits and 44 Mbits per second, which is why nobody samples at 44 MHz, which is why the whole flac / "lossless" compression's less lossless than the "audiophiles" care to understand.</description>
		<content:encoded><![CDATA[<p>But look at it : person joins, is voiced. Now what ? If he leaves the machine, and it loses power / connectivity, they'll be disconnected, so no ban -- it only applies if they stay connected but not voiced. If they get unvoiced, they can just disconnect. If they leave during their half hour window, after being voiced, they're just being disrespectful, I don't care what "aunt came to visit" bs ; but that notwithstanding it takes three occurences in a day at a minimum to make the cut, because two almost-half hours don't make an hour. And, of course, in any case I can just remove a ban by issuing the equivalent oneliner, /mode -b whatever.</p>
<p>The problem with making it as long as a day is that it expands the watching trinque has to do. You understand, to establish something like "has been X for Y time" computers poll periodically : is it X ? every Y/k intervals. Just like digitized music works, if you sample at 44KHz, you get 44`000 note states (up ? down ?) each second. If you do it at 44MHz you get... 44`000`000 note states. This makes the difference between 44 Kbits and 44 Mbits per second, which is why nobody samples at 44 MHz, which is why the whole flac / "lossless" compression's less lossless than the "audiophiles" care to understand.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pletzalcoatl</title>
		<link>http://trilema.com/2019/the-contemplated-update-to-the-trilema-voice-model/#comment-132660</link>
		<dc:creator>pletzalcoatl</dc:creator>
		<pubDate>Sun, 15 Dec 2019 20:42:24 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=90811#comment-132660</guid>
		<description>Yeah, I particularly like item #6. I do expect there could be some exceptional cases though where someone could be voiced in #trilema and speak a while, then need to pause before speaking again (as in say some media visitor/old-timer contacted via email), wherein the hour's limit resulting in an actual ban for #trilema could be a hindrance to all. So: possibly an hour's not long enough. I propose a day, or something closer to it. Will catch actual lurkers, less likely to catch edgecases and require runaround administering thereby.</description>
		<content:encoded><![CDATA[<p>Yeah, I particularly like item #6. I do expect there could be some exceptional cases though where someone could be voiced in #trilema and speak a while, then need to pause before speaking again (as in say some media visitor/old-timer contacted via email), wherein the hour's limit resulting in an actual ban for #trilema could be a hindrance to all. So: possibly an hour's not long enough. I propose a day, or something closer to it. Will catch actual lurkers, less likely to catch edgecases and require runaround administering thereby.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diana Coman</title>
		<link>http://trilema.com/2019/the-contemplated-update-to-the-trilema-voice-model/#comment-132613</link>
		<dc:creator>Diana Coman</dc:creator>
		<pubDate>Wed, 11 Dec 2019 18:55:24 +0000</pubDate>
		<guid isPermaLink="false">http://trilema.com/?p=90811#comment-132613</guid>
		<description>Better indeed! Thank you.</description>
		<content:encoded><![CDATA[<p>Better indeed! Thank you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
