Open scripting opened 1 year ago
I added a section at the top of the page, with info pulled from the <head> section of the outline.
Also included the outline URL because I'm not sure I understand how the URL is constructed. Does it default to bsky.social? It seems to be able to find the outline even if I just say davew but it can also find outlines for people who use their own domains.
Here is the current logic for that user handle input normalization:
thanks. i figured that's what you're doing. ;-)
btw your code is easy to read.
most people's code -- not so much.
what i want more than anything right now is a way to get a user's profile info.
what info do we have available?
btw, the source:markdown element really contains markdown! I was surprised.
do you convert their internal format to markdown?
BTW, I just tried something that worked.
That's the source for blueskyreader as of last night being viewed as i view it when i edit, in the outliner (drummer).
do you convert their internal format to markdown?
Yes, their Post records are just plain text with "facets" (text spans with start/end offsets into the text with either Link or Mention information), which can be represented as Markdown without losing anything.
btw, just noticed that the feedlist looks a million percent better in feedland. you changed the title of the feeds? good move putting the user's name first.
This is what the prototype looks like now.
http://scripting.com/code/blueskyreader/?subs=davew.bsky.social
BTW, this is what the equivalent timeline in FeedLand looks like.
The diff betw this and the prototype is that this is not a prototype. :smile:
https://blue.feedland.org/?river=true&screenname=dave
Nice! I am now pointing to bsky.app proper for the links, instead of staging.bsky.app, now that the Bluesky team enabled it
A nice benefit of having souce:markdown is if I accidentally write something that makes sense in markdown, i get the benefit.
Another comparison for our discussion tomorrow. This is the All tab in my feedland.org news page.
BTW, the philosophy of FeedLand is that everything but your settings and password are publicly accessible.
So you can see my News page.
https://feedland.org/?river=true&screenname=davewiner&catname=all
It's helpful to see what this stuff looks like from the other side.
Another thing I'm thinking for for Bluesky and Mastodon.
In 2014 I made a product for Twitter called Happy Friends at happyfriends.camp. It worked all the way until April. Screen shot below.
It's a mailbox style reader for twitter. Already Twitter was too well established for it to gain much traction, but it might work now for these two systems, esp since they have incompatible APIs.
I'm looking for a first thing to put into the market that might have a chance of gaining some users, so we can build on that.
BTW, I also want to do the productizing for the RSS and OPML feeds you have produced. I think that's a very important piece, a foundation for a lot of software. Might not be necessary to support APIs beyond those two formats.
I just changed the name on my account to scripting.com by creating the TXT record, and it worked, and I was able to get my OPML file.
Good morning! I'm going to keep dropping notes into this thread.
Note that the display now includes pointers to the opml and rss data. Makes it easy to review. I kept getting confused as to where these things were.
Most urgent -- get info about the author into the feed. I'm going to make a proposal for how it should look.
BTW, for reference, I have an app called http://tweetfeed.org that generates feeds for tweet streams.
http://tweetfeed.org/davewiner/rss.xml
For some reason it's still running.
A bunch of friends use it, but it never caught on, like everything else.
The docs..
I was reminded earlier today that it folds threads. I am happy to share the code for this. It also supports source:markdown for titles. I think tweets should have titles as should posts on Bluesky. The convention would be if the first character in the post is a # then the remaining text on the line is the title of the post. That would be reflected in the RSS. That way feed readers which kind of expect titles (thanks to Google Reader) will do something nice with the post.
These little things will add up to textcasting. It's going to be a slog made up of lots of little affordances.
This is the URL.
http://scripting.com/code/blueskyreader/?subs=davew
And a screen shot..
I'm continuing to work on it.