📝 Updated rss feeds
This commit is contained in:
parent
71fb71597c
commit
e096e3ca57
6 changed files with 4595 additions and 0 deletions
|
|
@ -22,3 +22,6 @@ file://./rss/skolelinux.rss
|
|||
file://./rss/simonwillison.atom
|
||||
file://./rss/felixcrux.xml
|
||||
file://./rss/david_walsh.rss
|
||||
file://./rss/democracylab.rss
|
||||
file://./rss/json_schema.xml
|
||||
file://./rss/brett_langdon.xml
|
||||
|
|
|
|||
1770
.config/newsboat/rss/brett_langdon.xml
Normal file
1770
.config/newsboat/rss/brett_langdon.xml
Normal file
File diff suppressed because it is too large
Load diff
49
.config/newsboat/rss/democracylab.rss
Normal file
49
.config/newsboat/rss/democracylab.rss
Normal file
File diff suppressed because one or more lines are too long
2259
.config/newsboat/rss/feed.rss
Normal file
2259
.config/newsboat/rss/feed.rss
Normal file
File diff suppressed because it is too large
Load diff
304
.config/newsboat/rss/felixcrux.xml
Normal file
304
.config/newsboat/rss/felixcrux.xml
Normal file
|
|
@ -0,0 +1,304 @@
|
|||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Felix Crux</title><link>https://felixcrux.com</link><description>Technology & Miscellanea</description><atom:link href="https://felixcrux.com/blog/rss.xml" rel="self"></atom:link><lastBuildDate>Sun, 08 Jan 2023 19:47:21 -0500</lastBuildDate><item><title>Feeds: The Only Civilised Way to Read Online</title><link>https://felixcrux.com/blog/feeds-the-only-civilised-way-to-read-online</link><description><p>How do you follow your favourite online creators and their blogs, articles,
|
||||
videos, podcasts, comics, or what have you? How do you choose what to read
|
||||
when you have a few minutes to kill on the bus, or when you want to get caught
|
||||
up in the morning with a cup of coffee?</p>
|
||||
|
||||
<p>Most people hand this choice over to social media, inviting along the whole
|
||||
associated host of problems like clickbait; outrage amplification; snooping
|
||||
targeted advertising; radicalising rabbit-holes; echo-chambers and filter
|
||||
bubbles; algorithms choosing what to show you based on “engagement” rather
|
||||
than what you’d want for yourself; and on and on.</p>
|
||||
|
||||
<p>There’s a better way — and there has been for decades! Amazingly, it seems
|
||||
underused even within tech circles, and almost completely unknown to the
|
||||
general public. It’s super easy to use, actually <em>more</em> convenient than
|
||||
social media apps, and leaves you in complete control of what you see.</p>
|
||||
|
||||
<p>I’m talking, of course, about RSS/Atom web feeds, and I contend that they
|
||||
are not only a better alternative, but in fact I’d go so far as to say that a
|
||||
feed reader is the only tolerable and civilised way to read online! The system
|
||||
works really well and more in line with what (I think) most people actually
|
||||
want; it minimizes the use of harmful social media platforms; and it helps
|
||||
foster a more vibrant, independent, creative, and non-commerical Web. So drop
|
||||
your non-chronological algorithmically-obscured sponsored timeline, and let’s
|
||||
have a whirlwind overview of what feeds are and how to use them!</p>
|
||||
<h3>What are feeds and feed readers?</h3>
|
||||
|
||||
<p>The core of the problem is this: You might have hundreds of people whose
|
||||
work you’re potentially interested in, but you can’t realistically regularly
|
||||
check whether each one has published something new recently. The solution
|
||||
(first cooked up around 1999!) is a <em>web feed</em> or <em>news feed</em>
|
||||
(sometimes <em>RSS feed</em> or <em>Atom feed</em>, <a
|
||||
href="#appendix-names">for uninteresting technical reasons</a>), combined
|
||||
with a program called a <em>feed reader</em> (or a <em>news reader</em> or
|
||||
<em>aggregator</em>). I strongly suspect that the wide range of inconsistent
|
||||
names has been a big hindrance to these tools being widely adopted, but in
|
||||
practice which name you use doesn’t matter: I’m just going to call them
|
||||
<em>feeds</em> and <em>feed readers</em> from now on.</p>
|
||||
|
||||
<p>A feed is a machine-readable version of new posts on a site. For a blog, it
|
||||
might contain, say, the last 10 blog posts, much like the human-readable
|
||||
“front page” of the web version would. A feed reader is a program that
|
||||
monitors all of the feeds from all of the sites that you’re interested in, and
|
||||
aggregates new updates in one place for you to read at your leisure.</p>
|
||||
|
||||
<p>So, if there’s a blog or podcast or something else you’d like to follow,
|
||||
you simply subscribe to it in your feed reader, and now all new updates will
|
||||
be automagically conveyed to you as soon as they come out. Your feed reader
|
||||
keeps track of what you’ve not yet read, and displays all posts in a simple
|
||||
chronological timeline, so you never miss anything. You can catch up whenever
|
||||
you want; there are no algorithms boosting controversial or sponsored
|
||||
nonsense; and no ads.</p>
|
||||
|
||||
<p>Feed readers would traditionally have been desktop programs that downloaded
|
||||
all the feeds you were monitoring onto your computer. That model still works
|
||||
just fine (and in fact may already be available on your computer thanks to it
|
||||
being a built-in feature of the <a
|
||||
href="https://support.mozilla.org/en-US/kb/how-subscribe-news-feeds-and-blogs">Thunderbird</a>
|
||||
and <a
|
||||
href="https://support.microsoft.com/en-us/office/subscribe-to-an-rss-feed-73c6e717-7815-4594-98e5-81fa369e951c">Outlook</a>
|
||||
email clients), but nowadays most people prefer to use online services so that
|
||||
their read/unread status for individual posts can be synchronized between
|
||||
their desktop and their phone. Articles can then be read in the browser or in
|
||||
a smartphone app, and you’ll always be up-to-date with what you’ve already
|
||||
seen and what you’ve not yet read.</p>
|
||||
|
||||
<p>Which feed reader you choose doesn’t matter much. Some popular web app
|
||||
options include <a href="https://newsblur.com/">NewsBlur</a>, <a
|
||||
href="https://feedly.com/">Feedly</a>, <a
|
||||
href="https://feedbin.com/">Feedbin</a> and <a
|
||||
href="https://www.inoreader.com/">Inoreader</a>, or if you’re up for
|
||||
self-hosting, <a href="https://tt-rss.org/">Tiny Tiny RSS</a>. Desktop
|
||||
applications include <a href="https://netnewswire.com/">NetNewsWire</a>, <a
|
||||
href="https://jangernert.github.io/FeedReader/">FeedReader</a>, <a
|
||||
href="https://newsboat.org/">Newsboat</a>, and <a
|
||||
href="https://hyliu.me/fluent-reader/">Fluent Reader</a>. There are many more;
|
||||
these are just a sample. All of the (non self-hosted) web services are paid
|
||||
products — that’s the tradeoff for not being profiled and advertised at.
|
||||
Fortunately, most have free tiers or free trial periods, so you can try them
|
||||
all out and see which you like best. Many try to differentiate themselves by
|
||||
offering extra features such as optional filtering or even
|
||||
machine-learning-based prioritization of your feeds, but in my case that’s
|
||||
what I’m trying to get <em>away</em> from so I just turn those features off
|
||||
and don’t use them. I personally use NewsBlur, which has worked just fine
|
||||
(along with their mobile app) for years.</p>
|
||||
|
||||
<p>So, you pick a feed reader to try out, and set up an account. Then, you
|
||||
find the feeds published by sites you’d like to follow, and subscribe to them
|
||||
in your feed reader. You can then check in whenever you’d like, and any new
|
||||
posts will be there waiting for you in your reader. No more random
|
||||
outrage-bait or advertising, just a chronological feed of what <em>you</em>
|
||||
chose to follow.</p>
|
||||
|
||||
<h3>But does anybody actually publish feeds?</h3>
|
||||
|
||||
<p>Surprisingly, yes, almost every blog or publishing platform out there does
|
||||
in fact publish a feed (often automatically, without the author needing to do
|
||||
anything special to set it up). This includes publishing systems like Medium,
|
||||
Substack, Wordpress, and Blogger, as well as smaller self-hosted site
|
||||
generators. You can follow feeds from an astonishing variety of sources,
|
||||
including YouTube channels, <a
|
||||
href="https://www.canada.ca/en/environment-climate-change/services/weather-general-tools-resources/weatheroffice-online-services/data-services.html">Environment
|
||||
Canada weather warnings</a>, <a
|
||||
href="https://www.cnn.com/services/rss/">CNN</a> or <a
|
||||
href="https://www.bbc.co.uk/news/10628494">the BBC</a>, <a href="
|
||||
https://github.com/felixc/rexiv2/releases.atom">GitHub releases</a>, <a
|
||||
href="https://status.circleci.com/history.atom">status pages for online
|
||||
services</a>, and of course, the myriad of small blogs out there on the web.
|
||||
The entire podcasting ecosystem is secretly built on top of feeds — that’s how
|
||||
new episodes get delivered to you! And, naturally, <a
|
||||
type="application/rss+xml" rel="alternate"
|
||||
href="https://felixcrux.com/blog/rss.xml">my feed is right here</a>.</p>
|
||||
|
||||
<p>To find a feed for a particular site, you can almost always just put in the
|
||||
address of the website into your feed reader, and it will auto-discover the
|
||||
feed. If not, first look for the ubiquitous orange and white feed icon: <img
|
||||
src="/media/img/feed.png" alt="">, perhaps alongside words such as “feed”, “RSS”, or
|
||||
“Atom”. There will be a link, which you can put into your feed reader to
|
||||
subscribe. Web browsers used to highlight the existence of feeds with an icon
|
||||
in the address bar, and you can restore that functionality to Firefox with <a
|
||||
href="https://addons.mozilla.org/en-US/firefox/addon/want-my-rss/">this
|
||||
addon</a>.</p>
|
||||
|
||||
<h3>What about discovering new authors?</h3>
|
||||
|
||||
<p>This is where some forms of social media perhaps have a defensible role to
|
||||
play. Potential sources for content discovery can be thought of as lying along
|
||||
a spectrum that at one end has high quality content but low frequency of
|
||||
discovering new sources, and at the other end has the incredible torrent of
|
||||
material that can be found online, which is usually of low value.</p>
|
||||
|
||||
<p>The most reliable, but slowest, way of finding new feeds to follow is to
|
||||
wait for friends, family, or coworkers to share links to things they found
|
||||
interesting. Rather than just read them and move on, take a minute to poke
|
||||
around the site and see if you think you’d like to see more from that creator.
|
||||
If so, check whether they have a feed, and subscribe to it. If it turns out
|
||||
they never post again, there’s no harm done. If it turns out their future
|
||||
posts aren’t very interesting, that’s ok: just unsubscribe.</p>
|
||||
|
||||
<p>A higher-volume but perhaps more inconsistent source of feeds to follow
|
||||
might be topic/community-focused public aggregator sites. These are a form of
|
||||
social media, but they center on particular subjects or communities, rather
|
||||
than whatever anyone would like to share. For example, technologists often
|
||||
follow <a href="https://news.ycombinator.com/">Hacker News</a>, <a
|
||||
href="https://lobste.rs/">Lobsters</a>, or <a
|
||||
href="https://www.reddit.com/r/programming/">the Programming subreddit</a>.
|
||||
Like with links shared with you directly, if you find something here you like,
|
||||
poke around the author’s homepage and consider following them for more. As a
|
||||
bonus, if you care about accruing karma/points/reputation on these social
|
||||
sites, this gives you an edge in finding new content to post to them!</p>
|
||||
|
||||
<p>To get a head start, here are two exported data files of the <a
|
||||
href="/files/feeds-tech.opml">tech-focused</a> and <a
|
||||
href="/files/feeds-general.opml">general</a> feeds I follow. You should be
|
||||
able to import them into your feed reader of choice — hopefully you find
|
||||
something you like! Note though that I don’t necessarily <em>endorse</em> any
|
||||
of these sites or authors; they may just have published one good thing years
|
||||
ago and I have no idea what they’ve been up to since.</p>
|
||||
|
||||
<h3>Ultimately, why should I bother with this?</h3>
|
||||
|
||||
<p>Like I said at the start, for me it comes down to three reasons:</p>
|
||||
|
||||
<p>Firstly, it just works really well — better than alternative options. By
|
||||
that I simply mean that a feed reader really is the best way to keep up with
|
||||
blogs and posts! A favourite part of my day is having my morning coffee and
|
||||
catching up on feeds. I can pick them up when I have a few minutes to spare,
|
||||
and what I’ve read or not read is automatically synced between my devices.
|
||||
Easy, pleasant, simple, convenient, and I’m in control of what I read.</p>
|
||||
|
||||
<p>The second reason is maybe not universally accepted by everyone, but in my
|
||||
opinion, it’s a healthier alternative to social media. I feel those platforms
|
||||
should be used only lightly and warily, if at all. Their very structure
|
||||
inherently promotes controversy and pile-ons rather than discussion; and fake
|
||||
“influencer” distortions over reality. While they may be a reasonable way to
|
||||
keep up with a small group of friends and family, opening the door to
|
||||
strangers being algorithmically boosted into your timeline, and the associated
|
||||
advertising and psychological manipulation (whether intentional or merely a
|
||||
side-effect) doesn’t feel healthy to me. Following blogs directly is a way to
|
||||
minimize or outright bypass these platforms and still benefit from the wide
|
||||
range of content out there on the web.</p>
|
||||
|
||||
<p>And finally, the third reason is that I hope that directly following blogs
|
||||
and creators promotes the older, more independent, non-commercial version of
|
||||
what the Web could be. Rather than merely a more interactive cable TV channel
|
||||
controlled by big platforms, we can encourage anyone who has an interesting
|
||||
story to tell to share it online, and they can build up a dedicated audience
|
||||
independently, without having to pander and clickbait in the hope of
|
||||
algorithmically going viral. I want to support <em>that</em> version of the
|
||||
Web by choosing what to read, following small blogs, and enjoying reading long
|
||||
blog posts written simply because the author had something to say.</p>
|
||||
|
||||
<h3 id="appendix-names">Appendix: Why all the inconsistent names?</h3>
|
||||
|
||||
<p>An unfortunate complication when evangelizing or adopting feeds is the
|
||||
proliferation of opaque names that all mean essentially the same thing. Why is
|
||||
it like this?</p>
|
||||
|
||||
<p>The <em>concept</em> of what we’re trying to publish is a “feed”. The
|
||||
original standardized <em>format</em> for publishing feeds was “RSS”: “Really
|
||||
Simple Syndication”. Several years later there was a schism in the community
|
||||
and a separate group produced a new standard format called “Atom”. Today, the
|
||||
choice of format is largely irrelevant, and essentially all feed readers
|
||||
support both. However, the <em>name</em> “RSS” caught on reasonably well, and
|
||||
so sometimes people will call the generic concept “RSS feeds” — confusingly
|
||||
even when the actual format in use might be Atom and not RSS!</p>
|
||||
|
||||
<p>However, ultimately, none of these details matter in the slightest to
|
||||
users. The only reason to know that RSS, Atom, news feed, and web feed are all
|
||||
possible names is so you can find the link to the feed to plonk it into your
|
||||
feed reader, which will happily work with any format or name.</p>
|
||||
</description><pubDate>Sun, 08 Jan 2023 19:47:21 -0500</pubDate><guid isPermaLink="false">feeds-the-only-civilised-way-to-read-online</guid></item><item><title>New Recommended Reading: People and Project Management</title><link>https://felixcrux.com/blog/new-recommended-reading-people-and-project-management</link><description><p>I’ve updated my <a href="https://felixcrux.com/library/recommended-reading-list-for-software-professionals#people-and-project-management">
|
||||
recommended reading list for software professionals</a> (<a href="https://felixcrux.com/blog/introducing-recommended-reading-list-for-software-professionals">introduced
|
||||
and explained here</a>) with a new section on people and project management.
|
||||
</p>
|
||||
|
||||
<p>Don’t think you need the word “manager” in your job title to benefit from
|
||||
learning these skills. If you want to make yourself more useful to a team,
|
||||
teach others, help your projects succeed, or guide groups to making good
|
||||
decisions, these books will help.</p>
|
||||
|
||||
<p>The <a href="https://felixcrux.com/library/recommended-reading-list-for-software-professionals#people-and-project-management">
|
||||
new section of the list is here</a>.</p>
|
||||
</description><pubDate>Sat, 30 Nov 2019 11:27:59 -0500</pubDate><guid isPermaLink="false">new-recommended-reading-people-and-project-management</guid></item><item><title>More Recommended Reading: Information, Design, and UX</title><link>https://felixcrux.com/blog/more-recommended-reading-information-design-ux</link><description><p>I’ve just added a new section to my <a href="https://felixcrux.com/library/recommended-reading-list-for-software-professionals#presenting-information-design-and-user-experience">
|
||||
recommended reading list for software professionals</a> (<a href="https://felixcrux.com/blog/introducing-recommended-reading-list-for-software-professionals">introduced
|
||||
and explained here</a>). This new section covers the presentation
|
||||
of information, design, and user interfaces/experiences.
|
||||
|
||||
<p>I’m not a designer, and reading these books won’t make you one either. But
|
||||
every developer should know how to present information and interfaces clearly
|
||||
and comprehensibly.</p>
|
||||
|
||||
<p>You can find <a href="https://felixcrux.com/library/recommended-reading-list-for-software-professionals#presenting-information-design-and-user-experience">
|
||||
the list itself here</a>.</p>
|
||||
</description><pubDate>Fri, 24 May 2019 16:25:13 -0400</pubDate><guid isPermaLink="false">more-recommended-reading-information-design-ux</guid></item><item><title>Recommended Reading List for Software Professionals</title><link>https://felixcrux.com/blog/introducing-recommended-reading-list-for-software-professionals</link><description><p>I’ve started putting together a list of the “core” books I recommend for
|
||||
people interested in exploring different facets of our field. I certainly
|
||||
don’t think you need to read all of them to be a capable software
|
||||
professional; rather it is the list I would put together if asked about how to
|
||||
learn more about specific areas.<p>
|
||||
|
||||
<p>This list came about because after compiling similar lists two or three
|
||||
times over the years in various places and formats, I’m following good
|
||||
development practice and factoring it out for reuse and sharing.</p>
|
||||
|
||||
<p>You can find <a href="https://felixcrux.com/library/recommended-reading-list-for-software-professionals">
|
||||
the list itself here</a>.</p>
|
||||
|
||||
<p>The list is far from complete; in fact today I’m starting with just one
|
||||
area: the culture and history of our field. Over time I will add sections on
|
||||
technical system design and architecture; project and people management; data
|
||||
visualization, information presentation, and user experience design; etc. Let
|
||||
me know if there are areas you want covered, or if you have recommendations of
|
||||
your own!</p>
|
||||
</description><pubDate>Sun, 19 May 2019 14:10:27 -0400</pubDate><guid isPermaLink="false">introducing-recommended-reading-list-for-software-professionals</guid></item><item><title>Favourite Firefox Feature: Keyword Search Bookmarks</title><link>https://felixcrux.com/blog/favourite-firefox-feature-keyword-search-bookmarks</link><description><p>One of my favourite features of the Firefox web browser is surprisingly
|
||||
unknown and sadly underused. Keyword search bookmarks let you kick off a
|
||||
custom search of any site straight from the address bar (a.k.a. the “awesome
|
||||
bar”). For example, if you typed “<code>w hedgehog</code>”, you could go to
|
||||
the Wikipedia page for the little critters, or “<code>img hedgehog</code>”
|
||||
could show you a cute image search.</p>
|
||||
<p>This is similar to search engine DuckDuckGo’s “<a
|
||||
href="https://duckduckgo.com/bang_lite.html">!bang commands</a>”, except you
|
||||
can define your own new ones and pick whatever keyword you like, instead of
|
||||
being limited to pre-defined ones.</p>
|
||||
|
||||
<p>You can set up a new search by right-clicking on any search field (try <a
|
||||
href="https://en.wikipedia.org">the one in the top-right on Wikipedia</a>) and
|
||||
selecting the context menu option “Add a Keyword for this Search…”. In the
|
||||
dialog that pops up, just pick the shortcut you’d like to use (for example,
|
||||
for Wikipedia I use “w”).</p>
|
||||
|
||||
<video autoplay loop muted playsinline controls width="380" height="290"
|
||||
style="margin: 0 auto; display: block; border: 1px solid #ddd; box-shadow: 1px 1px 3px #ddd;">
|
||||
<source src="/media/img/firefox-keyword-search.webm" type="video/webm">
|
||||
<source src="/media/img/firefox-keyword-search.mp4" type="video/mp4">
|
||||
</video>
|
||||
|
||||
</p>Alternatively, you can do the same thing by creating a regular bookmark
|
||||
through the full bookmark manager (not the sidebar) and filling in the
|
||||
“Keyword” field. In the bookmark URL, put the string “<code>%s</code>”
|
||||
wherever you want your search term to appear, and when you trigger the
|
||||
bookmark search via the keyword, it will be replaced with your query.<p>
|
||||
|
||||
<p>Some of my keyword searches that I use frequently:</p>
|
||||
|
||||
<ul>
|
||||
<li><kbd>w</kbd> → <a href="https://secure.wikimedia.org/wikipedia/en/wiki/Special:Search?search=%s">Wikipedia</a></li>
|
||||
<li><kbd>map</kbd> → <a href="http://maps.google.com/maps?q=%s">Google Maps</a></li>
|
||||
<li><kbd>img</kbd> → <a href="https://www.google.com/search?q=%s&tbm=isch">Google Images</a></li>
|
||||
<li><kbd>yt</kbd> → <a href="http://www.youtube.com/results?search_query=%s">YouTube</a></li>
|
||||
<li><kbd>py</kbd> → <a href="http://docs.python.org/3/search.html?q=%s">Python docs</a></li>
|
||||
<li><kbd>rs</kbd> → <a href="https://doc.rust-lang.org/std/index.html?=All%20crates&search=%s">Rust docs</a></li>
|
||||
<li><kbd>mdn</kbd> → <a href="https://developer.mozilla.org/en-US/search?q=%s">Mozilla Developer Network</a></li>
|
||||
</ul>
|
||||
|
||||
<p>It’s just super handy to be able to type “<code>map 123 main st</code>” or
|
||||
“<code>w echidna</code>” and get to the right place — especially on a phone.
|
||||
You can also make great use of this at work by setting up search bookmarks for
|
||||
your tools; like GitHub, JIRA, internal docs, etc.</p>
|
||||
|
||||
<p>I believe Chrome can also do something similar, but it may involve a few
|
||||
more steps and configuring a custom search engine — I’m not sure.</p>
|
||||
|
||||
<p>I hope this feature will delight you as much as it does me!</p>
|
||||
</description><pubDate>Thu, 28 Mar 2019 21:55:46 -0400</pubDate><guid isPermaLink="false">favourite-firefox-feature-keyword-search-bookmarks</guid></item></channel></rss>
|
||||
210
.config/newsboat/rss/json_schema.xml
Normal file
210
.config/newsboat/rss/json_schema.xml
Normal file
|
|
@ -0,0 +1,210 @@
|
|||
<?xml version="1.0" encoding="UTF-8" ?>
|
||||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||||
<channel>
|
||||
<title>JSON Schema Blog RSS Feed</title>
|
||||
<link>https://json-schema.org/blog/rss.xml</link>
|
||||
<atom:link rel="self" href="https://json-schema.org/blog/rss.xml" type="application/rss+xml"/>
|
||||
<description>JSON Schema Blog</description>
|
||||
<language>en-gb</language>
|
||||
<copyright>Made with :love: by the JSON Schema team.</copyright>
|
||||
<pubDate>Wed, 25 Jan 2023 10:21:06 GMT</pubDate>
|
||||
<generator>next.js</generator>
|
||||
<item>
|
||||
<title>Hello 2023, Hello JSON Schema Community</title>
|
||||
<description>Since Ben Hutton joined Postman to work full-time on JSON Schema the past year, other top contributors like Jason De
|
||||
</description>
|
||||
<link>https://json-schema.org/blog/posts/hello-2023--hello-json-schema-community?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/hello-2023--hello-json-schema-community?utm_source=rss</guid>
|
||||
<pubDate>Tue, 10 Jan 2023 00:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2023/hello-2023--hello-json-schema-community/jai.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>Introducing: Bowtie</title>
|
||||
<description>A new tool for executing JSON Schema implementations & a call to help improve it</description>
|
||||
<link>https://json-schema.org/blog/posts/bowtie-intro?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/bowtie-intro?utm_source=rss</guid>
|
||||
<pubDate>Wed, 16 Nov 2022 00:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2022/bowtie-intro/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>How the W3C Web of Things brings JSON Schema to the Internet of Things</title>
|
||||
<description>Using JSON Schema at the W3C Web of Things to create an interoperability layer so that different IoT platforms, protocols and standards can operate together</description>
|
||||
<link>https://json-schema.org/blog/posts/w3c-wot-case-study?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/w3c-wot-case-study?utm_source=rss</guid>
|
||||
<pubDate>Tue, 01 Nov 2022 06:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2022/w3c-wot-case-study/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>Towards a stable JSON Schema</title>
|
||||
<description>About this time last year, I hosted a discussion at the API Specification
|
||||
Conference about the future of JSON Schema. The most popular topic of discussion
|
||||
was, when JSON Schema is going to be "done".
|
||||
</description>
|
||||
<link>https://json-schema.org/blog/posts/future-of-json-schema?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/future-of-json-schema?utm_source=rss</guid>
|
||||
<pubDate>Fri, 21 Oct 2022 00:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2022/stability/arches.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>Using Dynamic References to Support Generic Types</title>
|
||||
<description>A step in the right direction for modelling data with JSON Schema</description>
|
||||
<link>https://json-schema.org/blog/posts/dynamicref-and-generics?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/dynamicref-and-generics?utm_source=rss</guid>
|
||||
<pubDate>Wed, 31 Aug 2022 00:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2022/dynamicref-and-generics/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>Fixing JSON Schema Output</title>
|
||||
<description>I have a problem: when I read GitHub issues, they occasionally resonate with me, and I obsess about them until they're resolved. That may not sound like a problem to some, but when that resolution c
|
||||
</description>
|
||||
<link>https://json-schema.org/blog/posts/fixing-json-schema-output?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/fixing-json-schema-output?utm_source=rss</guid>
|
||||
<pubDate>Sat, 23 Jul 2022 00:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2022/fixing-json-schema-output/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>The Architectural Scope of JSON Schema</title>
|
||||
<description>What actually is JSON Schema?!</description>
|
||||
<link>https://json-schema.org/blog/posts/the-architectural-scope-of-json-schema?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/the-architectural-scope-of-json-schema?utm_source=rss</guid>
|
||||
<pubDate>Fri, 15 Jul 2022 00:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2022/the-architectural-scope-of-json-schema/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>Joining Postman</title>
|
||||
<description>In the last couple of weeks, you may have seen that Postman has been investing
|
||||
heavily in JSON Schema's future by hiring some of its top contributors giving
|
||||
them the opportunity to work full time on
|
||||
</description>
|
||||
<link>https://json-schema.org/blog/posts/joining-postman?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/joining-postman?utm_source=rss</guid>
|
||||
<pubDate>Sun, 03 Jul 2022 00:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2022/joining-postman/baldy-hs-web.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>And Then There Were Three</title>
|
||||
<description>More full-time contributors is better, right?</description>
|
||||
<link>https://json-schema.org/blog/posts/and-then-there-were-three?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/and-then-there-were-three?utm_source=rss</guid>
|
||||
<pubDate>Thu, 23 Jun 2022 00:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2022/and-then-there-were-three/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>Hello World, Hello Postman</title>
|
||||
<description>Oh hello there! A second person is now working full-time on JSON Schema.</description>
|
||||
<link>https://json-schema.org/blog/posts/hello-world-hello-postman?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/hello-world-hello-postman?utm_source=rss</guid>
|
||||
<pubDate>Thu, 16 Jun 2022 00:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2022/hello-world-hello-postman/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>Astonishing Serializations & Schemas of Hyperborea</title>
|
||||
<description>Using JSON Schema for validating role-playing character sheets.</description>
|
||||
<link>https://json-schema.org/blog/posts/hyperborea?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/hyperborea?utm_source=rss</guid>
|
||||
<pubDate>Wed, 18 May 2022 00:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2022/hyperborea/cover.jpg" length="15026" type="image/jpeg"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>Get started with JSON Schema in Node.js</title>
|
||||
<description>Learn how to use JSON Schema for validation in your Node.js applications.</description>
|
||||
<link>https://json-schema.org/blog/posts/get-started-with-json-schema-in-node-js?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/get-started-with-json-schema-in-node-js?utm_source=rss</guid>
|
||||
<pubDate>Mon, 16 May 2022 06:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2022/get-started-with-json-schema-in-node-js/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>How Tyler Technologies reduced its client feedback loop with JSON Schema</title>
|
||||
<description>Using JSON Schema at Tyler Technologies meant showing added value to clients could take minutes rather than days or in some cases weeks.</description>
|
||||
<link>https://json-schema.org/blog/posts/tyler-technologies-case-study?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/tyler-technologies-case-study?utm_source=rss</guid>
|
||||
<pubDate>Mon, 09 May 2022 06:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2022/tyler-technologies-case-study/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>It all starts with applicability - JSON Schema Fundamentals part 1</title>
|
||||
<description>We explore the fundamental JSON Schema concepts: Applicability, Subschemas, and Assertion Boolean Logic - Everyone needs good fundamentals.</description>
|
||||
<link>https://json-schema.org/blog/posts/applicability-json-schema-fundamentals-part-1?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/applicability-json-schema-fundamentals-part-1?utm_source=rss</guid>
|
||||
<pubDate>Mon, 21 Mar 2022 00:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2022/fundamentals-part-1/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>JSON Schema joins the OpenJS Foundation and 2022 updates</title>
|
||||
<description>Find out what we've been doing in 2021 and read about our biggest development yet... joining the OpenJS Foundation. Oh, and WE'RE HIRING!</description>
|
||||
<link>https://json-schema.org/blog/posts/json-schema-joins-the-openjsf?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/json-schema-joins-the-openjsf?utm_source=rss</guid>
|
||||
<pubDate>Fri, 11 Feb 2022 00:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2022/json-schema-joins-the-openjsf/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>JSON Schema in 5 minutes</title>
|
||||
<description>Everyone needs good fundamentals, and understanding the basics of JSON Schema changes how you read, reason, and develop Schemas.</description>
|
||||
<link>https://json-schema.org/blog/posts/json-schema-in-5-minutes?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/json-schema-in-5-minutes?utm_source=rss</guid>
|
||||
<pubDate>Fri, 21 Jan 2022 00:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2022/json-schema-in-5-minutes/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>クックパッド株式会社におけるJSON Schemaの活用事例</title>
|
||||
<description>クックパッド株式会社ではJSON Schemaを活用することによって、クックパッドマートにおける販売者の商品登録時の正確性と体験を改善し、商品審査にかかる運営上の負担を大幅に軽減することができました。</description>
|
||||
<link>https://json-schema.org/blog/posts/cookpad-case-study-jp?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/cookpad-case-study-jp?utm_source=rss</guid>
|
||||
<pubDate>Mon, 17 Jan 2022 06:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2021/cookpad-case-study/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>JSON Schema deduplicated complex logic and validation at Cookpad</title>
|
||||
<description>Using JSON Schema at Cookpad improved the accuracy and experience when registering products, and has greatly reduced the operational burden of product screening.</description>
|
||||
<link>https://json-schema.org/blog/posts/cookpad-case-study-en?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/cookpad-case-study-en?utm_source=rss</guid>
|
||||
<pubDate>Thu, 09 Dec 2021 06:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2021/cookpad-case-study/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>Validating OpenAPI and JSON Schema</title>
|
||||
<description>Dynamic references make it possible to validate the schemas in an OpenAPI document even though OpenAPI does not constrain which JSON Schema dialects can be used.</description>
|
||||
<link>https://json-schema.org/blog/posts/validating-openapi-and-json-schema?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/validating-openapi-and-json-schema?utm_source=rss</guid>
|
||||
<pubDate>Wed, 08 Dec 2021 00:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2021/validating-openapi-and-json-schema/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>Why JSON Schema needs a Code of Conduct</title>
|
||||
<description>The community of JSON Schema is growing, and the community needs a culture for interactions to avoid past mistakes.</description>
|
||||
<link>https://json-schema.org/blog/posts/code-of-conduct-for-json-schema?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/code-of-conduct-for-json-schema?utm_source=rss</guid>
|
||||
<pubDate>Wed, 24 Nov 2021 06:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2021/code-of-conduct-for-json-schema/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
<item>
|
||||
<title>JSON Schema bundling finally formalised</title>
|
||||
<description>Existing tooling developers have created their own approaches to bundling JSON Schema and OpenAPI documents, but that can lead to errors. Bundling is now standardised.</description>
|
||||
<link>https://json-schema.org/blog/posts/bundling-json-schema-compound-documents?utm_source=rss</link>
|
||||
<category>blog</category>
|
||||
<guid isPermaLink="true">https://json-schema.org/blog/posts/bundling-json-schema-compound-documents?utm_source=rss</guid>
|
||||
<pubDate>Wed, 04 Aug 2021 06:00:00 GMT</pubDate>
|
||||
<enclosure url="https://json-schema.org/blog/img/posts/2021/bundling-json-schema-compound-documents/cover.webp" length="15026" type="image/webp"/>
|
||||
</item>
|
||||
</channel>
|
||||
</rss>
|
||||
Loading…
Add table
Add a link
Reference in a new issue