Sean Gillies (Posts about web)https://sgillies.net/tags/web.atom2023-12-31T01:26:22ZSean GilliesNikolaTwitter's problemhttps://sgillies.net/2022/11/27/twitters-problem.html2022-11-27T12:26:49-07:002022-11-27T12:26:49-07:00Sean Gillies<p>Twitter's biggest problem now is its owner's narcissism and right-wing
radicalization. Josh Marshall calls out Musk's <a class="reference external" href="https://talkingpointsmemo.com/edblog/elon-musk-and-the-narcissism-radicalization-maelstrom">scapegoating of minorities and
other ugly shit</a>:</p>
<blockquote>
<p>We’re hardly four weeks into the Elon era on Twitter and he’s already
cueing up a storyline in which he tried to placate the Blacks and the Jews
and the gays but they betrayed him and set out to “kill Twitter.”</p>
</blockquote>
<p>Musk isn't Tony Stark, he's the Donald Trump of batteries and rockets.</p>Second-guessing the modern webhttps://sgillies.net/2020/05/10/second-guessing-the-modern-web.html2020-05-10T20:09:39-06:002020-05-10T20:09:39-06:00Sean Gillies<p><a class="reference external" href="https://macwright.org/2020/05/10/spa-fatigue.html">Second-guessing the modern web</a> is a super interesting
post. I've never used React to build a web app and am pretty ignorant about it.
For example, I've never heard of "bundle splitting" before. It seems like
something out of a parody of web development. I know I should be skeptical of
something that confirms my biases like this, but Tom always has some good
insight into the tech he's involved in.</p>Goodbye, Twitterhttps://sgillies.net/2017/11/30/goodbye-twitter.html2017-11-30T18:02:01-07:002017-11-30T18:02:01-07:00Sean Gillies<p><a class="reference external" href="https://ramblingspace.com/posts/goodbye-twitter/">This, by Can Duruk</a>, so
much:</p>
<pre class="literal-block">I can’t go on sharing the same space with Trump and Nazis. I am done.</pre>Firefox Quantumhttps://sgillies.net/2017/11/20/firefox-quantum.html2017-11-20T22:00:09-07:002017-11-20T22:00:09-07:00Sean Gillies<p>I've been using Firefox 57.0, aka <a class="reference external" href="https://blog.mozilla.org/blog/2017/11/14/introducing-firefox-quantum/">"Quantum"</a>,
since the end of last week and have been loving it. It feels as fast as
advertised and I haven't noticed any deterioration in rendering of pages.</p>
<p>I've tended to use Chrome as my work browser and Firefox as my personal browser
over the past 4+ years. My personal browser just got a big upgrade. The Mozilla
Servo and Rust Language teams must be feeling pretty pleased and they deserve
it. Congratulations!</p>Zipped Shapefiles on the Webhttps://sgillies.net/2017/11/11/fiona-and-zipped-shapefiles-on-the-web.html2017-11-11T23:31:40-07:002017-11-11T23:31:40-07:00Sean Gillies<p>Here's a preview of a <a class="reference external" href="https://github.com/Toblerity/Fiona/pull/426">new feature coming in Fiona 1.8</a>.</p>
<div class="code"><pre class="code console"><a id="rest_code_b0f7c48ad3ca4c91a6c946553204770c-1" name="rest_code_b0f7c48ad3ca4c91a6c946553204770c-1" href="https://sgillies.net/2017/11/11/fiona-and-zipped-shapefiles-on-the-web.html#rest_code_b0f7c48ad3ca4c91a6c946553204770c-1"></a><span class="go">fio cat zip+s3://mapbox/rasterio/coutwildrnp.zip | fio collect | geojsonio</span>
</pre></div>
<figure>
<img alt="https://c1.staticflickr.com/5/4585/38320664512_35027691c8_b.jpg" src="https://c1.staticflickr.com/5/4585/38320664512_35027691c8_b.jpg">
</figure>Let's Encrypt and Certbothttps://sgillies.net/2017/11/11/lets-encrypt-and-certbot.html2017-11-11T22:37:22-07:002017-11-11T22:37:22-07:00Sean Gillies<p>Two years and two weeks ago <a class="reference external" href="https://sgillies.net/2015/11/29/migration-of-my-blog.html">I made my blog and home page available via HTTPS</a> following
a slightly arduous and manual process. Today I automated deployment of Let's
Encrypt SSL certificates on my <a class="reference external" href="https://trails.sgillies.net/">Fort Collins Trails Status</a> site using <a class="reference external" href="https://certbot.eff.org/">Certbot</a> and 10 lines of Ansible configuration. We've
come a long way in 2 years.</p>Web Linking is Updatedhttps://sgillies.net/2017/10/25/web-linking-is-updated.html2017-10-25T10:25:08-06:002017-10-25T10:25:08-06:00Sean Gillies<p>RFC 5988, which <a class="reference external" href="https://sgillies.net/2010/10/31/rfc-5988.html">I wrote about back in 2010</a>, has been updated by <a class="reference external" href="https://tools.ietf.org/html/rfc8288">RFC
8288</a>.</p>Geodata in the Cloudhttps://sgillies.net/2017/10/14/geodata-in-the-cloud.html2017-10-14T16:21:01-06:002017-10-14T16:21:01-06:00Sean Gillies<p>This past week there was a flurry of blog posts about deploying and accessing
geospatial data in "the cloud." Yes, I'm still putting scare quotes around "the
cloud" in 2017.</p>
<ul class="simple">
<li><p><a class="reference external" href="http://erouault.blogspot.com/2017/10/gdal-and-cloud-storage.html">"GDAL and cloud storage" by Even Rouault</a></p></li>
<li><p><a class="reference external" href="https://medium.com/planet-stories/cloud-native-geospatial-part-2-the-cloud-optimized-geotiff-6b3f15c696ed">"Cloud Native Geospatial Part 2: The Cloud Optimized GeoTIFF" by Chris Holmes</a></p></li>
<li><p><a class="reference external" href="https://blog.mapbox.com/combining-the-power-of-aws-lambda-and-rasterio-8ffd3648c348">"Combining the power of AWS Lambda and Rasterio" by Vincent Sarago</a></p></li>
</ul>
<p>I wrote a post specifically about <a class="reference external" href="https://github.com/mapbox/rasterio/issues/942">Rasterio and datasets on S3</a> last December. Shortly before that, Chris
Henrick wrote a great post about <a class="reference external" href="https://hi.stamen.com/stamen-aws-lambda-tiler-blog-post-76fc1138a145">preparing data to be deployed on S3 for use
with GDAL and Rasterio</a>.</p>
<p>As far as I can tell, the birth announcement for geodata in the cloud came
7 years ago in <a class="reference external" href="http://crschmidt.net/blog/archives/425/vsi-curl-support/">"VSI Curl Support" by Christopher Schmidt</a>.</p>
<p>It's remarkable that the authors of HTTP/1.1 foresaw this kind of application
in 1999: <a class="reference external" href="https://tools.ietf.org/html/rfc2616#section-14.16">https://tools.ietf.org/html/rfc2616#section-14.16</a>.</p>Pruning CRS from GeoJSONhttps://sgillies.net/2014/08/06/pruning-crs-from-geojson.html2014-08-06T00:00:00-06:002014-08-06T00:00:00-06:00Sean Gillies<p>I uploaded <a class="reference external" href="http://tools.ietf.org/html/draft-butler-geojson-04">version 4 of the GeoJSON I-D</a> to the IETF's tracker
yesterday. It contains a <a class="reference external" href="http://tools.ietf.org/rfcdiff?url2=draft-butler-geojson-04.txt">major change to section
3</a>. In
version 3, the draft contained more or less the same text as in
<a class="reference external" href="http://geojson.org/geojson-spec.html">http://geojson.org/geojson-spec.html</a>, but version 4 declares that coordinate
reference systems other than the default are not recommended and that means of
describing them, <em>including the CRS object of the original 2008 spec</em>, are now
application specific concerns. In other words, if you want projected
coordinates in the GeoJSON that travels between the front and back ends of your
web app you're on your own. Furthermore, you're doing it wrong if you
publish this projected GeoJSON to the open web and expect processors to have
access to an EPSG database.</p>
<p>I've been watching the IETF JSON Working Group's JSON, I-JSON, and JSON
Sequence discussions closely while revising the GeoJSON I-D. Version 4 treats
CRS like RFC 7159 treats <a class="reference external" href="http://tools.ietf.org/html/rfc7159#section-8">character encoding</a>, acknowledging other
coordinate reference systems while making a very strong recommendation for
using the default CRS. You could say CRS84 is our UTF-8. Version 4 also requires
that coordinates not be ordered latitude, longitude. Lat/lng is like our byte
order mark.</p>
<p>Removing the CRS object description from the draft has been a goal of mine from
the start. Its poor design has been a distraction and it never was as useful to
developers as we intended. The GeoJSON draft is better without it. I get the
impression that some standards people will see its removal from the draft as
a void to be filled. CRS wonks gotta wonk, I suppose, but do developers care
very much that there is no JSON equivalent of <code class="docutils literal"><gml:ProjectedCRS></code>? I don't
think so.</p>Steady as she goeshttps://sgillies.net/2014/07/02/steady-as-she-goes.html2014-07-02T00:00:00-06:002014-07-02T00:00:00-06:00Sean Gillies<p>Standards organizations are increasingly interested in the little format that
could and if <a class="reference external" href="http://www.w3.org/2014/05/geo-charter">http://www.w3.org/2014/05/geo-charter</a> is any indication it's
likely that you'll be seeing more mention of <a class="reference external" href="http://geojson.org">GeoJSON</a>
and <a class="reference external" href="http://github.com/geojson/geojson-ld">GeoJSON-LD</a> in OGC and W3C
materials soon. However, the GeoJSON working group (for which I'm speaking in
just this and the following sentence), is going to keep its own independent
course. Work on the <a class="reference external" href="http://tools.ietf.org/html/draft-butler-geojson-03">GeoJSON Internet Draft</a> will continue to be
done at <a class="reference external" href="https://github.com/geojson/draft-geojson">https://github.com/geojson/draft-geojson</a> and on the GeoJSON <a class="reference external" href="http://lists.geojson.org/listinfo.cgi/geojson-geojson.org">discussion
list</a>.</p>
<p>Now, Mapbox has recently joined the OGC and I've subsequently received emails
from OGC members seeking discussion of GeoJSON. This is exactly the thing that
I want to avoid and I will decline to do so outside of the GeoJSON venues
I listed above. I hope you will, too, because discussions of GeoJSON on closed OGC
technical committee lists or private emails with other OGC members aren't going
to do the GeoJSON format, I-D, or users any good. GeoJSON is for the open web.
Let's continue to tend it on the open web.</p>