tantek!tell cdevroe take another look at https://indieweb.org/WordPress_with_Bridgy and see if it makes it any easier, and definitely speak up when you see steps that you've run into trouble with before
gRegorLove"we'll presume you've got the IndieWeb WordPress plugin installed with the following minimal set of sub-plugins installed:" then lists the webmention support for threaded comments plugin "technically not required, but recommended"
LoqiWordPress with Bridgy is a work-in-progress guide for how to setup your WordPress blog to work with Bridgy to both backfeed (have social media likes, replies, reposts show up on your original posts) and POSSE (cross-post your posts to social media) https://indieweb.org/wordpress_bridgy
LoqiWordPress with Bridgy is a work-in-progress guide for how to setup your WordPress blog to work with Bridgy to both backfeed (have social media likes, replies, reposts show up on your original posts) and POSSE (cross-post your posts to social media) https://indieweb.org/WordPress_with_Bridgy
LoqiWordPress with Bridgy is a work-in-progress guide for how to setup your WordPress blog to work with Bridgy to both backfeed (have social media likes, replies, reposts show up on your original posts) and POSSE (cross-post your posts to social media) https://indieweb.org/WordPress_with_Bridgy
miklbprobably, but I'm going with the precept that someone setting up bridgy with WordPress is going to want to POSSE to silos, and without knowing they need an mf2 supported theme, pull their hair out trying to figure out why bridgy isn't doing X
gRegorLovee.g. A list of 4 plugins as the minimal setup for WordPress with Bridgy... that alone isn't very user-friendly. Not trying to be critical, just saying.
LoqiGenerations in the context of the indieweb refer to clusters of potential IndieWeb adopters in a series of waves that are expected to naturally adopt the indieweb for themselves and then help inform the next generation https://indieweb.org/generations
miklbI apologize it came out that way. I had Quill as a pinned app, and this actually gives a little more flexibility. Will need to debug micropub at some point for use on my phone.
GWGmiklb: It didn't. I am really having a bad day today for non-Indieweb reasons. I feel like Indieweb stuff is something that I can control...I build it.
GWGI have the same problems elsewhere. My old mentor used to warn me you have to do things backwards and forwards to prevent misunderstanding, and there will always be the person who does exactly what you strive to prevent.
Loqiprivate posts refer to posts or portions of posts which are private to either the author or to a limited audience chosen by the author https://indieweb.org/private_posts
GWGtantek: My point exactly. I see why it was removed. I want to discuss putting it back together because so many people seem to not realize they are codependent.
chrisaldrichSomehow I managed to lose an hours' worth of documentation in the wiki because I didn't hit save. Sure sign that I should give up tonight and go to bed. Good night mush. Good night brush. Good night IndieWeb. Good night moon.
danohu, Hory, nitot, jihaisse, Pierre-O and [jeremycherfas] joined the channel
[jeremycherfas]petermolnar I wonder how you think it is best to reply to something someone said in a chat some hours ago? I wasn’t here when it was said, or I might have replied immediately, and everyone could have seen it in context. I suppose I could quote the original message in my reply.
Loqi[[jeremycherfas]] petermolnar I wonder how you think it is best to reply to something someone said in a chat some hours ago? I wasn’t here when it was said, or I might have replied immediately, and everyone could have seen it in context. I suppose I could quote the ...
petermolnarthe team chats tend to have multiple simultaneous threads going on and it's never really been an issue for the past ~30 years; you just need to learn how to follow. introducing threads will just add to the complexity, which is already bad with Slack imho, having all the images and stuff displayed inline.
sebsel[jeremycherfas] but that permalink is Slacks permalink. What happens when Slack goes out of business? Better to own your own permalinks. So that's why chat.indieweb.org
sebsel(also, there is a limit on how far your Slack Archive goes. 10000 messages I think? If our Slack has more messages than that, the link would probably die.)
[jeremycherfas]OK, sebsel, I see your point. And now I suppose I’ll have to find a proper IRC client for Mac. I used to use Adium, but gave up on it because it couldn’t handle iChat properly.
jeremycherfasThanks voxpelli. None of my friends or co-workers use IRC — heck, some of them won’t even use iChat — so I don’t think I need anything as easy as Slack for anything other than Slack. I’m not sure about paying. But the free tier also looks good. I’ll see how this works out.
sebsel(nice: I posted it on my blog via Quill, syndicated via Bridgy, and see that it worked via Loqi and IRC, so no need to actually check Twitter anymore)
LoqiBy using a WordPress blog on your own domain, you are already part of the IndieWeb. Below are some suggestions to help you get started with upgrading your WordPress site to support IndieWeb philosophies https://indieweb.org/Getting_Started_on_WordPress
LoqiGet started on the indieweb by connecting with the indiewebcamp community, getting a personal domain, a place for your content, and setting up your home page & other indieweb essentials https://indieweb.org/Getting_Started
voxpelliJekyll and static site generators are a bit more complex than eg. Wordpress as they consist of so many more standalone parts than eg. wordpress does
gRegorLoveLooks like Google Contacts got a bit of a redesign. At least an introductory tour slideshow. I think they're auto-merging duplicates now, or displaying them as such. Mentioned in one of the slides.
martymcguire[m]this would definitely make a good hosted service. i'm not currently up for taking that on from a support standpoint, but it seems worth doing!
tantek!tell KartikPrabhu can you tell if Feedly supports any IndieWeb building blocks? Like do they support subscribing to an h-feed? Or consuming WebSub notifications?
tantek!tell KartikPrabhu I added some more positive stub sections to /Feedly like Features, IndieWeb Examples, IndieWeb Friendly - could you take a look and expand? Thanks much!
chrisaldrichI've used Feedly off and on since the death of Google Reader. But have been using an "embedded" reader in my site via the PressForward plugin for WordPress for the past month and change.
tantekI think both of those (reader with webactions) are key to solving the ease of use of "reply" and "like" actions, making them as seamless as they are in silos
LoqiFeedbin is a feed reader that is available as a paid, hosted service or as free software you can run on your own site[1] https://indieweb.org/feedbin
tantekI mean I think I know what the answer will be but I kinda want to see if how fast it grows and if there are any time periods where I make net progress ;)
[jgarber]Hello, all! I’m reading over the Micropub spec’s “querying” section and thinking about editing UI. From what I can gather, a Micropub client can query a Micropub server for information about a _single_ piece of content with `q=source` and `url=<foo>`.
[jgarber]But what I’m wondering: is it possible to query a Micropub server for a listing of posts (perhaps of a particular type) so that a Micropub client might display a UI of editable content?
[jgarber]I couldn’t find that obviously spelled out anywhere in the docs and it may be beyond the scope of Micropub, but the thought crossed my mind and I figured I’d ask here for input.
tantekthat's a good start, once there's proof of concept that someone's actually bothering to do that, then it makes sense to talk about a more extensive protocol to do more, e.g. query for private posts
bearif someone wants to offer a feed they will (explicitly owning the admin tax) and if they do not then the consumer needs to own it by using something like superfeedr
LoqiThe Internet Archive is a non-profit organization that is building a digital library, including archival copy of much of the public web https://indieweb.org/Internet_Archive
Loqiarchive in the context of the indieweb refers to date-grouped (often monthly) sets of posts (AKA personal historical archives, a common form of navigation), but can sometimes mean archival copy, a copy of a web page made (often by someone other than the author) at a particular point in time https://indieweb.org/archive
tantekjgarber, note, if a feature is taking me too long, or is breaking things, and I have "no" time left to work on it in that session, I finish by commenting out anything "breaking", and leave in any silent partial implementation for future iteration.
tantekor if the source-in-progress is irrecoverably broken, then it gets copied to a "parked for mining" folder, and reverted to the live version on the site.
tantekthat way in the future if I decide to try building that feature again, I can see what I tried in the first attempt (and maybe come up with a better approach with the passage of time)
[jgarber]I’m looking back at the source for FrancisCMS given what I’ve learned in the interim since I wrote it and thinking it may be a contender for “parked for mining.” Evolution tends to win out over revolution on code projects, though, so I haven’t come to a final conclusion on that.
[jgarber]Like: "Is the thing I want to build a version of what I’ve got or is it something completely new?” That’s the major question I’m considering while brainstorming ideas.
tantekoften where there's a code pattern getting repeated (copy/pasted) and it starts to look just ugly / error-prone (or causes one) enough to make me think the time rewriting that *piece* is worth the time saved debugging errors from copy/pasta in the future.
[jgarber]For instance: FrancisCMS is a Rails engine. You use it by including it in _another_ Rails app and mounting it at a base URL. That’s cool and interesting, but not without its shortcomings. At the time, I thought maybe others might pick it up and use it on their sites. That seems unlikely for all kinds of reasons (none of which I’m upset about).
[jgarber]So then, do I carry that implementation detail slash tech debt and iterate or do I scavenge the code for the good parts and write myself a standalone Rails app that’s easier to maintain based on my current skill level.
bear[jgarber] that sounds like you are using this as a learning task, so the answer is "yes, do it" but start working on tasks not with the mind you are going to "create the best thing in indieweb EVA" but rather start it as solving immediate problems