free
/
freedombone
Tarkkaile 1
Äänestä 0
Fork 0
Koodi Ongelmat 0 Pull-pyynnöt 0 Julkaisut 0 Wiki Activity
Selaa lähdekoodia

Why is the Pi not supported?

Bob Mottram 9 vuotta sitten
vanhempi
a7a86a3703
commit
2c211a009e
2 muutettua tiedostoa jossa 110 lisäystä ja 79 poistoa
Jaettu näkymä Näytä diff tilastot
  1. 5
    0
      doc/EN/faq.org
  2. 105
    79
      website/EN/faq.html

+ 5
- 0
doc/EN/faq.org Näytä tiedosto 

@@ -19,6 +19,7 @@
19 19 
 #+BEGIN_CENTER
20 20 
 #+ATTR_HTML: :border -1
21 21 
 | [[I don't have a static IP address. Can I still install this system?]]            |
22 
+| [[Why not support building images for Raspberry Pi?]]                             |
22 23 
 | [[Why use Github?]]                                                               |
23 24 
 | [[Why can't I access my .onion site with a Tor browser?]]                         |
24 25 
 | [[What is the best hardware to run this system on?]]                              |
 
@@ -42,6 +43,10 @@
42 43 
 Yes. The minimum requirements are to have some hardware that you can install Debian onto and also that you have administrator access to your internet router so that you can forward ports to the system which has Freedombone installed.
43 44
44 45 
 The lack of a static IP address can be worked around by using a dynamic DNS service. Freedombone uses [[http://troglobit.com/inadyn.html][inadyn]], which supports a variety of dynamic DNS providers.
46 
+* Why not support building images for Raspberry Pi?
47 
+The FreedomBox project supports Raspberry Pi builds, and the image build system for Freedombone is based on the same system. However, although the Raspberry Pi can run a version of Debian it requires a closed proprietary blob in order to boot the hardware. Who knows what that blob might contain or what exploits it could facilitate. From an adversarial point of view if you were trying to deliver "bulk equipment interference" then it doesn't get any better than piggybacking on something which has control of the boot process, and hence all subsequently run processes.
48 
+
49 
+So although the Raspberry Pi is cheap and hugely popular it's not supported by the Freedombone project. Perhaps future versions of the Pi won't have the proprietary blob requirement, or maybe the blob will be open sourced at some stage.
45 50 
 * Why use Github?
46 51 
 Github is paradoxically a centralized, closed and proprietary system which happens to mostly host free and open source projects. Up until now it has been relatively benign, but at some point in the name of "growth" it will likely start becoming more evil, or just become like SourceForge - which was also once much loved by FOSS developers, but turned into a den of malvertizing.
47 52

+ 105
- 79
website/EN/faq.html Näytä tiedosto 

@@ -3,15 +3,15 @@
3 3 
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4 4 
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5 5 
 <head>
6 
-<!-- 2016-01-17 Sun 13:21 -->
7 
-<meta  http-equiv="Content-Type" content="text/html;charset=utf-8" />
8 
-<meta  name="viewport" content="width=device-width, initial-scale=1" />
6 
+<!-- 2016-01-31 Sun 20:25 -->
7 
+<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
8 
+<meta name="viewport" content="width=device-width, initial-scale=1" />
9 9 
 <title></title>
10 
-<meta  name="generator" content="Org-mode" />
11 
-<meta  name="author" content="Bob Mottram" />
12 
-<meta  name="description" content="Turn the Beaglebone Black into a personal communications server"
10 
+<meta name="generator" content="Org-mode" />
11 
+<meta name="author" content="Bob Mottram" />
12 
+<meta name="description" content="Turn the Beaglebone Black into a personal communications server"
13 13 
  />
14 
-<meta  name="keywords" content="freedombox, debian, beaglebone, hubzilla, email, web server, home server, internet, censorship, surveillance, social network, irc, jabber" />
14 
+<meta name="keywords" content="freedombox, debian, beaglebone, hubzilla, email, web server, home server, internet, censorship, surveillance, social network, irc, jabber" />
15 15 
 <style type="text/css">
16 16 
  <!--/*--><![CDATA[/*><!--*/
17 17 
   .title  { text-align: center;
 
@@ -158,9 +158,14 @@ for the JavaScript code in this tag.
158 158 
 </div>
159 159 
 </div>
160 160
161 
-<center>
162 
-<h1>Frequently Asked Questions</h1>
163 
-</center>
161 
+<div class="HTML">
162 
+<p>
163 
+&lt;center&gt;
164 
+&lt;h1&gt;Frequently Asked Questions&lt;/h1&gt;
165 
+&lt;/center&gt;
166 
+</p>
167 
+
168 
+</div>
164 169
165 170 
 <div class="org-center">
166 171 
 <table border="-1" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
 
@@ -175,71 +180,75 @@ for the JavaScript code in this tag.
175 180 
 </tr>
176 181
177 182 
 <tr>
178 
-<td class="org-left"><a href="#orgheadline2">Why use Github?</a></td>
183 
+<td class="org-left"><a href="#orgheadline2">Why not support building images for Raspberry Pi?</a></td>
179 184 
 </tr>
180 185
181 186 
 <tr>
182 
-<td class="org-left"><a href="#orgheadline3">Why can't I access my .onion site with a Tor browser?</a></td>
187 
+<td class="org-left"><a href="#orgheadline3">Why use Github?</a></td>
183 188 
 </tr>
184 189
185 190 
 <tr>
186 
-<td class="org-left"><a href="#orgheadline4">What is the best hardware to run this system on?</a></td>
191 
+<td class="org-left"><a href="#orgheadline4">Why can't I access my .onion site with a Tor browser?</a></td>
187 192 
 </tr>
188 193
189 194 
 <tr>
190 
-<td class="org-left"><a href="#orgheadline5">Can I add more users to the system?</a></td>
195 
+<td class="org-left"><a href="#orgheadline5">What is the best hardware to run this system on?</a></td>
191 196 
 </tr>
192 197
193 198 
 <tr>
194 
-<td class="org-left"><a href="#orgheadline6">How do I remove a user from the system?</a></td>
199 
+<td class="org-left"><a href="#orgheadline6">Can I add more users to the system?</a></td>
195 200 
 </tr>
196 201
197 202 
 <tr>
198 
-<td class="org-left"><a href="#orgheadline7">How do I reset the tripwire?</a></td>
203 
+<td class="org-left"><a href="#orgheadline7">How do I remove a user from the system?</a></td>
199 204 
 </tr>
200 205
201 206 
 <tr>
202 
-<td class="org-left"><a href="#orgheadline8">Is metadata protected?</a></td>
207 
+<td class="org-left"><a href="#orgheadline8">How do I reset the tripwire?</a></td>
203 208 
 </tr>
204 209
205 210 
 <tr>
206 
-<td class="org-left"><a href="#orgheadline9">How do I create email processing rules?</a></td>
211 
+<td class="org-left"><a href="#orgheadline9">Is metadata protected?</a></td>
207 212 
 </tr>
208 213
209 214 
 <tr>
210 
-<td class="org-left"><a href="#orgheadline10">Why isn't dynamic DNS working?</a></td>
215 
+<td class="org-left"><a href="#orgheadline10">How do I create email processing rules?</a></td>
211 216 
 </tr>
212 217
213 218 
 <tr>
214 
-<td class="org-left"><a href="#orgheadline11">How do I change my encryption settings?</a></td>
219 
+<td class="org-left"><a href="#orgheadline11">Why isn't dynamic DNS working?</a></td>
215 220 
 </tr>
216 221
217 222 
 <tr>
218 
-<td class="org-left"><a href="#orgheadline12">How do I get a domain name?</a></td>
223 
+<td class="org-left"><a href="#orgheadline12">How do I change my encryption settings?</a></td>
219 224 
 </tr>
220 225
221 226 
 <tr>
222 
-<td class="org-left"><a href="#orgheadline13">How do I get a "real" SSL/TLS/HTTPS certificate?</a></td>
227 
+<td class="org-left"><a href="#orgheadline13">How do I get a domain name?</a></td>
223 228 
 </tr>
224 229
225 230 
 <tr>
226 
-<td class="org-left"><a href="#orgheadline14">How do I renew a Let's Encrypt certificate?</a></td>
231 
+<td class="org-left"><a href="#orgheadline14">How do I get a "real" SSL/TLS/HTTPS certificate?</a></td>
227 232 
 </tr>
228 233
229 234 
 <tr>
230 
-<td class="org-left"><a href="#orgheadline15">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</a></td>
235 
+<td class="org-left"><a href="#orgheadline15">How do I renew a Let's Encrypt certificate?</a></td>
231 236 
 </tr>
232 237
233 238 
 <tr>
234 
-<td class="org-left"><a href="#orgheadline16">Why use self-signed certificates?</a></td>
239 
+<td class="org-left"><a href="#orgheadline16">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</a></td>
235 240 
 </tr>
236 241
237 242 
 <tr>
238 
-<td class="org-left"><a href="#orgheadline17">Why not use the services of $company instead? They took the Seppuku pledge</a></td>
243 
+<td class="org-left"><a href="#orgheadline17">Why use self-signed certificates?</a></td>
239 244 
 </tr>
240 245
241 246 
 <tr>
242 
-<td class="org-left"><a href="#orgheadline18">Why does my email keep getting rejected as spam by Gmail/etc?</a></td>
247 
+<td class="org-left"><a href="#orgheadline18">Why not use the services of $company instead? They took the Seppuku pledge</a></td>
248 
+</tr>
249 
+
250 
+<tr>
251 
+<td class="org-left"><a href="#orgheadline19">Why does my email keep getting rejected as spam by Gmail/etc?</a></td>
243 252 
 </tr>
244 253 
 </tbody>
245 254 
 </table>
 
@@ -258,9 +267,21 @@ The lack of a static IP address can be worked around by using a dynamic DNS serv
258 267 
 </div>
259 268 
 </div>
260 269 
 <div id="outline-container-orgheadline2" class="outline-2">
261 
-<h2 id="orgheadline2">Why use Github?</h2>
270 
+<h2 id="orgheadline2">Why not support building images for Raspberry Pi?</h2>
262 271 
 <div class="outline-text-2" id="text-orgheadline2">
263 272 
 <p>
273 
+The FreedomBox project supports Raspberry Pi builds, and the image build system for Freedombone is based on the same system. However, although the Raspberry Pi can run a version of Debian it requires a closed proprietary blob in order to boot the hardware. Who knows what that blob might contain or what exploits it could facilitate. From an adversarial point of view if you were trying to deliver "bulk equipment interference" then it doesn't get any better than piggybacking on something which has control of the boot process, and hence all subsequently run processes.
274 
+</p>
275 
+
276 
+<p>
277 
+So although the Raspberry Pi is cheap and hugely popular it's not supported by the Freedombone project. Perhaps future versions of the Pi won't have the proprietary blob requirement, or maybe the blob will be open sourced at some stage.
278 
+</p>
279 
+</div>
280 
+</div>
281 
+<div id="outline-container-orgheadline3" class="outline-2">
282 
+<h2 id="orgheadline3">Why use Github?</h2>
283 
+<div class="outline-text-2" id="text-orgheadline3">
284 
+<p>
264 285 
 Github is paradoxically a centralized, closed and proprietary system which happens to mostly host free and open source projects. Up until now it has been relatively benign, but at some point in the name of "growth" it will likely start becoming more evil, or just become like SourceForge - which was also once much loved by FOSS developers, but turned into a den of malvertizing.
265 286 
 </p>
266 287 
 
@@ -273,17 +294,17 @@ The source code for this project is experimentally independently hosted, and it
273 294 
 </p>
274 295 
 </div>
275 296 
 </div>
276 
-<div id="outline-container-orgheadline3" class="outline-2">
277 
-<h2 id="orgheadline3">Why can't I access my .onion site with a Tor browser?</h2>
278 
-<div class="outline-text-2" id="text-orgheadline3">
297 
+<div id="outline-container-orgheadline4" class="outline-2">
298 
+<h2 id="orgheadline4">Why can't I access my .onion site with a Tor browser?</h2>
299 
+<div class="outline-text-2" id="text-orgheadline4">
279 300 
 <p>
280 301 
 By default the Tor browser has <a href="https://www.eff.org/HTTPS-everywhere">https everywhere</a> enabled and this can clash with onion addresses. Really this is a browser bug, which ought to be fixed. If you notice that "https" has been automatically prepended to your onion address then go to the https everywhere settings and disable it. https isn't needed for ontion sites since onion services already have their own public key encryption (the onion address is the public key).
281 302 
 </p>
282 303 
 </div>
283 304 
 </div>
284 
-<div id="outline-container-orgheadline4" class="outline-2">
285 
-<h2 id="orgheadline4">What is the best hardware to run this system on?</h2>
286 
-<div class="outline-text-2" id="text-orgheadline4">
305 
+<div id="outline-container-orgheadline5" class="outline-2">
306 
+<h2 id="orgheadline5">What is the best hardware to run this system on?</h2>
307 
+<div class="outline-text-2" id="text-orgheadline5">
287 308 
 <p>
288 309 
 It was originally designed to run on the Beaglebone Black, but that should be regarded as the most minimal system, because it's single core and has by today's standards a small amount of memory. Obviously the more powerful the hardware is the faster things like web pages (blog, social networking, etc) will be served but the more electricity such a system will require if you're running it 24/7. A good compromise between performance and energy consumption is something like an old netbook. The battery of an old netbook or laptop even gives you <a href="https://en.wikipedia.org/wiki/Uninterruptible_power_supply">UPS capability</a> to keep the system going during brief power outages or cable re-arrangements, and that means using full disk encryption on the server also becomes more practical.
289 310 
 </p>
 
@@ -293,9 +314,9 @@ It was originally designed to run on the Beaglebone Black, but that should be re
293 314 
 </p>
294 315 
 </div>
295 316 
 </div>
296 
-<div id="outline-container-orgheadline5" class="outline-2">
297 
-<h2 id="orgheadline5">Can I add more users to the system?</h2>
298 
-<div class="outline-text-2" id="text-orgheadline5">
317 
+<div id="outline-container-orgheadline6" class="outline-2">
318 
+<h2 id="orgheadline6">Can I add more users to the system?</h2>
319 
+<div class="outline-text-2" id="text-orgheadline6">
299 320 
 <p>
300 321 
 Yes. Freedombone can support a small number of users, for a "<i>friends and family</i>" type of home installation. This gives them access to an email account, XMPP, SIP phone and the blog (depending on whether the variant which you installed includes those).
301 322 
 </p>
 
@@ -320,9 +341,9 @@ Another point is that Freedombone installations are not intended to support many
320 341 
 </p>
321 342 
 </div>
322 343 
 </div>
323 
-<div id="outline-container-orgheadline6" class="outline-2">
324 
-<h2 id="orgheadline6">How do I remove a user from the system?</h2>
325 
-<div class="outline-text-2" id="text-orgheadline6">
344 
+<div id="outline-container-orgheadline7" class="outline-2">
345 
+<h2 id="orgheadline7">How do I remove a user from the system?</h2>
346 
+<div class="outline-text-2" id="text-orgheadline7">
326 347 
 <p>
327 348 
 To remove a user:
328 349 
 </p>
 
@@ -339,9 +360,9 @@ Select <i>Manage Users</i> and then <i>Delete a user</i>. Note that this will de
339 360 
 </p>
340 361 
 </div>
341 362 
 </div>
342 
-<div id="outline-container-orgheadline7" class="outline-2">
343 
-<h2 id="orgheadline7">How do I reset the tripwire?</h2>
344 
-<div class="outline-text-2" id="text-orgheadline7">
363 
+<div id="outline-container-orgheadline8" class="outline-2">
364 
+<h2 id="orgheadline8">How do I reset the tripwire?</h2>
365 
+<div class="outline-text-2" id="text-orgheadline8">
345 366 
 <p>
346 367 
 The tripwire will be automatically reset once per week. If you want to reset it earlier then do the following:
347 368 
 </p>
 
@@ -358,17 +379,17 @@ Select "reset tripwire" using cursors and space bar then enter.
358 379 
 </p>
359 380 
 </div>
360 381 
 </div>
361 
-<div id="outline-container-orgheadline8" class="outline-2">
362 
-<h2 id="orgheadline8">Is metadata protected?</h2>
363 
-<div class="outline-text-2" id="text-orgheadline8">
382 
+<div id="outline-container-orgheadline9" class="outline-2">
383 
+<h2 id="orgheadline9">Is metadata protected?</h2>
384 
+<div class="outline-text-2" id="text-orgheadline9">
364 385 
 <p>
365 386 
 Even when using Freedombone metadata analysis by third parties is still possible. This can be mitigated by accessing your blog, or other web services, via their <i>onion addresses</i>, rather than via more conventional domain names. In that case your ISP and any government which they might be compelled to report back to will know when your system is being accessed, but not necessarily <i>which</i> services are being accessed <i>or by whom</i>. So for instance using a Tor browser and the onion address people may be able to safely read your blog or wiki and be reasonably confident that metadata isn't being gathered about what they read (or more concisely the metadata which can be gathered by a third party may just not be very useful or personally identifiable). On the other hand if you access the system via conventional domain names and dynamic DNS then it's safe to assume that metadata can and will be collected by third parties.
366 387 
 </p>
367 388 
 </div>
368 389 
 </div>
369 
-<div id="outline-container-orgheadline9" class="outline-2">
370 
-<h2 id="orgheadline9">How do I create email processing rules?</h2>
371 
-<div class="outline-text-2" id="text-orgheadline9">
390 
+<div id="outline-container-orgheadline10" class="outline-2">
391 
+<h2 id="orgheadline10">How do I create email processing rules?</h2>
392 
+<div class="outline-text-2" id="text-orgheadline10">
372 393 
 <div class="org-src-container">
373 394
374 395 
 <pre class="src src-bash">ssh username@domainname -p 2222
 
@@ -426,9 +447,9 @@ Spamassassin is also available and within Mutt you can use the S (shift+s) key t
426 447 
 </p>
427 448 
 </div>
428 449 
 </div>
429 
-<div id="outline-container-orgheadline10" class="outline-2">
430 
-<h2 id="orgheadline10">Why isn't dynamic DNS working?</h2>
431 
-<div class="outline-text-2" id="text-orgheadline10">
450 
+<div id="outline-container-orgheadline11" class="outline-2">
451 
+<h2 id="orgheadline11">Why isn't dynamic DNS working?</h2>
452 
+<div class="outline-text-2" id="text-orgheadline11">
432 453 
 <p>
433 454 
 If you run the command:
434 455 
 </p>
 
@@ -496,9 +517,9 @@ http://httpbin.org/ip
496 517 
 </div>
497 518 
 </div>
498 519
499 
-<div id="outline-container-orgheadline11" class="outline-2">
500 
-<h2 id="orgheadline11">How do I change my encryption settings?</h2>
501 
-<div class="outline-text-2" id="text-orgheadline11">
520 
+<div id="outline-container-orgheadline12" class="outline-2">
521 
+<h2 id="orgheadline12">How do I change my encryption settings?</h2>
522 
+<div class="outline-text-2" id="text-orgheadline12">
502 523 
 <p>
503 524 
 Suppose that some new encryption vulnerability has been announced and that you need to change your encryption settings. Maybe an algorithm thought to be secure is now no longer so and you need to remove it. You can change your settings by doing the following:
504 525 
 </p>
 
@@ -515,9 +536,9 @@ Then select <i>Security Settings</i>. You will then be able to edit the crypto s
515 536 
 </p>
516 537 
 </div>
517 538 
 </div>
518 
-<div id="outline-container-orgheadline12" class="outline-2">
519 
-<h2 id="orgheadline12">How do I get a domain name?</h2>
520 
-<div class="outline-text-2" id="text-orgheadline12">
539 
+<div id="outline-container-orgheadline13" class="outline-2">
540 
+<h2 id="orgheadline13">How do I get a domain name?</h2>
541 
+<div class="outline-text-2" id="text-orgheadline13">
521 542 
 <p>
522 543 
 Suppose that you have bought a domain name (rather than using a free subdomain on freedns) and you want to use that instead.
523 544 
 </p>
 
@@ -585,9 +606,9 @@ You should now be able to send an email from <i>postmaster@mynewdomainname</i> a
585 606 
 </div>
586 607 
 </div>
587 608
588 
-<div id="outline-container-orgheadline13" class="outline-2">
589 
-<h2 id="orgheadline13">How do I get a "real" SSL/TLS/HTTPS certificate?</h2>
590 
-<div class="outline-text-2" id="text-orgheadline13">
609 
+<div id="outline-container-orgheadline14" class="outline-2">
610 
+<h2 id="orgheadline14">How do I get a "real" SSL/TLS/HTTPS certificate?</h2>
611 
+<div class="outline-text-2" id="text-orgheadline14">
591 612 
 <p>
592 613 
 If you did the full install or selected the social variant then the system will have tried to obtain a Let's Encrypt certificate automatically during the install process. If this failed for any reason, or if you have created a new site which you need a certificate for then do the following:
593 614 
 </p>
 
@@ -608,9 +629,9 @@ One thing to be aware of is that Let's Encrypt doesn't support many dynamic DNS
608 629 
 </p>
609 630 
 </div>
610 631 
 </div>
611 
-<div id="outline-container-orgheadline14" class="outline-2">
612 
-<h2 id="orgheadline14">How do I renew a Let's Encrypt certificate?</h2>
613 
-<div class="outline-text-2" id="text-orgheadline14">
632 
+<div id="outline-container-orgheadline15" class="outline-2">
633 
+<h2 id="orgheadline15">How do I renew a Let's Encrypt certificate?</h2>
634 
+<div class="outline-text-2" id="text-orgheadline15">
614 635 
 <p>
615 636 
 Normally certificates will be automatically renewed once per month, so you don't need to be concerned about it. If anything goes wrong with the automatic renewal then you should receive a warning email.
616 637 
 </p>
 
@@ -631,9 +652,9 @@ Select <b>Security settings</b> then <b>Renew Let's Encrypt certificate</b>.
631 652 
 </p>
632 653 
 </div>
633 654 
 </div>
634 
-<div id="outline-container-orgheadline15" class="outline-2">
635 
-<h2 id="orgheadline15">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</h2>
636 
-<div class="outline-text-2" id="text-orgheadline15">
655 
+<div id="outline-container-orgheadline16" class="outline-2">
656 
+<h2 id="orgheadline16">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</h2>
657 
+<div class="outline-text-2" id="text-orgheadline16">
637 658 
 <p>
638 659 
 Most likely it's because Let's Encrypt doesn't support your particular domain or subdomain. Currently free subdomains tend not to work. You'll need to buy a domain name, link it to your dynamic DNS account and then do:
639 660 
 </p>
 
@@ -650,9 +671,9 @@ Select <b>Security settings</b> then <b>Create a new Let's Encrypt certificate</
650 671 
 </p>
651 672 
 </div>
652 673 
 </div>
653 
-<div id="outline-container-orgheadline16" class="outline-2">
654 
-<h2 id="orgheadline16">Why use self-signed certificates?</h2>
655 
-<div class="outline-text-2" id="text-orgheadline16">
674 
+<div id="outline-container-orgheadline17" class="outline-2">
675 
+<h2 id="orgheadline17">Why use self-signed certificates?</h2>
676 
+<div class="outline-text-2" id="text-orgheadline17">
656 677 
 <p>
657 678 
 Almost everywhere on the web you will read that self-signed certificates are worthless. They bring up <i>scary-scary looking</i> browser warnings and gurus will advise you not to use them. Self-signed certificates are quite useful though. What the scary warnings mean - and it would be good if they explained this more clearly - is that you have an encrypted connection established but there is <i>no certainty about who that connection is with</i>.
658 679 
 </p>
 
@@ -674,17 +695,17 @@ For now a self-signed certificate will probably in most cases protect your commu
674 695 
 </p>
675 696 
 </div>
676 697 
 </div>
677 
-<div id="outline-container-orgheadline17" class="outline-2">
678 
-<h2 id="orgheadline17">Why not use the services of $company instead? They took the Seppuku pledge</h2>
679 
-<div class="outline-text-2" id="text-orgheadline17">
698 
+<div id="outline-container-orgheadline18" class="outline-2">
699 
+<h2 id="orgheadline18">Why not use the services of $company instead? They took the Seppuku pledge</h2>
700 
+<div class="outline-text-2" id="text-orgheadline18">
680 701 
 <p>
681 702 
 <a href="http://seppuku.cryptostorm.org/">That pledge</a> is utterly worthless. Years ago people trusted Google in the same sort of way, because they promised not be be evil and because a lot of the engineers working for them seemed like honest types who were "<i>on our side</i>". Post-<a href="https://en.wikipedia.org/wiki/Nymwars">nymwars</a> and post-<a href="https://en.wikipedia.org/wiki/PRISM_(surveillance_program)">PRISM</a> we know exactly how much Google cared about the privacy and security of its users. But Google is only one particular example. In general don't trust pledges made by companies, even if the people running them seem really sincere.
682 703 
 </p>
683 704 
 </div>
684 705 
 </div>
685 
-<div id="outline-container-orgheadline18" class="outline-2">
686 
-<h2 id="orgheadline18">Why does my email keep getting rejected as spam by Gmail/etc?</h2>
687 
-<div class="outline-text-2" id="text-orgheadline18">
706 
+<div id="outline-container-orgheadline19" class="outline-2">
707 
+<h2 id="orgheadline19">Why does my email keep getting rejected as spam by Gmail/etc?</h2>
708 
+<div class="outline-text-2" id="text-orgheadline19">
688 709 
 <p>
689 710 
 Welcome to the world of email. Email is really the archetypal decentralized service, developed during the early days of the internet. In principle anyone can run an email server, and that's exactly what you're doing with Freedombone. Email is very useful, but it has a big problem, and that's that the protocols are totally insecure. That made it easy for spammers to do their thing, and in response highly elaborate spam filtering and blocking systems were developed. Chances are that your emails are being blocked in this way. Sometimes the blocking is so indisciminate that entire countries are excluded. What can you do about it? Unless you control the block list at the receiving end probably you can't do anything. There is zero accountability for such blocking, and you can't just contact someone and say "hey, I'm not a spammer". This system works well for the big internet companies because it effectively centralises email to a few well-known brand names and keeps any independent servers out.
690 711 
 </p>
 
@@ -693,9 +714,14 @@ Welcome to the world of email. Email is really the archetypal decentralized serv
693 714 
 So the situation with email presently is pretty bad, and there's a clear selection pressure against decentralization and towards only a few companies controlling all email services. Longer term the solution is to have more secure protocols which make spamming hard or expensive. Bitmessage is one such system. As an immediate practical workaround you could try buying a domain name and then linking it to your dynamic DNS account (freeDNS, etc) in the hope that the blocking is against dynamic DNS domain names, but there is no guarantee that will work and often blocking may be based upon IP address ranges about which there is little you can do.
694 715 
 </p>
695 716
696 
-<center>
697 
-Return to the <a href="index.html">home page</a>
698 
-</center>
717 
+<div class="HTML">
718 
+<p>
719 
+&lt;center&gt;
720 
+Return to the &lt;a href="index.html"&gt;home page&lt;/a&gt;
721 
+&lt;/center&gt;
722 
+</p>
723 
+
724 
+</div>
699 725 
 </div>
700 726 
 </div>
701 727 
 </div>