Let's see what happens!
Every day a new post to see if Fargo is still working.
And the answer is...
Is Fargo still working?
On the Little Outliner support site, a user named Glenn asks if the docs, which were written in Fargo, will continue to work when Fargo stops working. The answer is yes. Dropbox is not needed for the hosting site. The pages are stored in Amazon S3.
It's July 1 and we're wondering if Fargo still works.
According to Dropbox the API was supposed to be turned off yesterday. But here I am in Fargo creating a new post in my test blog. So far it seems to be doing okay. I'm getting an error message in the console saying "Too many requests" but that's par for the course. It's been saying that for months. Never figured out why it's making so many, or if that's a problem with the API or what..
I guess the real test will be if this post makes it up to the server. Let's see.
Update: Yup. It's there. So maybe there's a grace period in the expiration? Or..?
This is a nice test of Fargo to see how it is working.
What a nice page this is!
The CMS is a very nice piece of software.
Let's see what we can do.
What do you think of Twitter's new polling feature?— Stephen Foskett (@SFoskett) October 29, 2015
I did a bad thing, I let the domain rsscloud.org lapse.
When I did that, all the rssCloud docs fell off the web. ;-(
We need them back, so I bought rsscloud.co. It isn't perfect but most of the docs now work.
I decided to fix the address in Fargo, rather than rely on pagepark to do the mapping.
So hopefully everyone will update their copy of Fargo to the current version, done simply by reloading the page.
I am going to try to publish this through my new server and see what happens.
Davey you have a very interesting little project here!
Damn if this isn't the cat's pajamas.
I get it now
Time Loves a Hero
But only time will tell
If he's real
He's a legend from heaven
If he ain't he's a sinner from hell.
This is an example of an outline
I have structured it deliberately using the outline structure.
There is no Markdown here, just outline structure and HTML.
This is a test: Scripting News.
The attribute is #flMarkdown.
If it's an outline, and markdown is turned off, we use the outline renderer.
That's what makes sense.
Intuitive not intelligent
It's intelligent enough. If there are no subheads it knows that this should not be formatted as a headline.
However if there are subheads then it assumes it's a list.
Here's a nice outline
A few interesting tweets
Melo feeling good about things. pic.twitter.com/LBXumBm0K5— Little Pork Chop (@Twittergram) July 2, 2014
Ygritte says I should try again. pic.twitter.com/GrbKPQMX7f— Little Pork Chop (@Twittergram) July 2, 2014
A list of things
Lawrence of Arabia
But then there's another paragraph and everything is back to normal. Until something appears underneath it then it becomes a headline again. You learn how to play with it, I guess.
I heard that when you type the term siigit into Fargo you get a weird Emoji character.
That's six hyphen digit. The trigger is x hyphen d.
Let's see if it happens here.
We're using Emojify in Fargo to do the rendering.
One thing you can do until we figure out what's going wrong is you can turn Emoji's off globally or on a single page. See the announcement page for Fargo 1.60 to see how to do it.
Perhaps this should be reported as an issue on the GitHub project?
I added a comment to a reported issue that says that'd gets screwed up in a similar way.
Outline is the most basic type in Fargo.
Here's a tweet inside an outline.
Today's Scripting News background image is rebeccapurple, a new web color. http://t.co/5VtNerMDAA— Dave Winer (@davewiner) June 26, 2014
Everyone at the World Cup Is Getting Laid, Thanks to Tinder. http://t.co/GZ3IQoIFmT— Dave Winer (@davewiner) June 26, 2014
Joe Moreno: [What's the Big Deal About Outliners?] http://t.co/bG3GRyj96O— Dave Winer (@davewiner) June 26, 2014
Scripting News: Note to press people re Happy Friends. http://t.co/3rSMrIpp4X— Dave Winer (@davewiner) June 26, 2014
Below is a tweet. Let's see if it renders.
There is trolling. And then there is Ann Coulter. She's like the Einstein of trolling. Respec— Farhad Manjoo 🥜 (@fmanjoo) June 26, 2014
This is a slide
This is a little text on a slide.
Comparison of advertising strategies at Quartz, Business Insider, and Forbes http://t.co/V39DpjQ00u— Zach Seward (@zseward) June 26, 2014
This is a little text on a slide.
Yet another slide
This is a little text on a slide.
Good night Gotham pic.twitter.com/QRwVjLIkg8— Bijan Sabet (@bijan) June 26, 2014
When I did the transition to the new format of Scripting News over the weekend, I decided for the moment not to change the format of the feed. However I will do it, eventually -- and it's almost certain not to work well in some feed readers, maybe most of them.
One of the reasons I wanted to give it a little extra time is to create a time for feed reader devs who care to make the small changes necessary to accommodate title-less items.
This is the feed for the noteblog. You probably should not subscribe to this feed because it will stop updating when the next transition happens. But it's an example of the kinds of items that will show up in the main feed.
This is my original linkblog feed, going back to 2010.
All the items in this feed are title-less.
If developers want to handle the coming changes in Scripting News these two examples should be enough to make these feeds work in your software.
I explained the changes, and the reasons in this March 9 post.
Here's how Chrome deals with title-less items. Not optimal!
And here's how River 3 deals with title-less items.
Feedly handles them a lot like Chrome.
An item may represent a "story" -- much like a story in a newspaper or magazine; if so its description is a synopsis of the story, and the link points to the full story. An item may also be complete in itself, if so, the description contains the text (entity-encoded HTML is allowed; see examples), and the link and title may be omitted. All elements of an item are optional, however at least one of title or description must be present.
Manila, the first CMS to produce RSS feeds, supported title-less items in feeds.
In 2006, Google Reader had gained dominance, and didn't support title-less posts. As a result Scripting News didn't look great in their reader, so there was pressure on me to change. At the same time Twitter came along, and fully adopted the idea of posts without titles, so I split my blogging into two pieces, one on Twitter and my linkblog, and the other, just the essays that appeared on Scripting News before. Scripting News, the first blog to have a feed, conformed to Google Reader's omission (a kind way of putting it) or bug (more fair). Scripting News became Google's idea of what a blog is. Ugh.
I felt this was okay as long as Twitter held promise for being a revolutionary Internet-scale notification service with a powerful API. But they've backed off that. Their service hasn't improved in a long time. I didn't realize how much I missed doing the intermediate-length posts until I started using Facebook regularly. But stuff I post there has no lasting value. So I need a better place for that kind of writing, so why not use my own blog? Of course that's the right answer.
I'm undoing the mistake I made in 2006. And that means you may either find that your RSS reader supports my feed, or it doesn't. I'm not going to let them hold me back. If you can't read my feed in their tools, then you can switch to one that works properly, read the site in a web browser, or don't read it at all.
I'm sorry it has to be this way, but reader developers have been deciding arbitrarily not to support an important part of the RSS standard. I want to use the feature, I was using it long before any of them existed, and it's easy for them to support. Just a little bit of thinking and a little bit of coding.