Blog aggregator for the Recurse Center community! Just add your blog and the Blaggregator Bot will share any new posts with your eager readers in the #blogging channel on Zulip.
Blog + aggregator = blaggregator. Also inspired by xkcd.
Add your blog to your profile here: https://blaggregator.recurse.com (RC login required).
During her batch, Sasha (W '13) noticed that her peers were all blogging about their work at the Recurse Center on their individual blogs. It was really cool to see what they were working on and thinking about!
But the challenge was hearing about it: many people had just started their blogs and didn't have an audience yet. Some folks would post about their new posts in Zulip, some on Twitter, and some were shy and wouldn't spread the word at all. There was all this great work going on, but it was scattered across the internet and hard to find.
Blaggregator puts all this awesome work in one place, and automatically shares your work and creates a Zulip discussion thread. You now have a built-in friendly audience, and we get to see your awesome work!
Go here, log in, and go to your Profile in the upper-right corner.
On Blaggregator's next crawl, your two newest posts will be shown
(You'll see a vestigial feed of recent posts. The original concept was to discuss the posts on Blaggregator itself, to be a less noisy environment for alums than Zulip, but Zulip is much more lively)
The Recurse Center staff wishes to keep the list of people attending the Recurse Center private. So you are required to authenticate with your Recurse Center credentials
If that ever changes (for instance, to surface the best posts that are coming out of the Recurse Center to show off what we're working on) you will be given lots and lots of warning to decide how you want to participate.
Once an hour, the crawler checks all registered blogs for new posts. New posts are displayed on the main page and a message is sent to Zulip.
See below for how Blaggregator defines "new" posts.
If you published it less than an hour ago, hang tight: it'll show up when the crawler next checks the registered blogs (as of this writing, hourly).
Open their profile page, https://blaggregator.recurse.com/profile/<id>/,
where <id> is the number in their recurse.com/people/<id> URL. Next to each
of their blogs that is "Active", click "Turn off". Crawling stays off until the
owner edits the blog or adds the feed again.
So considerate of you to ask! Blaggregator already limits itself to posting only two new posts per crawl, for exactly this situation, so don't sweat it too much.
"New" is defined as a post having a new URL AND a new title. Blaggregator does not consider timestamps. If you need to change both, you could change the URLs, wait until the next crawl, then change the titles. But again, the worst case is two new posts.
If you posted more than two posts since Blaggregator's last crawl, it only Zulips about two of them, but all of them will appear in the (vestigial) feed on the live Blaggregator site. This also applies if you're adding a new blog with many past posts—only the last two will be Zuliped.
No problem! RCers usually enjoy reading non-technical posts by others.
But, if you like, you could tag or categorize your relevant posts and make a separate RSS/Atom feed for them. Most blogging software has separate feeds for different categories/tags.
If you use Wordpress, for instance, categorize all your code-related posts "code", say. Then your code-specific RSS feed that you should publish to Blaggregator is: http://yoururl.com/blog/category/code/feed/
Yes! Find your personal authenticated URL in your profile.
Sasha was the initial author. Puneeth is the head maintainer.
A bunch of other recursers have contributed. You are welcome to contribute as well!
Yes, that would be great! This is a project by and for the Recurse Center community. Help make it more awesome!
There's a very generic and high level list of areas that could use some help and a bunch of specific open issues.
Look at the developer documentation for help with setting up your development environment.
Before implementing a major contribution, it's wise to get in touch with the maintainers by creating an issue (or using an existing issue) to discuss it.
It's a Django (Python) app, with some Bootstrap on the frontend. It's deployed on Heroku using their Postgres and Scheduler add-ons. Check out the code here.
Don't let the perfect be the enemy of the good. Your posts don't have to be long, groundbreaking, perfect, or full of citations. Short, imperfect, and published always beats unpublished.
Don't let the perfect be the enemy of the good. Just get something up and resist the urge to fiddle with it. Use Tumblr if you have to. Just start writing!
Consider starting your own Iron Blogger challenge. Participants commit to writing one blog post a week, and are on the hook for $5 if they don't post. The pot can be used for a party, donated to charity, or donated to a charity the group hates (added incentive to hit the publish button!).
The Fall 2013 batch ran a very successful Iron Blogger program. Emilia Lazer-Walker wrote a very nice article on how it worked.
Copyright © 2013-2026 Sasha Laundy and others.
This software is licensed under the terms of the AGPL, Version 3. The complete license can be found at https://www.gnu.org/licenses/agpl-3.0.html.