Onion Information
Posts tagged 'update' - Marty McGuire
Posts Tagged update - ππΈοΈπ 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 r...
Onion Details
Page Clicks: 0
First Seen: 04/27/2024
Last Indexed: 10/23/2024
Onion Content
Marty McGuire Posts Tagged update 2024 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 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 updates for the directory or the site layout, or help surface more information about member sites, like whether they advertise RSS feeds. 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 π June 23, 2024 at 7:51PM EDT β’ by Marty McGuire Sat Jun 15 π€βπΏ Gardening an IndieWeb webring Are you a member of the πΈοΈπ IndieWeb Webring ? Perhaps one of many who have been confused to discover that member sites are not automatically removed when the webring links disappear from their site ? I'm pleased to announce that the webring will now be self-gardening! Webring member sites th- Hold on, links to what now? That-... is actually a good question! In order for webrings to work, member sites have to link to one another, usually through the webring itself. When you sign in to the πΈοΈπ IndieWeb Webring, you see this prompt on your dashboard page: These links should be copied and pasted into your site so that they appear on the page that matches your webring sign-in. For example, I sign in with my homepage http://martymcgfuraocsgy2a25btl5srhifcdud6m4eiphz2mq6fafttwh7qd.onion/, so I put my links to the webring on my homepage. They look like this on my site, but you can style them up to look like anything you want. The basic deal for most webrings is that, in order to receive incoming traffic from other member sites, you need to also display links back to the webring so a visitor can continue on their journey browsing sites from the webring. If that's the deal, then when a member site goes offline, or removes the webring links from their page, the webring should no longer direct visitors to that site. The IndieWeb webring tracks whether a site is "Active" or ... "Not Active" (ahem, Inactive). Active sites can receive traffic from webring visitors and, if you choose, appear on the Directory page. Inactive sites... can't do those things. As the owner of an webring member site, you can sign in to the webring and your Dashboard page will show your site's current "Active" / "Not Active" status and the results of the most recent attempts to check your site for webring links. If you've made changes to your site, there's a "Check links now!" button on the Dashboard to scan for them again. Okay that's enough background, I think. Right, thanks. But actually no, there is more. Initially, Active status on the webring kiiiiind of worked like an honor system. The first time you successfully sign in, your site is added to the webring and set to Active. From that point on, there were only two ways for your site to get marked as Not Active: If you clicked "Check links now!" while your site was offline or didn't have webring links on it. OR if I ran a "gardener" script that checked the webring links for one or more sites. Since the webring came online in, um, 2018, I've only received a handful of nudges from folks who have been willing to track me down to the IndieWeb chat and complain. That led me to think this honor system was "okay" or "at least not so bad that folks are willing to jump through hoops to bring it to my attention". That's definitely enough background. Agreed! So what's new? Well, the honor system days are over! Which should be good for all webring member sites, I think. I've built a little automated gardener that will periodically check member sites for their links. It's designed in a way that trends towards polling member sites about once per month. For a new member site, it basically works like this: about an hour after you sign up, your site will be checked for links. If they're there, the gardener will check again the next day. It will check again a few days later, then a week, then two weeks. Finally, as long as the links are there at every check, the gardener will only check once per month. What happens if the webring links disappear from my site? If the gardener finds that an Active member site has gone offline or lost the webring links, the site is marked Not Active. It's checked again the next day, then a few days later, then a week and then two. Finally, the Not Active site will be checked once per month for 3 months. If the site stays Not Active that whole time, the gardener will stop checking and the site owner will need to sign in to re-check links manually if they want the site to become Active again. What happens if I put the webring links back on my site? If the gardener finds that a Not Active member site has their webring links back, the site is marked as Active and the schedule resets. The gardener will then check it the next day, then three days later, then a week, then... Okay, got it! Woohoo! Why now, though? Oh dang, that's a good question. I've found the energy and space to start working on the webring again, including some possible projects like those I listed in my last update . Before jumping into any of those, though, I want to feel like I can "trust" that the webring is taking care of itself and its visitors. That means not sending folks to sites where the owner changed their mind about being a webring member or, worse, lost sites , and keeping track of active sites on its own! Can we see the code? Sure! The bulk of the updates are here on my git hosting . As with most things webring there's a little bit that's well thought out and some attempts at rigor followed by a rush of throwing things together when it appears near working. I'm open if folks have suggestio- Wait, I didn't actually want to look at code! I put some words in your mouth, there, yeah. Sorry. π Okay! That's it for now. 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 π June 15, 2024 at 2:27PM EDT β’ by Marty McGuire Sun Jun 9 An absentee webring steward returns Are you a member of th...