csh
/
y.st.
forked from y.st./y.st.


			
				
					
						
						
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154
							<?xml version="1.0" encoding="utf-8"?>
<!--
                                                                                     
 h       t     t                ::       /     /                     t             / 
 h       t     t                ::      //    //                     t            // 
 h     ttttt ttttt ppppp sssss         //    //  y   y       sssss ttttt         //  
 hhhh    t     t   p   p s            //    //   y   y       s       t          //   
 h  hh   t     t   ppppp sssss       //    //    yyyyy       sssss   t         //    
 h   h   t     t   p         s  ::   /     /         y  ..       s   t    ..   /     
 h   h   t     t   p     sssss  ::   /     /     yyyyy  ..   sssss   t    ..   /     
                                                                                     
	<https://y.st./>
	Copyright © 2015 Alex Yst <mailto:copyright@y.st>

	This program is free software: you can redistribute it and/or modify
	it under the terms of the GNU General Public License as published by
	the Free Software Foundation, either version 3 of the License, or
	(at your option) any later version.

	This program is distributed in the hope that it will be useful,
	but WITHOUT ANY WARRANTY; without even the implied warranty of
	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
	GNU General Public License for more details.

	You should have received a copy of the GNU General Public License
	along with this program. If not, see <https://www.gnu.org./licenses/>.
-->
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<base href="https://y.st./en/weblog/2015/12-December/02.xhtml" />
		<title>Endless loops, Facebook policies, and a letter from our ISP &lt;https://y.st./en/weblog/2015/12-December/02.xhtml&gt;</title>
		<link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png" />
		<link rel="stylesheet" type="text/css" href="/link/basic.css" />
		<link rel="stylesheet" type="text/css" href="/link/site-specific.css" />
		<script type="text/javascript" src="/script/javascript.js" />
		<meta name="viewport" content="width=device-width" />
	</head>
	<body>
		<nav>
			<p>
				<a href="/en/">Home</a> |
				<a href="/en/a/about.xhtml">About</a> |
				<a href="/en/a/contact.xhtml">Contact</a> |
				<a href="/a/canary.txt">Canary</a> |
				<a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
				<a href="/en/opinion/">Opinions</a> |
				<a href="/en/coursework/">Coursework</a> |
				<a href="/en/law/">Law</a> |
				<a href="/en/a/links.xhtml">Links</a> |
				<a href="/en/weblog/2015/12-December/02.xhtml.asc">{this page}.asc</a>
			</p>
			<hr/>
			<p>
				Weblog index:
				<a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
				<a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
				<a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
			</p>
			<hr/>
			<p>
				Jump to entry:
				<a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
				<a rel="prev" href="/en/weblog/2015/12-December/01.xhtml">&lt;Previous</a>
				<a rel="next" href="/en/weblog/2015/12-December/03.xhtml">Next&gt;</a>
				<a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
			</p>
			<hr/>
		</nav>
		<header>
			<h1>Endless loops, Facebook policies, and a letter from our <abbr title="Internet service provider">ISP</abbr></h1>
			<p>Day 00270: Wednesday, 2015 December 02</p>
		</header>
<p>
	Last night, I could not get this website to compile.
	It seemed to be caught in an endless loop somewhere in one of the scripts.
	It seemed to somehow be tied to yesterday&apos;s weblog entry file, though it did not contain any loops or call any functions that do.
	This morning, I had time to actually sit down and debug, and it seems that the issue was not caused by any of the content of yesterday&apos;s weblog entry file, but rather by its presence.
	The script used to build the weblog index pages calls <code>\st\y\calendar()</code>, a looping function, in order to build the <abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars with the hyperlinks to individual entry pages.
	The function stops looping when it comes to the end of a week in which the next week is part of a month that is of a higher month number than the intended month.
	This was meant to make the function terminate when reaching the next month, but caused a glitch when dealing with the month of December.
	<abbr title="PHP: Hypertext Preprocessor">PHP</abbr> treats December as month twelve and January as month one, so for the loop to terminate, the loop would need to reach the nonexistent month number thirteen.
	I speculate that this same issue may have caused a bug in <abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars representing January as well, causing the loop to terminate prematurely due to the preceding month having a higher month number than the intended month.
	I have now corrected the bug by having the function take into account both the month and the year when deciding when to terminate.
</p>
<p>
	Speaking of the calendar pages, the script that I use to build them will need to be adjusted next month.
	When I built it, I set it up to use the page at &quot;/weblog/2015/&quot; as the main index page knowing that come 2016, I would want to create a more inclusive index at &quot;/weblog/&quot;.
	I later moved the weblog index to <a href="/en/weblog/2015/">&quot;/en/weblog/2015/&quot;</a> when I moved everything to to &quot;/en/&quot;, but the plans for a more inclusive index have not changed.
