<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://htyp.org/mw/index.php?action=history&amp;feed=atom&amp;title=InstaGov%2Fissues</id>
	<title>InstaGov/issues - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://htyp.org/mw/index.php?action=history&amp;feed=atom&amp;title=InstaGov%2Fissues"/>
	<link rel="alternate" type="text/html" href="https://htyp.org/mw/index.php?title=InstaGov/issues&amp;action=history"/>
	<updated>2026-06-27T10:45:52Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.45.3</generator>
	<entry>
		<id>https://htyp.org/mw/index.php?title=InstaGov/issues&amp;diff=19229&amp;oldid=prev</id>
		<title>Woozle: extracted from syntax page</title>
		<link rel="alternate" type="text/html" href="https://htyp.org/mw/index.php?title=InstaGov/issues&amp;diff=19229&amp;oldid=prev"/>
		<updated>2012-12-30T16:18:39Z</updated>

		<summary type="html">&lt;p&gt;extracted from syntax page&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;==Retroactive Content Changing==&lt;br /&gt;
There is a potential problem where a user edits a question or answer so as to change the sense of it &amp;#039;&amp;#039;after&amp;#039;&amp;#039; some consequences (answers to a question, ratings of an answer) have already been registered.&lt;br /&gt;
&lt;br /&gt;
The rigorous way to prevent this would be for vote to be tied to a particular revision of a question/answer. I am hoping that community monitoring will turn out to be more effective at preventing malicious content-modification than revision control would be -- e.g. users can vote on whether an edit reflects a significant change to a item&amp;#039;s meaning, and whether it should have been posted as a separate item. That will also take some development, but won&amp;#039;t be as much of a usability obstacle as making everyone vote &amp;#039;&amp;#039;again&amp;#039;&amp;#039; every time there&amp;#039;s a minor tweak to an answer&amp;#039;s content.&lt;br /&gt;
&lt;br /&gt;
In any case, I&amp;#039;m taking the approach of developing the simplest system that&amp;#039;s usable, but trying to anticipate problems and having ideas fleshed out for dealing with them if they happen.&lt;/div&gt;</summary>
		<author><name>Woozle</name></author>
	</entry>
</feed>