Onion Information

Page Clicks: 0

First Seen: 04/27/2024

Last Indexed: 10/23/2024

Domain Index Total: 84

Marty McGuire Posts Tagged indieweb 2024 Thu Aug 29 Has the IndieWeb become discourse again? I recently read Has the IndieWeb Become Irrelevant from starbreaker.org . The post does a great job linking to and summarizing a spate of posts that I will call “people being mad at the IndieWeb”, while also being one of these posts. These posts accuse “the IndieWeb” of being elitist, exclusionary, overengineered, complicit, and unnecessary, among many other things. There are some common threads I noticed among these posts: None of them mention micro.blog ! They seem to attack a “straw person” version of the IndieWeb, where one is expected to read, follow, and implement over a decade of experimentation on the web. Micro.blog is real Folks that would like to try a turnkey website hosting service, where: you bring your own domain (or register a new one!) you can leave and take your content with you whenever you want requires no coding (and no plugins to configure, and no “files and folders”) offers mobile and desktop apps that let you post (and read) the kinds of content you want supports IndieWeb building blocks to let you follow and interact with other people via your own websites I don’t see eye-to-eye with its creator Manton Reese about everything, but micro.blog is a great example of a real world service that makes use of IndieWeb building blocks in ways that customers benefit from without having to build anything! The rest is wiki I think many of other complaints, from being “overengineered” to (paraphased) “POSSE makes IndieWeb complicit with the corporate web”, come from misconstruing the IndieWeb wiki at indieweb.org as the entirety of “being IndieWeb”. When I discovered indieweb.org (in maybe 2015?) I was intrigued and nearly instantly overwhelemed. Trying to absorb all the concepts there would be nearly impossible. Understanding and implementing all the techniques there is actually impossible. That’s because indieweb.org is not a presciption or a cookbook or an exercise plan. It doesn’t tell you how to “be IndieWeb”. It’s a collective memory of experiments, some successful and some not, from a group of experimenters that has changed greatly over time. For example, I find that criticisms like “f*ck the corporate web and f*ck IndieWeb for interoperating with the corporate web” don’t really hold up when a lot of that stuff doesn’t even work anymore . On corporate complicity Automatic POSSE , syndicating posts from your own site out to your profiles on social silos, only ever barely (and briefly) worked for Instagram, was turned off for Facebook a few years ago, and was all but destroyed for Twitter shortly after its last acquisition. backfeed - pulling comments and likes from these platforms to display on your own site - has similarly been blocked by technical measures. These were experiments that worked for a time. People used them for a time. That time has passed and the people have moved on. Some folks have replaced their Twitter usage with something like Mastodon, or Blue Sky, or Threads, and amazing people like Ryan have stepped up to help experiment with bridging personal sites and federated services . There is no “the way”, only “your way” People don’t have to move on for purely technical reasons. Even before Twitter closed their APIs, many in the IndieWeb community were shuttering their Twitter accounts and removing posts. They moved on from Twitter, despite all those documented pages on the IndieWeb wiki, because they didn’t want to use the web this way anymore . And to me, this is actually what “being IndieWeb” or “doing IndieWeb” is about: using the web in ways that fit your wants and needs, being mindful of when (and to whom) you give up control over your stuff and your connections. Figuring out how you want to use the web is a daunting task, to say the least! The IndieWeb wiki is full of interesting examples and ideas - but as a logbook of ways of using the web, it can be inscrutable. It was never intended that every way of using the web would be suitable for everyone. A collective memory is extremely hard to keep up-to-date and to signpost for navigation. Trying to rely on the wiki alone is a recipe for frustration. I freely admit that the community has fallen into some serious prescriptive traps over time. Like with tools like indiewebify.me that offer a checklist of implementation details, without accompanying reasons why you might want these features. This isn’t the first time this has happened, by any means, and it won’t be the last, but the criticisms of these tools and models do make their way back into the collective memory. (see: generations and IndieMark ) Talk with us That’s why the IndieWeb chat exists. It’s a place where real actual people, who are working to use the web in ways that suit them, are ready to help in whatever ways we can. We love to share what is (and is not) working for us, what we’re trying, and so on. More importantly, we want to help you find ways of using the web that work for you. # IndieWeb # discourse 🔗 August 29, 2024 at 2:16PM EDT • by Marty McGuire Sun Aug 25 🔐🕸️💍 Restored sign-in options for an IndieWeb webring Are you a member of the 🕸️💍 IndieWeb Webring ? Or have you wanted to be, but you couldn't sign in because it strictly required IndieAuth for sign-in? I was recently gently reminded that the IndieWeb webring at one time allowed you to verify your identity using an alternative sign-in mechanism. For instance, by making bi-directional links between your home page and your GitHub account, you can delegate the step of "proving" that you are the person in control of your homepage to GitHub, and let them worry about storing and checking usernames and passwords. This concept is called RelMeAuth (because it works by embedding links in your homepage let look like ). The original version of the webring would first check to see if your site specifies its own IndieAuth provider and, if not, would fall back to using Aaron Parecki 's indielogin.com , which handles checking for these rel="me" links to supported sites. It also supports sending codes to your email, if you prefer! So it used to work? Yeah! I, uh, broke it when I moved the site over to PHP some time ago . But it works now? It should! If your homepage has no IndieAuth server specified, but has rel="me" links to your GitHub or an email "mailto:" link, you should be able to sign in to the webring using those methods! It was broken for how long? 😅 it was fixed within a day of someone telling me it was broken! Please don't share any links to code- Here are the updates I added today to enable indielogin.com support . Some of it is a little hacky until indielogin.com is updated to allow the full client_id URL for the webring, but it works OK! Sigh, ok. Okay that's it, for now! Thanks for reading, imaginary interlocutor! As always, feel free to reply to this post on your own site, or feel free to drop me a line in the #indieweb chat (I’m schmarty there)! # 🕸️💍 # webring # indieweb # update # IndieAuth # RelMeAuth 🔗 August 25, 2024 at 4:32PM EDT • by Marty McGuire Wed Aug 21 ☑ RSVP'd to an event https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k events.indieweb.org post 25 Aug 2024 Sunday 8 00 AM -0700 Grand Stark Study Hall 509 SE Grand Ave. Portland Oregon USA IndieWebCamp Portland 2024 I'm going! Looking forward to spending some quality time with some quality IndieWeb folks! 💖 # IndieWeb # IWC # Portland 🔗 August 21, 2024 at 9:08AM EDT • by Marty McGuire Tue Aug 20 ☑ RSVP'd to an event https://events.indieweb.org/2024/08/indieweb-meetup-at-xoxo-social-2024-okVmgbkaps1w events.indieweb.org post 23 Aug 2024 Friday 11 30 AM -0700 Rogue Eastside Pub & Pilot Brewery 928 SE 9th Ave Portland Oregon United States IndieWeb Meetup at XOXO Social 2024 I'm going! Excited for my first in-person IndieWeb event in quite some time! # IndieWeb # XOXOFest # meetup 🔗 August 20, 2024 at 10:43PM EDT • by Marty McGuire Sun Jun 23 🕸️👉👈💍 Ordering an IndieWeb webring Are you a member of the 🕸️💍 IndieWeb Webring ? Perhaps one of many who noticed that the "previous" and "next" links were actually going to random active member sites in the ring? I'm pleased to announce that the "next" and "previous" links between webring member sites should now be, more or less, deterministic! For example, if you visit gRegor's site , scroll to the webring links at the bottom, and click "next", you'll be taken to a site like mine! (at this moment, it is mine!) From my site, if you click the "previous" link, you'll be taken back to gRegor's site! This should m- Wait, did you say "more or less"? Well, uh, yeah, good spot. At a high level, the update works like this: Each active member site gets a pseudo-random "sorting" number. For a given site, the "next" site is the one with the next highest sorting order, and the "previous" is the one with the next lowest. When you click on a "next" or "previous" webring link from a member site, your browser tells* the webring where you're coming from with a "referrer" header. If the webring recognizes the referer as an active member site, it'll look up the next - or previous - site in the ring to redirect you. Woah, woah, I see that asterisk Way to stay sharp! Referrer headers can leak potentially sensitive information, so over time browsers have added ways to restrict how and when referrer headers are sent between sites . Most of the time, the webring will only see the referring URL up to the first slash after the domain. For folks whose site on the webring has a path component, the webring won't be able to match it against most referrers. It's also possible that your site is configured to not send referrer headers at all - in that case, the webring has nothing to go on to figure out that the visitor came from your site. If the webring can't figure out where a visitor came from, they'll just get directed to a random active site. That feels kinda broken if you ask me Well, it's no worse than before! Isn't there a way to improve it? There is! Or... was. The first version of the webring included unique identifiers in the webring "next" and "previous" links for each member site. These unique IDs would have made it straightforward to figure out where a visitor is coming from. Oh, don't tell me- Yeah, I removed that feature last year . 😅 The emoji-based IDs were hard to manage, added messy unintended meaning, and made it easy to mess up the webring links (or spoof someone else's) when copy-pasting! You're going to link us to some code, aren't you? You bet! You can find today's updates to the code here on my git hosting . Thanks, I guess. So, what's next? I'm not sure! I feel like this update has the webring in a pretty good place. It's simple enough that I understand it and it works. I might look into some upda...