</p>
<p>
	Even once I had my SRV records set correctly, <a href="https://hosted.im/">Hosted.IM</a> was still having trouble seeing that they resolved to the addresses that they wanted them to.
	It has been several days now though, so they have cleared out the stale records from their system and performed a fresh query.
	I am now available over <a href="xmpp:y@y.st"><abbr title="Extensible Messaging and Presence Protocol">XMPP</abbr></a> for anyone that would like to contact me that way.
</p>
<p>
	I applied for work at the local convenience store.
	My mother would not like if I went to work there, but I am running out of options and there is no harm in applying.
	If I get the interview and they end up wanting to hire me, I will discuss it with her and and decide whether or not to take the position.
	After registering an account with the convenience store job website, they sent me a link to register for some sort of Employer collective.
	I do not know how effective this was though, there seem to be no login credentials associated with the accounts there, so I cannot check on the status of my application.
</p>
<p>
	<a href="https://wowana.me/">Wowaname</a> told me today that Facebook&apos;s policies regarding legal names have changed recently, saying that they now make exceptions.
	However, when I asked about it, she said that to get an exception, you must first go against the policy, then get caught and make an appeal explaining why you did not use your legal name on your Facebook account.
	This is not good enough; one must be allowed to create an account under their preferred name instead of their legal name, knowing that this will be fine from the start.
	I did a little research on Facebook policy, and while I did not find any information about this appeal process, I did find information on <a href="https://www.facebook.com/help/159096464162185">proving your identity to Facebook</a>.
	It appears that it is possible to use your real name even if it is not your legal name, though you need to cough up more personal information than I care to.
	First of all, this does not get you out of Facebook&apos;s date of birth requirement.
	As far as I am concerned, Facebook does not need this information.
	Second, you need three forms of identification.
	The first two forms of identification must have your preferred name on them.
	The third can have a different name, such as your legal name, but must have either a photograph of you or have your date of birth.
	I could easily meet these requirements.
	I receive my mail under the name Yst Dawson and my credit card is under this same name.
	Both of these are listed as valid forms of identification.
	As for the third item, I could submit my government-issued identification card that instead of having my real name, has my legal name.
	However, I again feel that this is going too far.
	If Facebook wants my legal name, they will have to put in the minimal effort needed to run a whois query on my domain.
	(Further reading revealed that Facebook allows the covering up of extra information present on the identification documents that are not needed for verification.
	The examples mentioned included covering up your Social Security number or credit card number, but as the state-issued identification card contains a legal name, date of birth, and photograph and only one of these is needed, the photograph and legal name can be covered up.) Besides, registering a Facebook account over <abbr title="The Onion Router">Tor</abbr> seems to require verification of a telephone number these days, and I absolutely refuse to give Facebook a telephone number, even just a burner number.
</p>
<p>
	Our <abbr title="Internet service provider">ISP</abbr> wrote today that someone in our household downloaded something illegally.
	They did not say what that illegal thing was though, so we were unable to determine which of us downloaded it.
	I know that it was not me for two reasons.
	First, I only download things that are under licenses that allow redistribution.
	Second, my traffic is behind three or seven encrypted proxies at all times, so the <abbr title="Internet service provider">ISP</abbr> does not see what I am doing.
	One good thing did come of this though: I managed to talk Cyrus into routing his Web traffic though <abbr title="The Onion Router">Tor</abbr>.
	Vanessa is still convinced that using <abbr title="The Onion Router">Tor</abbr> is incredibly difficult, despite my repeated reassurances, but once Cyrus sees how pretty much nothing has changed over <abbr title="The Onion Router">Tor</abbr>, he can help me convince Vanessa.
	I will not even try with our mother though, at least for now.
	She is far too against pretty much anything relating to anticensorship, online privacy, and freedom.
	If the <abbr title="Internet service provider">ISP</abbr> is going to be this way though, there is no way that I can run a <abbr title="The Onion Router">Tor</abbr> exit node here.
</p>
<p>
	My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
</p>
		<hr/>
		<p>
			Copyright © 2015 Alex Yst;
			You may modify and/or redistribute this document under the terms of the <a rel="license" href="/license/gpl-3.0-standalone.xhtml"><abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr></a>.
			If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
			My address is in the source comments near the top of this document.
			This license also applies to embedded content such as images.
			For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
		</p>
		<p>
			<abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
			This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2015%2F12-December%2F02.xhtml"><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1</a> specification and uses style sheets that conform to the <a href="http://jigsaw.w3.org./css-validator/validator?uri=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2015%2F12-December%2F02.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
		</p>
	</body>
</html>