“Starting August 23, 2024, goo.gl links will start displaying an interstitial page for a percentage of existing links notifying your users that the link will no longer be supported after August 25th, 2025 prior to navigating to the original target page.”
Are you washing up during eternal Caturday?
Do you watch the horror films and shows? Don’t forget to vote in the Fangoria #ChainsawAwards
Happy belated birthday to these two goofs. (During eternal Caturday)
Had a (fireball) blast running Joel and Andy of the Silver Linings Playback Podcast through some loosey goosey Dungeons & Dragons as we discussed the loosey goosey 2000 film adaptation Dungeons & Dragons.
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-
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.
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.
Well, it's no worse than before!
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.
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 bet! You can find today's updates to the code here on my git hosting.
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)!
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-
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 https://martymcgui.re/, 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.
"An IndieWeb Webring 🕸️💍" text flanked by left and right unicode arrow links.
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.
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:
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".
Agreed!
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.
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.
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...
Woohoo!
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!
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-
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).
This is now the official song of #caturday:
https://imanicoppola.bandcamp.com/track/clap-your-hands
I will not be taking questions at this time.
Are you a member of the 🕸💍 IndieWeb Webring? Everything is fine! We are up to around 450 active sites, with more than 250 of those appearing on the webring directory page!
Ha! Ha. Reader, you see right through me. Since the last IndieWeb Webring update, an afficionado of IndieWeb, webrings, and PHP who goes by Von Explaino (aka Colin) reached out about collaborating!
He posted about his own updates in Playing with IndieWeb ring's code, and I posted a follow-up with my interest, and he shared his fork of the codebase and posted some ideas for future work. Look at this lovely back and forth discussion between our IndieWeb-powered sites! You love to see it.
That all started in, =ahem=, JULY OF 2023. After a slow email exchange between a patient Colin and a very embarrassed and tired me promising to take a look any day now, I eventually apologized for not having the energy to work on the web ring at that time, and around September we stopped corresponding.
No! Well, sort of? This weekend I finally made time to reading through Colin's updates and additions, especially focused around the PHPUnit tests that he added for the basic database logic and site fetching and parsing and link-finding code.
The tl;dr is: I've incorporated most of Colin's updates, hooray!
Sure! You can find today's updates to the code here on my git hosting!
Oh! Fair enough. None of today's updates affect how the webring looks or works at this time. It's more like setting up support infrastructure around the way the webring works now to make sure that nothing breaks unintentionally during future updates.
Most likely! But all good stuff, I think. At the top of my list are:
Right, haha. 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).
I guess it was in early 2019 when Google announced they would be breaking thousands of development and test environments by making the ".dev" domain a thing (archive link to announcement).
Four years later they sold their entire Google Domains operation to Squarespace (archived).
And, yeah, I have two of these ".dev" domains registered and so this has now become my problem. And remains my problem! Here's the timeline so far.
I guess Squarespace intends to sit on my domains for another 5 days, hoping I will fall for their deceptive pattern and cancel the transfer?
Update 2024-05-10 3:15pm EDT: lol I tried their chat bot
Update 2024-05-13 11:10am EDT: still waiting
Continue to watch this space? I guess??
Anyway, you asked.
Are you peeking out during eternal Caturday?
The People’s Joker time
Sliced a little extra off the bottom in FlashPrint. Nice and quick and the result feels sturdy with both a GameBoy Advance and a GameBoy Color!
