fluffycritter

I tried LDN, it didn’t help at all unfortunately.

It’s the fear of a vestibular attack that gives me anxiety which causes a vestibular attack. These attacks last like two seconds. Having a thing that keeps me lane centered has stopped the vestibular attacks. If I have another big one I will definitely pull over.

I am disabled, unemployed, and live alone and have no other reliable access to transportation. What else am I supposed to do? Simply stop existing?

I am well aware that I am taking a huge risk. It is harm reduction. And as the main underlying issue is anxiety, simply having a safety net (or even the perception of a safety net) has significantly cut down on the anxiety.

The CD archive was actually published by an unaffiliated company that specialized in bundling up public data repositories onto CD-ROM. NMSU was never involved in the publishing of physical artifacts.

Wow. I ran this archive back in the 90s, when I was a student at NMSU and it was one of my ancillary duties when I worked part-time for the IT department. I wasn't a fan of OS/2 myself but I appreciated how much of a community there was around it and how excited people were to continue to use it. When I inherited it the website was put together with duct tape and paperclips (and Comic Sans), and the files were pretty inconsistently-organized.

At one point I spent a few months building a new website and tooling to make it easier to manage and then completely reorganized the archive, and while other students replaced the underlying code over the years (eventually replacing my not-very-great C++-based bespoke-CGI system with a much more robust PHP-based one), my design was largely intact, as was the file structure I'd established.

I'm kind of amazed it kept running for this long, but this is a personal end of an era for me. I still hold a lot of nostalgia for it and my time working on it.

EDIT: I wrote some more detailed thoughts on my blog. http://beesbuzz.biz/blog/14299-Hobbes-OS-2-Archive-An-end-of...

something something ipfs

Many years ago I wrote an article about this very issue (because I ran into it while debugging a service outage at 5 AM, which turned out to be something using select() when it shouldn't have): http://beesbuzz.biz/code/5739-The-problem-with-select-vs-pol...

I used a structure.io sensor (referenced in the text of the post). https://structure.io/

Hi, artist here. I also did an interactive installation work directly inspired by I Am Sitting In A Room. :) It's only had a single (prototype) showing though. https://beesbuzz.biz/art/1512-whatwesaidwillbe

You seem to be under the impression that IndieWeb is a formalized organization where the people operating under its banner are being paid by said organization.

In reality it's a set of shared goals, which a lot of the people disagree on facets of implementation and the like, and a collection of generally-agreed-to protocols that people can choose to support as part of interoperability with other websites.

I am fairly active in IndieWeb spaces and I disagree with others in these spaces all the time. I've also certainly never accepted any Google money (or any other sponsor) for my contributions, not that it's even been offered. This is the first I'm hearing of "us" being sponsored by Google.

I've seen plenty of material support from Mozilla (because there are several Mozillians involved in the projects) and Okta (for the same reason). But those aren't in any way signs that those companies are steering the decisions being made -- they're just offering things like hosting rooms and providing food at our mini-conferences and providing t-shirts and whatever (and those t-shirts, as far as I know, never have any sponsor logos on them).

Also, we take a more user-centric view of things; while we'd all like people to be on their own self-hosted websites and free of the big social networks and so on, we understand that it's not realistic to just ask everyone to jump ship all at once, and running your own web presence is not what most people want to do. It's much better to build bridges so that people can connect in whatever way works for them, and that's why there are services like brid.gy and so on which people run out of the kindness of their hearts, and paid services like micro.blog that try to make it easier for people to dive in without having to Do All The Things, and people who work on IndieWeb integrations for Wordpress and so on.

And I'm very grateful for things like brid.gy; most of the comments/responses I get on my website come in through that, via people on Twitter and Mastodon and occasionally Reddit. Sometimes I get webmentions from other IndieWeb users, but they're the vast minority. And same goes for private-post logins; most people log in via Twitter or Mastodon, and a bunch use my email-based login mechanism as well, and very few actually log in via IndieAuth. If I were to restrict my interactions to pure IndieWeb I'd have a very lonely presence.

Not to mention how IndieWeb sites already provide way more interoperability than any of these site.js things, while not being beholden to a single stack with a single design philosophy (or an asinine requirement that every site be run as a single tenant on a dedicated server).

Plus, some of us already have post privacy, allowing access via other IndieWeb identities -- as well as making the allowances for people to log in without having to run their own damn website.

IndieWeb principles are based on modularity, communication, community, and compassion. None of those are things I'm getting from Aral's latest vanity project.

Facebook is a pretty good example of how neither of those things actually help, and if anything only amplify the harm that comes to marginalized people who have good reasons to not use their real names or faces.

I'd argue that porn is better for you than most of these addictive websites, and certainly better than tobacco.

You cannot convince me that the addictiveness of social media is a good thing.

What I was trying to (clumsily) say is that when people develop "isomorphic" code they tend to forget that some of it runs on the client and some of it runs on the server and the interface between the two cannot be trusted.

Form validation is a common example of where things can break, like someone injects malicious data that's already been validated by the client-side code and then the server assumes that the code has already been validated by the client.

And if you don't even know which code is running where, that makes it even more dangerous.

Ah, thanks, force of habit. :)

Hi, if possible, could the link please be updated to point to the original post at https://beesbuzz.biz/blog/2934-Advice-to-young-web-developer... ? The Tumblr automatic crosspost isn't really intended to be the canonical version, and I wouldn't mind getting a server load test while we're here.

Thanks!

I had posted this to my own blog at http://beesbuzz.biz/blog/2934-Advice-to-young-web-developers and it looks like it was the Tumblr auto-crossposted version that got submitted here. That's unfortunate.

EDIT: I've updated the Tumblr version to make this a bit more clear.