Repost

Really interesting talk at #TechFast, and #Morph is enjoying having breakfast with us ☺

  https://twitter.com/anna_hax/status/1265908233769754624

 Bookmark

`@API` Guardian

Found this out today, via a colleague, as a good way for your Java library to expose information about the API stability / intent behind classes.

Recommended read: `@API` Guardian https://github.com/apiguardian-team/apiguardian

 Reply

Reply to https://github.com/spring-projects/spring-boot/issues/10452

FYI I've documented this at https://www.jvt.me/posts/2020/05/25/read-servlet-request-body-multiple/ based on https://stackoverflow.com/a/36619972/2257038 and https://stackoverflow.com/a/30748533/2257038 - this caches the actual ServletInputStream rather than just the bytes that are returned.

 Like

 Reply

 Reply

cat /etc/*release? Or are those files only Linux based?

 Repost

 Reply

Reply to https://lobste.rs/s/hwhptd/which_atom_rss_reader_do_you_use

I'm quite heavily into the IndieWeb movement, in which we've designed a new standard Microsub which allows for a slightly better API than "regular" RSS/Atom readers, as it allows for you to use different feed formats on the backend. It also splits between the client and the server quite nicely, so I can use Indigenous for Android when on the move, and Monocle when I'm on the desktop. The best thing about the standard, aside from allowing extensible feed parsing, is that I can use different clients to read it, instead of relying on a single provider - which I believe we've seen with some of the RSS/Atom readers around currently.

The server I use is Aperture, built and run by Aaron Parecki, and I subscribe to a mix of RSS/Atom, JSON Feed and Microformats2 feeds