Computers, Web, JavaScript, Stuff…
Following up on a fedi post, I made a website shell to display random article summaries/links.
https://gitlab.com/eroosenmaallen/towne-crier
Articles are input as text files, the a build script compiles them into JSON and puts them into the site; the repo includes a gitlab-ci script to publish the output to GitLab Pages.
I hope it might be useful to somebody.
After some configuration sadness, the CheerLights fedi bot is back up and running, now at @CheerLights@mastodon.art.
In a Fedi post, mention the bot or the hashtag #CheerLights along with a colour (blue!), and connected RGB lights all over the world will change together.
Remember, even when things seem bad, we are all connected.
After seeing several people ask about a tool to download their toots, I’ve started building one.
Masto-DL will archive all your toots into individual json files to grep and analyze to your heart’s content.
After seeing several people ask about a tool to download their toots, I’ve started putting together a tool to do just that.
Masto-DL will archive all your toots into individual files (json right now, yaml to come, more as needed/requested).
Continue reading “Initial Release: Masto-DL”My Fedi-Follow widget is ready for a full 1.0.0 release!
The widget provides an interface for Fediverse users to easily follow or share a url from their home instance. It’s the first stage in my plan to make it easier to integrate Fediverse sharing and following into other platforms, like WordPress or other site engines.
Continue reading “Full 1.0.0 release: Fedi-follow Widget”I’ve started work on my #Mastodon client library, #MastoBot.
Initial work has progressed well; I have wrappers for HTML methods and reasonable coverage of helpers for Mastodon API endpoints.
Continue reading “MastoBot”Bohemian Rhapsody played on old computer beeps
Bohemian Rhapsody played on old computer beeps
(found via Neil Gaiman’s blog, he found it at El Reg)
I’ve finally finished up the OpenID signup for Rosebleed. The workflow is what you’d expect – OpenID box on the login form, if the given URL isn’t recognized then it redirects to the signup form and prepopulates it with the sreg fields.
I did notice a strange behaviour in OpenID; I’m not yet certain if I missed it in the spec or if it’s left to one’s judgement (note to self: read the spec again)… Anyway, here’s what happens:
– Say I sign up with “roosenmaallen.com”. This site delegates to my ClaimID page, so the openid.identity response is http://openid.claimid.com/silvermoon82, and this is what I actually use to identify the user.
To my thinking, I should be able to log in using “roosenmaallen.com” (since that delegates to my ClaimID), or claimid.com/silvermoon82, or openid.claimid.com/silvermoon82. These URLs all end up at the same identity, so they should be equivalent — and that’s how I implemented it on Rosebleed.
I’ve noticed other OpenID-enabled sites handle this differently. On the OpenID Directory for instance, I first signed up as “claimid.com/silvermoon82”. I’ve gotten in the habit of logging in using roosenmaallen.com; but when I try that at OpenID Directory, I get an error message that my email address is already registered to my ClaimID URL.
So, barring finding that the spec keeps “equivalent” OpenID URLs separate, I think I’m in the right here; always open to feedback though.
Update [2008-03-19]: I’ve checked the spec, and as it turns out, I’m actually in the wrong:
So, to use www.example.com as their Identifier, but have Consumers actually verify http://exampleuser.livejournal.com/ with the Identity Provider located at http://www.livejournal.com/openid/server.bml, they’d add the following tags to the HEAD section of the HTML document returned when fetching their Identifier URL.
<link rel=”openid.server” href=”http://www.livejournal.com/openid/server.bml”>
<link rel=”openid.delegate” href=”http://exampleuser.livejournal.com/”>Now, when a Consumer sees that, it’ll talk to http://www.livejournal.com/openid/server.bml and ask if the End User is exampleuser.livejournal.com, never mentioning www.example.com anywhere on the wire.
The main advantage of this is that an End User can keep their Identifier over many years, even as services come and go; they’ll just keep changing who they delegate to.
I just came across an interesting post about energy savings based on the colour of a webpage (specifically, Google – but the idea applies everywhere): A black Google start screen? | Wired Gecko.
I’ve found other posts dating back to May of this year (The Numbers Guy) on the subject, so it’s really not a new idea.
The largest part of my doubt is the question of technology. In a CRT, it does indeed use more energy to display bright colours than dark (ref. DOE Energy Star Desktop Information). A CRT produces bright colours by directing an energy beam at the front of the screen; more brightness == more energy used.