Posted Saturday, June 20 at 2:11 AM (7 months ago)
Pushl v0.3.0 is now out. Changes since v0.2.14:
- Some caching fixes
- Updates to some antiquated terminology
Per the above, the main code branch1 is now called
main, and you include and exclude link
rel attributes with
--rel-exclude, in keeping with some long-overdue naming convention updates.
We’re all in this together.
Posted Tuesday, December 3 at 11:28 PM (a year ago)
Double-whammy release today.
Posted Sunday, December 1 at 9:10 PM (a year ago)
I’ve released a new version of Pushl.
Changes since the last version:
- Added support for tracking entry URL changes
- Finally got around to adding type annotations and static analysis
Posted Thursday, October 3 at 1:49 AM (a year ago)
I have now released Pushl v0.2.12. The following is new:
- It now respects
rel="self" when determining which URL to send a WebSub ping for
- You can now send self-pings using the
- Miscellaneous code cleanups
Posted Monday, September 23 at 9:33 AM (a year ago)
In trying to fix what looked like a bug in Pushl (which turned out to be a bug in one of the services I was pinging), I did a bunch of much-needed code cleanup and refactoring.
I also added the ability to ping the Internet Archive Wayback Machine for outgoing links if the target has changed (relative to the usual
Pushl will now also log warnings for two useful situations:
- An outgoing link generates a 400-class error (403/404/410/etc.)
- An outgoing webmention has a different canonical URL than what’s being pinged (improved since v0.2.8)
The way it handles canonical URLs is also now improved; if a page has
<link rel="canonical"> it will use that, otherwise it will use the final URL that is the result of chasing redirects.
Posted Wednesday, August 21 at 10:21 PM (a year ago)
I’ve released v0.2.8 of Pushl, which fixes an issue with Webmention and Pingback where it was over-optimistically setting the link target. It will also warn you if the link target doesn’t match with the actual page, so you can update your links accordingly.
Right now it’s a little spammy (in that it’ll tell you about redirection mismatches for all links, not just ones with a Webmention or Pingback endpoint), but the next version will address that.
Posted Monday, August 12 at 5:25 PM (a year ago)
Around a month ago a bunch of my webmention stuff broke on my site, and I just figured out what was causing it. Pushl was getting confused by the fact that I had multiple feeds which provided the same content, and some of them were in a no-webmentions context. The no-webmentions ones were getting processed first, which was preventing the webmention-context versions from actually being processed.
So, I fixed this bug by making the context part of what dedupes the actions.
Every time I work on Pushl I feel like it could use a major rewrite, incidentally. This is one of those times.
Posted Monday, April 1 at 11:29 AM (2 years ago)
I have released v0.2.5 of Pushl. The changes since v0.2.4:
- Improved the logging levels a bunch, making them more useful
- Added the ability to only send WebSub for feeds
The latter improvement makes it so that if your site is accessible from multiple URLs (e.g.
https, or multiple domain names), it won’t send multiple Webmentions to everyone with each possible URL. This helps to cut down on spamminess to sites which don’t detect multi-origin pings (such as most IndieWeb blogs or fed.brid.gy).
I also finally added a tools page to this website, to collect useful things that make Publ work better with other things. I also intend to add various useful quality-of-life things like an image cropping tool, and whatever else might occur to me down the road.
Someday I need to get around to making a proper “Features” page for this site, too. Someday…
Posted Friday, March 15 at 5:29 PM (2 years ago)
While trying to figure out some weird access patterns on the day-job site I had the realization Pushl wasn’t actually specifying a user-agent, so it was just coming through as the generic
aiohttp one, which isn’t very friendly.
Now it sends a reasonable user-agent by default, and this can be overridden by the
--user-agent flag if you want to for your own analytics or whatever.
Oh, and I had quietly released 0.2.3 a few days ago; there were just some minor internal changes to logging and also declaring Pushl as beta, rather than alpha, software.
Posted Sunday, March 10 at 6:25 PM (2 years ago)
I’ve done a bunch more work on Pushl to try to get it more stable. In particular, I’ve made it so that it will only recurse into feeds that are on domains that were declared in the initial requests, and I seem to have cleared up some cases which were causing it to hang and also added a global timeout which will, hopefully, prevent it from hanging indefinitely.
I do wish I could figure out what is causing the hangs when they do happen though. Oh well. Some discussion of the issue below the cut.
Posted Thursday, March 7 at 10:27 PM (2 years ago)
I’ve been working on getting Pushl much more stable and reliable, particularly around a persistent “too many open files” error I was having, which turned out to be primarily due to a fd leak in the caching routines. Oops.
Anyway, there’s also seemingly a problem with how
aiohttp manages its connection pool, at least on macOS, so I’ve disabled connection keep-alive by default. However, if you still want to use keep-alive, there’s now a
--keepalive option to allow you to do that. I’m finding that it doesn’t really improve performance all that much anyway.
This is feeling beta-ready but I’ll give it a few days for other issues to shake out first.
Posted Thursday, March 7 at 12:05 AM (2 years ago)
So, I just released v0.2.0 of Pushl. It was a pretty big change, in that I pretty much rewrote all the networking stuff, and fixed some pretty ridiculous bugs with the caching implementation as well.
The main thing is now it’s using async I/O instead of thread-per-connection, so it’s way more efficient and also times out correctly.
And oh gosh, I had so many tiny but critical errors in the way caching was implemented – no wonder it kept on acting as if there was no cached state. Yeesh.
Anyway, I’ll let this run on my site for a few days and if I like what I see I’ll upgrade it to beta status on PyPI.
Posted Monday, January 14 at 9:28 PM (2 years ago)
I ended up doing some more work on Pushl and have now released v0.1.7. The major changes:
- Did a bunch of refactoring to make the code a little cleaner and handle configuration more appropriately
- Added a configurable timeout for connections (which now defaults to 15)
- Added a
--version option on the command line arguments
Also, some suggested usage ideas below the cut!
Posted Sunday, January 13 at 8:48 PM (2 years ago)
It’s been a while since I’ve updated Pushl but today I released v0.1.6. It includes the following fixes:
- Now it supports Pingback as well as Webmention
- Improved the threading defaults and connection pooling
- Also checks entries for updates even if the feed didn’t change (in case something changed in the more text or page metadata or whatever)
Anyway, it should just be a
pip install --upgrade pushl (or
pipenv update) away.
Posted Saturday, December 22 at 1:35 AM (2 years ago)
While I’m fixing random stuff in Publ, I figured I’d finally fix some problems with Pushl too. Nothing major here, just:
- Stability: Fixed a bug where feeds that don’t declare links caused the worker to die before entries got processed
- Performance: Now we use a global connection pool (so connections can be reused)
- Fixed a minor correctness issue with archive feeds (which actually doesn’t make any difference in the real world but whatever)
Posted Wednesday, November 28 at 1:18 AM (2 years ago)
I just released Pushl v0.1.3, which adds some minor performance optimizations and a bug fix.
Originally I was hoping to have a major performance optimization, in the form of having rewritten Pushl from thread-per-connection to async operation, but unfortunately I ran into a bunch of problems with it. Mostly that I was running into a “too many open files” error and I couldn’t figure out what was causing a descriptor leak. I have the work-in-progress branch online if anyone wants to take a look at it.
Anyway, the reason I went down this route is because I added WebSub subscriber support to my fork of Feed-On-Feeds, which makes it so that WebSub-enabled RSS and Atom feeds will push their updates to your reader instead of having to wait for a polling interval.
You can read more about some of my other thoughts on a blog entry that quickly devolves into a rant, if you’re so inclined.
Posted Wednesday, October 10 at 10:41 PM (2 years ago)
I’ve gotten Pushl to the point that I’m confident in releasing it as a full alpha and having a cron job run it every 15 minutes. Whew.
I’ve also added some
h-entry markup to the Publ site templates so that hopefully the notifications appear at least somewhat reasonably elsewhere.
I really need to redo these site templates now that I have a better idea of how they go together. Also the quickstart guide could be a lot better.
Posted Monday, October 8 at 11:53 PM (2 years ago)
I finally got around to releasing a very rough prototype of Pushl to pypi. It only sends out WebSub notifications for now (does anyone even use those?), but I’ll work on actually implementing WebMention soon.
Also, recently someone pointed out to me fed.brid.gy which makes it easy to turn a static site into an ActivityPub source. At some point I’ll experiment with setting up Publ for this; it looks like it’s just a matter of adding a couple of additional route rules to Publ, so that will probably go into an advanced configuration guide if I ever get around to making such a thing. (Or it could actually be added to Publ directly but there isn’t much of a reason for that, IMO.)