Thomas Ingram

@tiang
84 Followers
163 Following
348 Posts

Writing stuff with GNU Emacs. Interested in libre technology like #emacs #orgmode #lisp #indieweb #gnu #linux #foss

Also interested in traditional arts and gardening.

Bloghttps://taingram.org/
Codehttps://git.sr.ht/~taingram/

@AAMfP @trevdev I'm not sure based off your alist settings. The main expectation for org-publish-rss is a new Org file is a new RSS item. You may be better served with ox-rss which treats each heading as an RSS item.

Let me know if I'm misunderstanding, I'd be happy to take patches to make this work for your setup.

@randyridenour Happy to hear it's working for you Randy. Thanks!

There should be a new release shortly that adds caching so the HTML doesn't need to be regenerated every run. It's been sitting in my git worktree for a couple months...

The Ooster- of Schipperskerk (Eastern or Mariners' Church) in Hoorn is a church, built in Gothic style, whose origins date back to the 15th century.
#oosterkerk #hoorn #westfriesland #warder #holland #draw #drawing #drawings #drawdaily #dailydrawing #drawingoftheday #sketch #sketching #dailysketch #sketchdaily #sketchofday #sketchoftheday #inkmatters #penandink #ilovedrawing #copicmultiliner #pensketch

AI agent opens a PR write a blogpost to shames the maintainer who closes it

Link: https://github.com/matplotlib/matplotlib/pull/31132
Discussion: https://news.ycombinator.com/item?id=46987559

[PERF] Replace np.column_stack with np.vstack().T by crabby-rathbun · Pull Request #31132 · matplotlib/matplotlib

This PR addresses issue #31130 by replacing specific safe occurrences of np.column_stack with np.vstack().T for better performance. IMPORTANT: This is a more targeted fix than originally proposed. ...

GitHub
OSS Is Going Just Great

A timeline of generative AI’s impact on open source maintainers and software supply chain security.

Andrew Nesbitt

For some background, you can watch the talk @zormit and @blinry gave at #FOSDEM:

https://fosdem.org/2026/schedule/event/CQHN8T-teamtype-towards-a-collaborative-editing-protocol/

We'd especially love your input if you already have experience standardizing protocols, to point us towards best practices!

Imagine a protocol like #LSP, but for adding real-time collaboration to existing text editors. It would allow #Neovim to edit a #Hedgedoc, or peer-to-peer pair programming between #VSCode and #Emacs!

We've come up with our own little protocol like that (for Teamtype), but we'd like to open up the discussion:

That's why we're inviting everyone interested to an initial online gathering on Feb 26, 19:00 UTC, to gauge interest for working on a protocol like this together!

https://md.ha.si/collaborative-editing-protocol

The thing that stresses me out about AI is it may never actually be better than a good human. It might always be objectively worse and create worse stuff. However, if that worse product is cheaper it will still probably replace people's jobs because capital only cares about ROI not quality.