In the new Micropub syndication targets format, the uid field can be literally anything:

The uid property is opaque to the client, and is the value the client sends in the Micropub request to indicate the targets to syndicate to.

I use HTML (a Bridgy Publish link) as the uid… which breaks Woodwind:

This is vulnerable to XSS — although in this case a user can only attack their own browser, putting untrusted strings directly into HTML is not a good idea.

Woodwind should escape the uid in the template, and unescape when sending Micropub post requests.

Right now subscribed to all three of https://ben.thatmustbe.me, http://ben.thatmustbe.me, http://ben.thatmustbe.me/

woodwind=# select * from feed where id=66 or id=75 or id=87;
 id |        name        |          origin           |           feed            | type |        last_updated        |        last_checked        | etag
----+--------------------+---------------------------+---------------------------+------+----------------------------+----------------------------+------
 66 | ben.thatmustbe.me  | https://ben.thatmustbe.me | https://ben.thatmustbe.me | html | 2015-02-19 17:18:28.419858 | 2015-02-19 18:20:27.844713 |
 75 | ben.thatmustbe.me  | http://ben.thatmustbe.me  | http://ben.thatmustbe.me  | html | 2015-02-19 13:45:00.287542 | 2015-02-19 16:59:55.130761 |
 87 | ben.thatmustbe.me/ | http://ben.thatmustbe.me/ | http://ben.thatmustbe.me/ | html | 2015-02-19 18:05:16.210167 | 2015-02-19 19:10:08.398211 |

I tried installing this on an Ubuntu server and needed to first install the python3-dev package:

apt-get install python3-dev

example of a post that has <input> in the title and shows up an HTML form element!

https://reader.kylewm.com/?entry=https%3A%2F%2Fadactio.com%2Flinks%2F9738

So that the Back button brings you back to where you were, instead of reloading just the first page.

I added lazy loading to my h-feed of photos at https://jeena.net/photos and I added <noscript> for browsers which aren't able to deal with the javascript loading the images on demand by scrolling.

Sadly woodwind shows the html content of the <noscript>-tag instead which looks weird:

I'm not quite sure how to deal with things like this, it makes h-feed not as apealing for now. Perhaps the readers should get the full content from the permalink instead?

It'd be great if it could remember your place if there is an audio/video player.

aaronpk provides an example UI: https://monocle.p3k.io/preview?url=http://transportini.com/episode/1

We should save the form state before redirecting to micropub auth.

Thanks @snarfed for reporting!

On my site, 00dani.me, I've declared my authorisation endpoint like so:

<link rel="authorization_endpoint" href="/auth/indie" />

The correct behaviour when attempting to log in to Woodwind as 00dani.me would be, therefore, to redirect to https://00dani.me/auth/indie with appropriate parameters. Woodwind, however, incorrectly redirects to https://woodwind.xyz/auth/indie instead - presumably it just tries to redirect to /auth/indie, and defaults to the same domain.

Other IndieAuth clients, like https://indieauth.com and https://telegraph.p3k.io, correctly resolve my authorisation endpoint. Woodwind should do the same.

When a reply is added to the stack of new posts not shown, it counts as 2 posts. So even if there's only one reply post waiting to be shown, the link will say "2 New Posts".

Right now it looks kind of weird to see all the posts say "3 seconds ago" as I watch new ones stream in.

Maybe using a library like https://github.com/github/time-elements

This https://www.marcus-povey.co.uk/2015/03/05/fixing-flickr-gallery-again/ post keeps popping up as updated every time we poll Marcus's feed because of (apparently) randomly generated ids in the syntax coloring id=\"crayon-54ff585d54165409999404\".

We probably need to ignore markup when doing the update-check.

thus saith @tantek and I agree

Minor request: alphabetically sorting the tags at the top of the main page would be nice.

It would be nice if Ctrl+Return in the comment text area would send the comment like it does in Twitter.

maybe just make them non-editable

Reply posts in Known show up as if they were just ordinary notes in Woodwind (without an "In reply to..." link above them).

How replies from Known appear on Woodwind:

How replies appear on Known:

How replies from Redwind appear:

Sorry if this is a problem with Known and not Woodwind, but the reply link is properly tagged as u-in-reply-to, so I figured it was a parsing issue.

The buttons for syndication expect the names to be domain names, if they're not domain names then it looks quite odd:

Perhaps it would be good to at least have the name as an alt text so it would show up if the image can not be loaded.

replace Update with a refresh icon, and Unsubscribe with a red X (+ confirmation dialog).

separate Save so it's clear it applies to save changes to the feed (or just make the feeds immutable -- probably smarter -- see #17)

thanks @gRegorLove for the suggestions

Similar to aaronpk/webmention.io#47
I try to authenticate as https://wwelves.org/perpetual-tripper and it greets me just as wwelves.org

I'd like to publish the list of the websites I follow, for that it would be nice if one could download the OPML of the websites. This could be later used to import it in some other reader or instance of woodwind.

Posting a reply and the "Success" link appears, but it should really then clear out the reply box and hide it again.

For subscriptions that consistently fail, start backing off and checking less frequently.

When subscribing to https://elliottucker.net/

