W1siziisijiwmtqvmdyvmjkvmtuvmtkvmjkvmjqxl2htyw5zx2j1zxjzdguyx3nxdwfyzs5qcgcixsxbinailcj0ahvtyiisijmwmhgzmdajil1d?sha=e70f445e784e7667

Posts tagged with: indieweb

Only displaying matching posts originating from hmans.io. Show all?
In reply to: pants.epir.at/kcd764
Absolutely, even though in the current code, there’s a couple of pieces missing for it to fully work. #pants uses two separate channels for communicating across nodes: webmentions for immediately ...

@hmans.io How does #pants does the following thing? Would it be possible to let another blog software communicated with #pants blogs?

Absolutely, even though in the current code, there’s a couple of pieces missing for it to fully work.

#pants uses two separate channels for communicating across nodes: webmentions for immediately notifying other sites about new content, and polling other sites for new and updated content.

Webmentions are an open #indieweb standard and, even today, will happily work across #pants and, say, Wordpress sites, as long as the latter support it. I could probably support non-webmention enabled Wordpress sites by adding support for Pingback or Trackback, but I don’t really want to go down that route, since Webmention, a significantly simpler protocol, is set to supersede these.

When it comes to polling, the polled site (eg. a site you’re following from your #pants) currently needs to be a #pants site, too, as I’m simply loading its /posts.json resource. Adding compatibility with non-#pants sites mostly involves also supporting feed discovery and pulling RSS or ATOM feeds if /posts.json is not available. It shouldn’t be too hard to implement, but it also doesn’t have the highest priority right now.

Generally speaking, I’m trying to make #pants a good citizen, interoperating with non-#pants sites as smoothly as possible, but there will probably always be stuff that will only work 100% if both sites involved are #pants-based.

In reply to: jonasw.io/vct156
I totally want to move away from making S3 a requirement, but I’m on the fence regarding OwnCloud.

Wouldn’t it be nice to use #ownCloud for the image storage? I don’t know how complicated this would be to be implemented, but in the spirit of #indieweb, this would be a much better approach than #s3.

I totally want to move away from making S3 a requirement, but I’m on the fence regarding OwnCloud. The two primary goals are:

  1. keep the number of hard dependencies to a minimum
  2. make it possible to install #pants on cloud providers like Heroku that don’t have persistent file storage.

I’ll probably just shove things into the database in some way and leave it up to the administrator to choose a different data store if they prefer.

#WhatsNewInPants

#WhatsNewInPants

  • @mentions: You can now mention another user just like you know it from, cough, Twitter. Check it out: @hmans.io! Hooray! Note that this currently doesn’t do any checks if the referenced domain name is actually a #pants user, but your #pants will send the mentioned domain a Webmention ping (just like it will for any other link included in your post.)
  • Push tweaks: When you post something new, your #pants will no longer send pings to the users you’re following. This mostly means that for users that are not following you back, in order to push your post to their incoming timelines, you’ll need to @mention them like described above.
  • ATOM tweaks: Posts that are replies to other posts will now indicate this in your #pantsATOM feed.
  • Improved #IndieWeb standards support: the overall goal is to make #pants interoperate happily with non-#pants sites, so your #pants will now display incoming Webmentions from all sources (see http://hmans.io/oqq524 for an example of what this looks like.) Also, your posts are now fully marked up with h-entry microformats, allowing the #IndieWeb-enabled interwebs to fetch and process your posts in a structured fashion (example). If you’re interested in details on #IndieWeb, check out @indiewebcamp.com.

API Changes

In addition to all this, if you’ve been hacking around with the #pants API, please note the following changes:

  • The domain and slug fields have been removed from the post JSON data as they’re now pretty much obsolete. The post JSON still has url and guid, which should be enough to extract domain and path (slug) from.
  • The title, type and data attributes have been added to the post JSON data. I rambled about type and data for a bit yesterday; these fields don’t do much yet, but they’ll play a central role in a lot of things that are to come. title, of course, is the post title (which, as you know, is being auto-extracted from the post body.)

Enjoy!

Just like a human being, your software project needs to breathe.

Just like a human being, your software project needs to breathe.

When #pants is breathing in, I’m adding Likes, Reposts and other user-facing features, setting up the API so third-party clients can talk to your site, or changing internal protocols to #indieweb ones for improved interoperability.

When #pants is breathing out, I’m renaming things to make them easier to understand, refactoring my code to make it easier to maintain, improving how it deals with unexpected errors, or writing specs that I should have written a long time ago.

Just like a human being, it is important that the two take turns, and that you breathe out just as much as you’re breathing in. You can’t do one all the time, and I question the sustainability of continuously doing one more than the other.

In reply to: pants.monoxyd.de/tmo521

Und jetzt stelle ich grade fest, dass eine Art von Like oder so cool wäre. Also eine 1-Button-Lösung für “Habe ich gelesen, finde ich cool.” Weil ich würde gerne sagen: \o/, ohne dass als Post in meiner Timeline ganz oben stehen zu haben.

Likes kommen!

Likes kommen! Aber genau wie bei den “statischen Seiten” bin ich mir auch noch nicht 100% mit mir selber einig, wie ich sie implementiere, wobei ich gerade dank #indieweb eine ganz gute Idee davon bekomme.