|
1
|
1 <?xml version="1.0" encoding="utf-8"?>
|
|
|
2
|
|
|
3 <feed xmlns="http://www.w3.org/2005/Atom">
|
|
|
4 <title>Changaco's blog</title>
|
|
|
5 <link href="http://changaco.net/blog/"/>
|
|
|
6 <link href="http://changaco.net/blog/feed.atom" rel="self" type="application/atom+xml"/>
|
|
|
7 <author>
|
|
|
8 <name>Changaco</name>
|
|
|
9
|
|
|
10 </author>
|
|
|
11
|
|
|
12
|
|
|
13
|
|
|
14 <id>http://changaco.net/blog/</id>
|
|
|
15
|
|
|
16 <subtitle type="html">Changaco</subtitle>
|
|
|
17 <generator uri="http://ikiwiki.info/" version="3.20111107">ikiwiki</generator>
|
|
|
18 <updated>2011-12-10T13:52:20Z</updated>
|
|
|
19 <entry>
|
|
|
20 <title>DNS problems and alternatives</title>
|
|
|
21
|
|
|
22 <id>http://changaco.net/blog/DNS_problems_and_alternatives/</id>
|
|
|
23
|
|
|
24 <link href="http://changaco.net/blog/DNS_problems_and_alternatives/"/>
|
|
|
25
|
|
|
26
|
|
|
27
|
|
|
28
|
|
|
29
|
|
|
30 <updated>2011-12-10T13:34:21Z</updated>
|
|
|
31 <published>2011-12-10T13:34:21Z</published>
|
|
|
32
|
|
|
33 <content type="html" xml:lang="en">
|
|
|
34 <p>Replacing the <abbr title="Domain Name System">DNS</abbr> is a recurrent topic. In this post I try to explain the problems and give a list of existing or proposed alternatives.</p>
|
|
|
35
|
|
|
36 <h2 id="problemsofthedns">Problems of the DNS</h2>
|
|
|
37
|
|
|
38 <p>A little terminology first : the DNS has two functions, registering and resolving names. Critics of the registration mechanisms are mostly political, resolution problems are mostly technical.</p>
|
|
|
39
|
|
|
40 <h3 id="censorship">Censorship</h3>
|
|
|
41
|
|
|
42 <p>The US government has <a href="http://torrentfreak.com/feds-seize-130-domain-names-in-mass-crackdown-111125/">seized many domain names in November 2011</a>, as it had done the year before. Contrary to what some people said, <a href="http://domainincite.com/icann-had-no-role-in-seizing-torrent-domains/">the ICANN was not involved in those operations</a>. It was <a href="http://en.wikipedia.org/wiki/Verisign">Verisign</a>, the operator of the .com, .net, and .name generic top-level domains, that was ordered to seize the domains. As a result, some sites have fled generic TLDs controlled by US companies.</p>
|
|
|
43
|
|
|
44 <h3 id="economicvampirismanddomainparking">Economic vampirism and domain parking</h3>
|
|
|
45
|
|
|
46 <p>The DNS is a big profitable business.</p>
|
|
|
47
|
|
|
48 <p>The name renting (you can't buy a domain name) business works like this : client → registrar (domain manager) → registry (<abbr title="Top-Level Domain">TLD</abbr> manager) → ICANN (root manager). Some of these organizations are nonprofit (e.g. ICANN), but that doesn't mean people working for them don't profit (there are high salaries, expensive dinners, trips, etc). Others are corporations that make very good profits<a href="http://changaco.net/blog/#fn:1" id="fnref:1" class="footnote">1</a>.</p>
|
|
|
49
|
|
|
50 <p>X.509 certificates are another business. They are delivered by Certificate Authorities and used in TLS. This security model has been widely criticized<a href="http://changaco.net/blog/#fn:2" id="fnref:2" class="footnote">2</a><a href="http://changaco.net/blog/#fn:3" id="fnref:3" class="footnote">3</a><a href="http://changaco.net/blog/#fn:4" id="fnref:4" class="footnote">4</a> and there are plans to put certificates directly in DNS records<a href="http://changaco.net/blog/#fn:5" id="fnref:5" class="footnote">5</a><a href="http://changaco.net/blog/#fn:6" id="fnref:6" class="footnote">6</a>, and others to replace X.509 by OpenPGP<a href="http://changaco.net/blog/#fn:7" id="fnref:7" class="footnote">7</a>.</p>
|
|
|
51
|
|
|
52 <p>Finally, there is the very annoying <a href="http://en.wikipedia.org/wiki/domain%20parking">domain parking</a> business.</p>
|
|
|
53
|
|
|
54 <h3 id="technicalproblems">Technical problems</h3>
|
|
|
55
|
|
|
56 <p>Being very old, the DNS also has technical weaknesses.</p>
|
|
|
57
|
|
|
58 <p>The first is slow propagation of records because the DNS uses time-based caches.</p>
|
|
|
59
|
|
|
60 <p>The second is that records are not stored in a P2P network, but by authoritative servers, which can be taken down by <abbr title="Denial of Service">DoS</abbr> attacks if they aren't sufficiently protected. This is rarely a problem in practice though.</p>
|
|
|
61
|
|
|
62 <h2 id="whyhaventtheproblemsbeensolvedyet">Why haven't the problems been solved yet ?</h2>
|
|
|
63
|
|
|
64 <p>Well, because different people want things that are contradictory. The problem is often known as <a href="http://en.wikipedia.org/wiki/Zooko%27s%20triangle">Zooko's triangle</a>, but there are in fact more than three desirable properties for identifiers :<a href="http://changaco.net/blog/#fn:8" id="fnref:8" class="footnote">8</a></p>
|
|
|
65
|
|
|
66 <ul>
|
|
|
67 <li>We want to <strong>choose</strong> a <strong>unique</strong> and <strong>memorable</strong> name so we can communicate it to somebody else even if we don't have our computer with us at the moment. Some people who always have their smartphone with them may argue that this property is not important anymore, but not everybody has a smartphone.</li>
|
|
|
68 <li>We want a <strong>censorship-free</strong> system.</li>
|
|
|
69 <li>We want our <strong>trademarks</strong> to be registered only by us.</li>
|
|
|
70 <li>We want links between documents that are <strong>stable in time</strong>, the Web doesn't like broken URLs.</li>
|
|
|
71 <li>We want the registration process to be <strong>easy, fast and free of charge</strong>.</li>
|
|
|
72 <li>We want a name to be <strong>resolvable</strong> to an address, otherwise it's of no use to us.</li>
|
|
|
73 <li>We want names that are <strong>recoverable</strong> in case of hijacking or loss of credentials.</li>
|
|
|
74 </ul>
|
|
|
75
|
|
|
76 <h2 id="existingorproposedalternatives">Existing or proposed alternatives</h2>
|
|
|
77
|
|
|
78 <p>I can't help but start by my own DNS replacement proposal. <img src="http://changaco.net/blog/../smileys/smile.png" alt=":)" /> The <a href="http://changaco.net/ins/">Internet Naming System</a> acknowledges that there is no perfect solution and chooses to keep a central authority for name allocation. It makes censorship automatically detectable but not impossible.</p>
|
|
|
79
|
|
|
80 <p>Projects for P2P registration of names :</p>
|
|
|
81
|
|
|
82 <ul>
|
|
|
83 <li><a href="http://dot-bit.org/">Dot-BIT</a> (<a href="irc://irc.freenode.net/namecoin">#namecoin on freenode</a>) uses Bitcoin-like proof-of-work (which assumes that honest nodes have the majority of computing power)</li>
|
|
|
84 <li><a href="http://www.p2pns.org/">P2PNS</a> assumes that a vast majority of peers is honest</li>
|
|
|
85 <li><a href="http://lauren.vortex.com/archive/000787.html">IDONS: Internet Distributed Open Name System</a> (<a href="http://forums.gctip.org/forum-34.html">forum</a>) seems dead</li>
|
|
|
86 <li><a href="irc://irc.efnet.org/dns-p2p">#dns-p2p</a>, which used to have a wiki on dot-p2p.org, never gave anything and is dead</li>
|
|
|
87 </ul>
|
|
|
88
|
|
|
89 <p>Technical solutions for improving resolution :</p>
|
|
|
90
|
|
|
91 <ul>
|
|
|
92 <li><a href="http://beehive.systems.cs.cornell.edu/codons.php">CoDoNS</a></li>
|
|
|
93 <li><a href="http://huitema.wordpress.com/2011/01/03/a-simple-p2p-dns-proposal/">A simple P2P DNS proposal</a></li>
|
|
|
94 </ul>
|
|
|
95
|
|
|
96 <p>Other projects :</p>
|
|
|
97
|
|
|
98 <ul>
|
|
|
99 <li><a href="http://opennicproject.org/">OpenNIC</a> (<a href="irc://irc.freenode.net/opennic">#opennic on freenode</a>, <a href="http://lists.darkdna.net/mailman/listinfo">OpenNIC lists</a>) is an alternative root</li>
|
|
|
100 <li><a href="http://dns.telecomix.org/">Telecomix Censorship-proof DNS</a> (<a href="irc://irc.telecomix.org/dns">#dns on telecomix IRC</a>)</li>
|
|
|
101 </ul>
|
|
|
102
|
|
|
103 <p>Other proposals :</p>
|
|
|
104
|
|
|
105 <ul>
|
|
|
106 <li>on the <a href="http://lists.zooko.com/mailman/listinfo/p2p-hackers">p2p-hackers list</a> :
|
|
|
107 <ul>
|
|
|
108 <li><a href="http://lists.zooko.com/pipermail/p2p-hackers/2010-December/002598.html">Secure, decentralized DNS (a.k.a. solving Zooko's triangle)</a></li>
|
|
|
109 <li><a href="http://lists.zooko.com/pipermail/p2p-hackers/2010-December/002587.html">.p2p domain</a></li>
|
|
|
110 </ul></li>
|
|
|
111 <li><a href="http://roland.entierement.nu/blog/2010/10/02/for-a-truly-acentric-internet.html">For a truly acentric Internet</a>, proposes to abandon meaningful identifiers (an old proposition that comes back regularly)</li>
|
|
|
112 <li><a href="http://www.templetons.com/brad/dns/">Problems, Goals and a Fix for Domain Names</a>, proposed to only allow trademarks as TLDs</li>
|
|
|
113 </ul>
|
|
|
114
|
|
|
115 <h2 id="referencesandcredits">References and credits</h2>
|
|
|
116
|
|
|
117 <p>Thanks to Stéphane Bortzmeyer for helping with this post.</p>
|
|
|
118
|
|
|
119 <div class="footnotes">
|
|
|
120 <hr />
|
|
|
121 <ol>
|
|
|
122
|
|
|
123 <li id="fn:1"><p><a href="http://www.chemla.org/textes/voleur.html">Confessions d'un voleur</a> [fr]<a href="http://changaco.net/blog/#fnref:1" class="reversefootnote">&#160;&#8617;</a></p></li>
|
|
|
124
|
|
|
125 <li id="fn:2"><p><a href="https://www.eff.org/deeplinks/2010/03/researchers-reveal-likelihood-governments-fake-ssl">New Research Suggests That Governments May Fake SSL Certificates</a><a href="http://changaco.net/blog/#fnref:2" class="reversefootnote">&#160;&#8617;</a></p></li>
|
|
|
126
|
|
|
127 <li id="fn:3"><p><a href="https://docs.google.com/present/view?id=df9sn445_206ff3kn9gs">It's Time to Fix HTTPS</a><a href="http://changaco.net/blog/#fnref:3" class="reversefootnote">&#160;&#8617;</a></p></li>
|
|
|
128
|
|
|
129 <li id="fn:4"><p><a href="http://lair.fifthhorseman.net/~dkg/tls-centralization/">Technical Architecture shapes Social Structure: an example from the real world</a><a href="http://changaco.net/blog/#fnref:4" class="reversefootnote">&#160;&#8617;</a></p></li>
|
|
|
130
|
|
|
131 <li id="fn:5"><p><a href="http://tools.ietf.org/wg/dane/">DNS-based Authentication of Named Entities - IETF Working Group</a><a href="http://changaco.net/blog/#fnref:5" class="reversefootnote">&#160;&#8617;</a></p></li>
|
|
|
132
|
|
|
133 <li id="fn:6"><p><a href="http://www.bortzmeyer.org/jres-dane-2011.html">Exposé sur les clés dans le DNS à JRES</a> [fr]<a href="http://changaco.net/blog/#fnref:6" class="reversefootnote">&#160;&#8617;</a></p></li>
|
|
|
134
|
|
|
135 <li id="fn:7"><p><a href="http://web.monkeysphere.info/">The Monkeysphere Project</a><a href="http://changaco.net/blog/#fnref:7" class="reversefootnote">&#160;&#8617;</a></p></li>
|
|
|
136
|
|
|
137 <li id="fn:8"><p><a href="http://www.bortzmeyer.org/no-free-lunch.html">Inventer un meilleur système de nommage: pas si facile</a> [fr]<a href="http://changaco.net/blog/#fnref:8" class="reversefootnote">&#160;&#8617;</a></p></li>
|
|
|
138
|
|
|
139 </ol>
|
|
|
140 </div>
|
|
|
141
|
|
|
142 </content>
|
|
|
143
|
|
|
144
|
|
|
145 <link rel="comments" href="/blog/DNS_problems_and_alternatives/#comments" type="text/html" />
|
|
|
146
|
|
|
147
|
|
|
148 <link rel="comments" href="/blog/DNS_problems_and_alternatives/comments.atom" type="application/atom+xml" />
|
|
|
149
|
|
|
150 </entry>
|
|
|
151 <entry>
|
|
|
152 <title>Privacy and distant storage</title>
|
|
|
153
|
|
|
154 <id>http://changaco.net/blog/Privacy_and_distant_storage/</id>
|
|
|
155
|
|
|
156 <link href="http://changaco.net/blog/Privacy_and_distant_storage/"/>
|
|
|
157
|
|
|
158
|
|
|
159
|
|
|
160
|
|
|
161
|
|
|
162
|
|
|
163 <category term="tags/idea" />
|
|
|
164
|
|
|
165 <category term="tags/internet" />
|
|
|
166
|
|
|
167
|
|
|
168 <updated>2010-09-02T11:12:33Z</updated>
|
|
|
169 <published>2010-08-30T22:45:55Z</published>
|
|
|
170
|
|
|
171 <content type="html" xml:lang="en">
|
|
|
172 <p>Some people seem to think that their data is only safe in their own homes. I agree that not keeping a local copy or storing unprotected personal documents on a machine you don't control are bad things. But I was reminded today (while trolling on <a href="http://www.numerama.com/">Numerama</a>, a French tech-related news site) that having them home doesn't make them safe from:</p>
|
|
|
173
|
|
|
174 <ul>
|
|
|
175 <li>hardware failures such as hard drive breakdowns (although <a href="http://smartmontools.sourceforge.net/">smartmontools</a> may be able to alert you before it is too late)</li>
|
|
|
176 <li>disasters such as fire</li>
|
|
|
177 </ul>
|
|
|
178
|
|
|
179 <p>Of course, if your home burns, loosing your files will be the least of your concerns, but if you know they are safe it is one less thing to worry about.</p>
|
|
|
180
|
|
|
181 <p>Then I realized that having backups in different geographic places does not necessarily endanger your privacy, it just depends on how you do it. What you need is to encrypt and/or cut the data so that the people who will store it for you will not be able to read or exploit it (just like <a href="http://en.wikipedia.org/wiki/Freenet">Freenet</a> does for different reasons).</p>
|
|
|
182
|
|
|
183 <p>So the next question is where to store it ? I came to see three possibilities:</p>
|
|
|
184
|
|
|
185 <ul>
|
|
|
186 <li>pay for some storage service, might be necessary if you have a lot of data</li>
|
|
|
187 <li>share storage space with peers, this was my original thought</li>
|
|
|
188 <li>share storage space with family and/or friends, this the safest of the three and credit goes to Kaliko for suggesting it on the <a href="xmpp:utopians@muc.changaco.net?join">utopians chat room</a></li>
|
|
|
189 </ul>
|
|
|
190
|
|
|
191 <p>I believe, like many others, that a good place for such sharing software is in <a href="http://en.wikipedia.org/wiki/residential%20gateway">residential gateway</a>s, maybe we'll see it implemented someday in the <a href="http://wiki.debian.org/FreedomBox">Freedom Box</a> ?</p>
|
|
|
192
|
|
|
193 </content>
|
|
|
194
|
|
|
195
|
|
|
196 <link rel="comments" href="/blog/Privacy_and_distant_storage/#comments" type="text/html" />
|
|
|
197
|
|
|
198
|
|
|
199 <link rel="comments" href="/blog/Privacy_and_distant_storage/comments.atom" type="application/atom+xml" />
|
|
|
200
|
|
|
201 </entry>
|
|
|
202 <entry>
|
|
|
203 <title>tabs vs spaces</title>
|
|
|
204
|
|
|
205 <id>http://changaco.net/blog/tabs_vs_spaces/</id>
|
|
|
206
|
|
|
207 <link href="http://changaco.net/blog/tabs_vs_spaces/"/>
|
|
|
208
|
|
|
209
|
|
|
210
|
|
|
211
|
|
|
212
|
|
|
213 <updated>2011-04-12T09:23:05Z</updated>
|
|
|
214 <published>2010-06-01T15:09:22Z</published>
|
|
|
215
|
|
|
216 <content type="html" xml:lang="en">
|
|
|
217 <p>In this post I try to summarize the different points of view on the tabs versus spaces war.</p>
|
|
|
218
|
|
|
219 <h2 id="decompositionoftheproblem">Decomposition of the problem</h2>
|
|
|
220
|
|
|
221 <p>Firstly, you need to understand the difference between the <strong>tab key</strong> and the <strong>tab character</strong>. What you text editor does when you press the tab key is a matter of configuration and has nothing to do with the problem discussed here.</p>
|
|
|
222
|
|
|
223 <p>Secondly, we need to distinguish <strong>indentation</strong> and <strong>alignment</strong>, this is explained in <a href="http://www.iovene.com/61">TABs vs Spaces. The end of the debate.</a> and shows why the historical rendering of tabs is not fit for alignment.</p>
|
|
|
224
|
|
|
225 <h2 id="thesolutions">The solutions</h2>
|
|
|
226
|
|
|
227 <h3 id="useonlyspaces">Use only spaces</h3>
|
|
|
228
|
|
|
229 <p>This is the solution proposed by many and is notably exposed in <a href="http://www.jwz.org/doc/tabs-vs-spaces.html">Tabs versus Spaces: An Eternal Holy War.</a></p>
|
|
|
230
|
|
|
231 <p>The obvious solution when dynamic doesn't work is to fall back to static. Using only spaces does indeed work for both indentation and aligning and you can configure most text editors to make it as easy as using tabs. So, what's wrong with it ? Here's a list :</p>
|
|
|
232
|
|
|
233 <ul>
|
|
|
234 <li>you can't use proportional fonts</li>
|
|
|
235 <li>you can't easily change the indentation width</li>
|
|
|
236 <li>your files are larger</li>
|
|
|
237 </ul>
|
|
|
238
|
|
|
239 <p>The two first points are all about freedom, maybe you don't like proportional fonts to code, but some people do.</p>
|
|
|
240
|
|
|
241 <p>As to the third point, people usually reject it by saying that it doesn't matter nowadays because of disks capacity, network speed and compression. Still, I wanted to make a <em>quick and dirty</em> measure of the impact of the 4 spaces policy on python 2.6 on my system as of June 2010 ( done in zsh ) :</p>
|
|
|
242
|
|
|
243 <pre><code># cd /usr/lib/python2.6
|
|
|
244 # for f in **/*(/); do mkdir -p "../python2.6.spaces/&#036;f" "../python2.6.tabs/&#036;f"; done;
|
|
|
245 # for f in **/*.py; do cp "&#036;f" "../python2.6.spaces/&#036;f"; cp "&#036;f" "../python2.6.tabs/&#036;f"; done;
|
|
|
246 # du -h --max-depth=0 python2.6.*
|
|
|
247 43M python2.6.spaces
|
|
|
248 43M python2.6.tabs
|
|
|
249
|
|
|
250 # cd ../python2.6.tabs
|
|
|
251 # sed 's/^\(\t*\) /\1\t/' -i **/*.py
|
|
|
252 # du -h --max-depth=0 ../python2.6.tabs
|
|
|
253 41M ../python2.6.tabs
|
|
|
254 # sed 's/^\(\t*\) /\1\t/' -i **/*.py
|
|
|
255 # du -h --max-depth=0 ../python2.6.tabs
|
|
|
256 39M ../python2.6.tabs
|
|
|
257
|
|
|
258 ... I did it two more times but the rounded number stayed 39M
|
|
|
259 </code></pre>
|
|
|
260
|
|
|
261 <p>The result is that using 4 spaces instead of tabs makes files about 10% bigger. If you get a different result or tested something else than python 2.6 I invite you to post a comment.</p>
|
|
|
262
|
|
|
263 <h3 id="usespacesforalignment">Use spaces for alignment</h3>
|
|
|
264
|
|
|
265 <p>Since the problem with tabs is alignment, some people argue that you can use whatever you want for indentation as long as you use spaces for alignment. If you choose to use tabs, the indentation width is no longer an issue and most of the space waste goes away, but you still can't use proportional fonts.</p>
|
|
|
266
|
|
|
267 <h3 id="elastictabstops">Elastic tabstops</h3>
|
|
|
268
|
|
|
269 <p>This solution solves all the issues listed here and makes alignment easier. How ? By redefining the way the tab character is displayed. It's all explained in <a href="http://nickgravgaard.com/elastictabstops/">Elastic tabstops - a better way to indent and align code</a>. The downside is that text editors' code has to be modified.</p>
|
|
|
270
|
|
|
271 <h2 id="myopinion">My opinion</h2>
|
|
|
272
|
|
|
273 <p>I use tabs for indentation, spaces for alignment and I wish elastic tabstops were more widely known, implemented and used.</p>
|
|
|
274
|
|
|
275 </content>
|
|
|
276
|
|
|
277
|
|
|
278 <link rel="comments" href="/blog/tabs_vs_spaces/#comments" type="text/html" />
|
|
|
279
|
|
|
280
|
|
|
281 <link rel="comments" href="/blog/tabs_vs_spaces/comments.atom" type="application/atom+xml" />
|
|
|
282
|
|
|
283 </entry>
|
|
|
284 <entry>
|
|
|
285 <title>Réponse à Daniel Glazman</title>
|
|
|
286
|
|
|
287 <id>http://changaco.net/blog/R%C3%A9ponse_%C3%A0_Daniel_Glazman/</id>
|
|
|
288
|
|
|
289 <link href="http://changaco.net/blog/R%C3%A9ponse_%C3%A0_Daniel_Glazman/"/>
|
|
|
290
|
|
|
291
|
|
|
292
|
|
|
293
|
|
|
294
|
|
|
295 <updated>2011-12-10T13:50:13Z</updated>
|
|
|
296 <published>2010-05-16T20:49:20Z</published>
|
|
|
297
|
|
|
298 <content type="html" xml:lang="en">
|
|
|
299 <p>Comme le dit le dicton populaire : « mieux vaut tard que jamais ». Je vais donc profiter de l'ouverture de mon blog pour répondre à un message de Daniel Glazman, mais ce billet concerne aussi Tristan Nitot.</p>
|
|
|
300
|
|
|
301 <p>Commençons par poser le décor, l'histoire commence avec une <a href="http://standblog.org/blog/post/2010/04/02/Interview-Glazman-BlueGriffon">interview de Daniel Glazman par Tristan Nitot</a>. Ayant le Standblog dans mon lecteur de flux je lis l'article et trouvant étrange le modèle économique choisi par M. Glazman je décide de laisser un commentaire :</p>
|
|
|
302
|
|
|
303 <blockquote>
|
|
|
304 <p>Encore et toujours en train d'essayer de vendre des copies, quand allez-vous comprendre que ce n'est pas un modèle viable ?<br />
|
|
|
305 Voir entre autres : <a href="http://hcsoftware.sourceforge.net/jason-rohrer/freeDistribution.html">Free Distribution</a>.</p>
|
|
|
306 </blockquote>
|
|
|
307
|
|
|
308 <p>J'avoue que c'était plutôt <em>trollesque</em>, j'aurais pu commencer par une question plus neutre sur le pourquoi du modèle économique choisi.</p>
|
|
|
309
|
|
|
310 <p>C'est là que commencent les choses intéressantes. Tout d'abord, les commentaires étaient modérés à priori ce qui compliquait le débat en introduisant de longs délais, on a continué malgré tout, jusqu'à ce que M. Nitot ferme les commentaires, sans donner d'explication. <a href="http://changaco.net/blog/#note1" id="note1_c1" title="Aller &agrave; la note 1">1</a></p>
|
|
|
311
|
|
|
312 <p>Puis quelqu'un qui est abonné au blog de M. Glazman m'envoie un message sur Jabber pour me signaler que celui-ci a publié un billet pour continuer le débat : <a href="http://www.glazman.org/weblog/dotclear/index.php?post/2010/04/07/Usual-suspects">Usual suspects - &lt;Glazblog/&gt;</a>.</p>
|
|
|
313
|
|
|
314 <p>Je réponds donc là-bas, mais M. Glazman en a vite marre et ferme les commentaires à son tour, en laissant ce message :</p>
|
|
|
315
|
|
|
316 <blockquote>
|
|
|
317 <p>A ce point, crevé par le jetlag, une crève monumentale et mon retour tardif de Paris hier soir, ce commentateur me les broute menu-menu. Ses arguments sont tellement nuls ("<cite>Si BlueGriffon était financé par Mozilla on ne serait pas en train de parler de tout ça</cite>" et si ma tante en avait...) que j'en ai franchement ras-le-bol d'offrir une tribune à cette personne ; je ferme donc les commentaires sur cet article mais je laisse sa prose, elle fera date...</p>
|
|
|
318 </blockquote>
|
|
|
319
|
|
|
320 <p>Tout d'abord je tiens à faire remarquer que j'ai passé pas mal de temps à rédiger mes commentaires or la majorité de mes propos n'a pas eu de réponse, par exemple ma question dans mon dernier commentaire sur la fiabilité du modèle économique choisi :</p>
|
|
|
321
|
|
|
322 <blockquote>
|
|
|
323 <p>je ne vois pas en quoi le modèle économique de la vente d'extensions propriétaires serait sûr. Par exemple si la communauté développe les mêmes en libre que ferez-vous ? La course aux fonctionnalités ?</p>
|
|
|
324 </blockquote>
|
|
|
325
|
|
|
326 <p>Enfin, et c'est la motivation première de ce billet, je tiens à dénoncer cette pratique de la fermeture des commentaires totalement contraire à la liberté d'expression, il y a des façons plus civilisées de clore un débat, qu'il soit <em>trollesque</em> ou non.</p>
|
|
|
327
|
|
|
328 <p><a id="note1" href="http://changaco.net/blog/#note1_c1">↑</a> <strong>Édit :</strong> on me rétorque que les commentaires sont fermés automatiquement aux bouts de 3 jours sur le Standblog. À cela je réponds deux choses :</p>
|
|
|
329
|
|
|
330 <ul>
|
|
|
331 <li>je ne vois aucune mention de ça sur ledit blog, il me semble que la moindre des choses serait de le signaler</li>
|
|
|
332 <li>je suis autant en désaccord avec cette pratique qu'avec la fermeture manuelle</li>
|
|
|
333 </ul>
|
|
|
334
|
|
|
335 </content>
|
|
|
336
|
|
|
337
|
|
|
338 <link rel="comments" href="/blog/Réponse_à_Daniel_Glazman/#comments" type="text/html" />
|
|
|
339
|
|
|
340
|
|
|
341 <link rel="comments" href="/blog/Réponse_à_Daniel_Glazman/comments.atom" type="application/atom+xml" />
|
|
|
342
|
|
|
343 </entry>
|
|
|
344 <entry>
|
|
|
345 <title>About this blog</title>
|
|
|
346
|
|
|
347 <id>http://changaco.net/blog/About_this_blog/</id>
|
|
|
348
|
|
|
349 <link href="http://changaco.net/blog/About_this_blog/"/>
|
|
|
350
|
|
|
351
|
|
|
352
|
|
|
353
|
|
|
354
|
|
|
355
|
|
|
356 <category term="tags/clevercss" />
|
|
|
357
|
|
|
358 <category term="tags/css3" />
|
|
|
359
|
|
|
360 <category term="tags/html5" />
|
|
|
361
|
|
|
362 <category term="tags/ikiwiki" />
|
|
|
363
|
|
|
364
|
|
|
365 <updated>2011-12-10T13:52:20Z</updated>
|
|
|
366 <published>2010-05-16T20:49:20Z</published>
|
|
|
367
|
|
|
368 <content type="html" xml:lang="en">
|
|
|
369 <p>This site is powered by <a href="http://ikiwiki.info">Ikiwiki</a>. It took me a while to set it up and I have some things to share.</p>
|
|
|
370
|
|
|
371 <p>Firstly :</p>
|
|
|
372
|
|
|
373 <ul>
|
|
|
374 <li><a href="http://changaco.net/blog/../templates/">templates</a> that use HTML5</li>
|
|
|
375 <li><a href="http://changaco.net/blog/../code/s2p2/">s2p2</a>, a bash script that pre-processes JavaScript and ( Clever ) CSS</li>
|
|
|
376 </ul>
|
|
|
377
|
|
|
378 <p>About <a href="http://changaco.net/blog/../style/">style sheets</a> :</p>
|
|
|
379
|
|
|
380 <ul>
|
|
|
381 <li>there is quite some of CSS3, like selectors and flexible box model</li>
|
|
|
382 <li>the biggest part is written in <a href="http://sandbox.pocoo.org/clevercss/">Clever CSS</a></li>
|
|
|
383 </ul>
|
|
|
384
|
|
|
385 <p>For Clever CSS, a <a href="http://changaco.net/blog/../code/ccss.xml">ccss syntax file</a> for <a href="http://kate-editor.org/">kate</a>.</p>
|
|
|
386
|
|
|
387 <p>Concerning <a href="http://changaco.net/blog/../script/">JavaScript</a> :</p>
|
|
|
388
|
|
|
389 <ul>
|
|
|
390 <li>I got rid of the default ikiwiki.js as I don't support old browsers</li>
|
|
|
391 <li><a href="http://changaco.net/blog/../code/chtml/">chtml</a> creates real elements from HTML code contained in comments of the form <code>&lt;!--(CHTML) ... --&gt;</code></li>
|
|
|
392 </ul>
|
|
|
393
|
|
|
394 <p>Everything has been written with technologies supported by the current versions of Firefox and Chromium as of April 2010. A conditional comment hides scripts and styles from all versions of IE. If you are using an up-to-date free browser and you encounter a problem send me a mail or even better a patch, I'll see what I can do.</p>
|
|
|
395
|
|
|
396 <h2 id="aboutcomments">About comments</h2>
|
|
|
397
|
|
|
398 <p>After a lot of thinking and some debate I decided to enable pseudo-anonymous comments only ( you can put a nickname and a website ). This means no OpenID and no user registration.</p>
|
|
|
399
|
|
|
400 <p>I'll try to talk about that in a future post on Internet Identity.</p>
|
|
|
401
|
|
|
402 <h2 id="criticsofikiwiki">Critics of ikiwiki</h2>
|
|
|
403
|
|
|
404 <ul>
|
|
|
405 <li>Perl sux</li>
|
|
|
406 <li>I couldn't find a good way to build a site from multiple repositories</li>
|
|
|
407 <li>no threaded comments</li>
|
|
|
408 <li>discussion pages as crappy as traditional MediaWiki ones ( maybe even more )</li>
|
|
|
409 </ul>
|
|
|
410
|
|
|
411 </content>
|
|
|
412
|
|
|
413
|
|
|
414 <link rel="comments" href="/blog/About_this_blog/#comments" type="text/html" />
|
|
|
415
|
|
|
416
|
|
|
417 <link rel="comments" href="/blog/About_this_blog/comments.atom" type="application/atom+xml" />
|
|
|
418
|
|
|
419 </entry>
|
|
|
420
|
|
|
421 </feed>
|