sqlalchemy.exc.ProgrammingError: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely) (psycopg2.ProgrammingError) can't adapt type 'FeedParserDict' [SQL: 'INSERT INTO feed (name, origin, feed, type, last_updated, last_checked, etag, push_hub, push_topic, push_verified, push_expiry, push_secret, last_pinged) VALUES (%(name)s, %(origin)s, %(feed)s, %(type)s, %(last_updated)s, %(last_checked)s, %(etag)s, %(push_hub)s, %(push_topic)s, %(push_verified)s, %(push_expiry)s, %(push_secret)s, %(last_pinged)s) RETURNING feed.id'] [parameters: {'type': 'xml', 'push_secret': None, 'etag': None, 'last_pinged': None, 'push_verified': None, 'origin': 'https://elliottucker.net/', 'push_topic': None, 'push_expiry': None, 'last_updated': None, 'name': {}, 'feed': 'https://elliottucker.net/feeds/all.atom.xml', 'last_checked': None, 'push_hub': None}]
[pid: 31348|app: 0|req: 11/11] 127.0.0.1 () {50 vars in 1090 bytes} [Mon Jun  1 07:45:56 2015] POST /subscribe => generated 0 bytes in 2464 msecs (HTTP/1.1 500) 0 headers in 0 bytes (0 switches on core 0)

cc @elliottucker, I'm not sure what's causing this yet!

Suggested by @benwerd in IRC http://indiewebcamp.com/irc/2015-02-10#t1423603439276. Thanks!

Ideally this would work regardless of which reader your friends-of-friends use, maybe they publish XFN links to the feeds they follow. But just within woodwind would be cool.

not all browsers support input type="url" and you need to do verification anyway.

http://existentialcomics.com/rss.xml currently has a post with the date wrong - set to Sat, 31 Oct 2015 00:00:00 PDT
This shows up at the top of my feed continually.
Suggested fix: when you read in a date form a feed, set it to current time if its in the future (which I think is what you do with missing dates)

I got a bunch of indieweb blog subscribed into woodwind. I log in with my own website.
I configured interaction to be based on IndiePub in the settings page.

When I try to reply from woodwind, I just see a "Failure" message without more explanations

is this error/behavior due to my Known site? anything I can do to test it more thoroughly ?

Collect reply chains (especially when we subscribe to all participants) so that you don't get these weird, out-of-order repetitious entries from a series of tweets

Example feed with videos: https://aaronparecki.com/tag/100daysofmusic

I, and I think others too, would be able to help fix bugs and perhaps commit some features too, but it is not really obvious what we need to get it started. I guess one needs some database and it seems to be written with help of some framework which I don't recognize, a couple of lines on how to start the app would help a lot.

Support importing of legacy OPML format for feeds. Allow individuals to 'upgrade' from RSS to HTML.

In the readme it isn't mentioned that redis has to run, if it doesn't you get some weird errors which are not very helpful.

Hi, I'm not sure whether this is the right place to ask, but @withknown suggested I try.

I am experimenting with indieweb using my domain vaviblog.com which is hosted by indiehosters.

I created an account at woodwind.xyz to see whether that would make life easier for sharing.

When I use micropub as my reply mechanism, I get failure with reply but success with repost. I get failure with starring too.

When I use configurable action URLs, using the model you suggest for Known, I get a 503 error for every single option.

Unfortunately, I have no access to the server logs. I asked the person who operates indiehosters and he said he could not see any 503 errors in the log.

Any suggestions as to how I might track down the problem?

I just noticed the "view posts from this feed" links on the "Feeds" page. It might be nice when viewing "Home" to have a similar link beside each post.

Two different feeds, I subscribe to both.

Just a suggestion:

Setting the h1 and the navigaiton ul to display: inline-block; line-height: 64px; vertical-align: middle; will make the navigation vertically 'center' with the logo. Sans the floats, the order of the elements would need to change too. It should wrap at lower resolutions automatically.

Somehow I think there is something missing in the requirements.txt because I get this error when I try to initialize the db:

➜ jeena@Lala woodwind (master) python init_db.py
Traceback (most recent call last):
  File "init_db.py", line 3, in <module>
    from woodwind import create_app
  File "/Users/jeena/Projects/woodwind/woodwind/__init__.py", line 1, in <module>
    from .app import create_app
  File "/Users/jeena/Projects/woodwind/woodwind/app.py", line 1, in <module>
    from woodwind import extensions
  File "/Users/jeena/Projects/woodwind/woodwind/extensions.py", line 1, in <module>
    from flask.ext.login import LoginManager
ImportError: No module named flask.ext.login

Any tips on how to get this working?

when subscribing to a site that has both h-feed and xml feeds, we should present the html feed first.

suggested by @tantek, thanks!

On mobile, I noticed some instagram photos weren't showing up full width. It appears to be because the "more from this feed" link gets bumped down into the content area depending on the length of the feed name.

I tested this bit of CSS to self-clear the header and it seems to work:

header:after { content: ""; display: table; clear: both; }

I have used WoodWind for a while. Recently I deleted my browser cache and cookies and wanted to use WoodWind again, but for some reason I cannot get authenticated. I'm not sure what is causing it. It was working fine, but I did update Known a few times with the most recent commit in Github.

Firstly after giving it my website (https://tinokremer.nl) it asks me to authenticate

Then this happens:

In my logs I see no errors. I'm not sure if this is caused by me or WoodWind.

have to implement support for https://pubsubhubbub.googlecode.com/git/pubsubhubbub-core-0.4.html#authednotify