From my archives... this is what the command center of a mid-1990s dialup ISP looked like.
Later iterations would be more advanced, but this is how it started. A natural progression and leap of faith from the multi-line BBS it replaced.
for just the price of a small silicon fab and injection molding equipment, we can deflate retro game costs to even lower prices
@pluralistic
"The problem with, say, Meta, is only partially that Mark Zuckerberg is personally monumentally unsuited to serving as the unelected, unaccountable, permanent social media czar for 3 billion people. The real problem is that no one should have that job. That job shouldn't exist.
We don't need to find a better Mark Zuckerberg. We need to abolish Mark Zuckerberg."
Cory Doctorow
This!
I made a website today, by installing Microsoft FrontPage 98 on a 26-year-old laptop. And that website is about golf simulators. Well, more specifically, that website is about two bookshelves that contain golf simulators.
Get to know the Golfshrine at https://netizen.club/~wildweasel - retro browsers welcomed!
I am finally getting somewhere with #uxn! There's no collision or anything, but you wouldn't believe how much work it was just to draw this.
Oh! A new Chemical Safety Board video!
This takes something which could have taken them 20 minutes while they watch Netflix and turned it into 2-3 hours of painful code review stretched across 3 weeks. It's easy for you to actually cost the maintainer MORE time than they would have spent doing it themselves.
But isn't mentoring part of being a maintainer? Shouldn't you expect to sometimes spend 3 hours in code review on something that could have taken 20 minutes. Isn't that important for onboarding new project members?
Yes and no.
This leads to two problems. First, you've forced the maintainer to do something they were probably intentionally delaying. While a bit of that is expected in the maintainer role (that's code review for you), one of the hardest parts of being a maintainer is time management, balancing code review with getting your own work done. It's precisely because these kinds of refactors look easy that it's easy to generate a flood of patches which DOS the maintainer.
This is a bit of a #subtoot but I'm going to say it anyway:
If you're a new person to any project, open-source or not, doing "maintainer work" of re-organizing the code-base isn't as helpful as you think it is.
Go ahead and re-read that if you have to. Yes, every single project has a backlog of that sort of work. This file should be there. That include crosses module boundaries. Yes, it's a mess. Yes, it needs to be cleaned up. No, you're not the person to do it.
What this says to me is if anyone anywhere is still using Twitter as a commercial promotion / news feed, they *should not do so*, because Twitter will be not only withholding your new posts from logged-out visitors, they will be doing so in a "silent"/misleading way. A user who gets one of your tweets and follows it to your profile, rather than seeing news, will see a random post you didn't select, *and will not realize anything is missing*. They may then assume you have no more recent news.
Something I didn't discuss above, but is interesting:
I mentioned Twitter-logged-out users can't view links to profiles. What I didn't mention is you can still *access* profiles— — *sort of*.
Imagine someone links you a tweet, and you click the there-linked profile logged out. If you access the profile in this way, following a link from *within* Twitter, it *will* show you the profile
*Inaccurately*.
The tweets will be shown out of order (popular first?), and pinned tweets will not be shown.
Trans woman, bisexual, someone's fiancée, forever a programmer, poly, and former total mess