litchralee

I'm glad you enjoyed reading it. This was basically an invitation to brain-dump my thoughts from this past week, in light of Bluesky's recent record user-counts, and also because I just finished reading the recently-published book Character Limit: How Elon Musk Destroyed Twitter, a multi-faceted chronicle of how and why it happened and who knew what and when. Check your local library if they already have it.

I also follow Mike Masnick on Mastodon via Bluesky bridging, and listen to his podcast on the topic of Trust & Safety. He's also the one who coined the term Streisand Effect, which I think makes him fairly well qualified to write banger articles like Speedrunning The Moderation Curve, which are examples of unintended consequences running amok.

To start, let's verify that Bluesky the app is indeed open-source. Yep, it is. But that's not the same as having all the machinery be open-source, where anyone could spin up their own, compatible service; maybe named ExampleSky. To be compatible, ExampleSky would need to use the same backend interface -- aka protocol -- as Bluesky, which is known as ATProto. The equivalent (and older) protocol behind Mastodon and Lemmy is ActivityPub.

ATProto is ostensibly open-source, but some argue that it's more akin to "source available" because only the Bluesky parent company makes changes or extensions to the protocol. Any alternative implementation would be playing a game of chase, for future versions of the protocol. History shows that this is a real risk.

On the flip side, Mike Masnick -- founder of Techdirt, author of the 2019 paper advocating for "protocols, not platforms" that inspired Bluesky, and recently added member of the board of Bluesky, replacing Jack Dorsey -- argues that the core ability to create a separate "Bluesky2" is where the strength of the protocol lays. My understanding is that this would act as a hedge to prevent Bluesky1 from becoming so undesirable that forking to Bluesky2 is more agreeable. To me, this is no different than a FOSS project (eg OpenOffice) being so disagreeable that all the devs and users fork the project and leave (eg LibreOffice).

But why a common protocol? As Masnick's paper argues, and IMO in full agreement with what ActivityPub has been aiming towards for years, is that protocols allow for being platform-agnostic. Mastodon users are keenly aware that if they don't like their home instance, they can switch. Sure, you'll have to link to your new location, but it's identical to changing email providers. In fact, email is one of the few protocol-agnostic systems in the Internet still in continued use. Imagine if somehow Gmail users couldn't send mail to Outlook users. It'd be awful.

Necessarily, both ActivityPub and ATProto incorporate decentralization in their designs, but in different fashions. ActivityPub can be described as coarse decentralization, as every instance is a standalone island that can choose to -- and usually does -- federate with other instances. But at the moment, core features like registration, login, or rate limiting, or spam monitoring, are all per-instance. And as it stands, much of those involve a human, meaning that scaling is harder. But the ActivityPub design suggests that instances shouldn't be large anyway, so perhaps that's not too big an issue.

ATProto takes the fine-grained design approach where each feature is modular, and thus can be centralized, farmed out, or outright decentralized. Now, at this moment, that's a design goal rather than reality, as ATProto has only existed for so many years. I think it's correct to say for now that Bluesky is potentially decentralizable, in the coarse sense like how Mastodon and Lemmy are.

There are parts of the Bluesky platform -- as in, the one the Bluesky organization runs -- which definitely have humans involved, like the Trust and Safety team. Though compared to the total dismantlement of the Twitter T&S team and the resulting chaos, it may be refreshing to know that Bluesky has a functional team.

A long term goal for Bluesky is the "farming out" of things like blocklists or algorithms. That is to say, imagine if you wanted to automatically duplicate the blocks that your friend uses, because what she finds objectionable (eg Nazis) probably matches your own sensibilities, then you can. In fact, at this very moment, I'm informed that Bluesky users can subscribe to a List and implement a block against all members of the List. A List need not be just users, but can also include keywords, hashtags, or any other conceivable characteristic. Lists can also be user-curated, curated by crowd sourcing, or algorithmically generated. The latter is the long goal, not entirely implemented yet. Another example of curation is "Starter Packs", a List of specific users grouped by some common interest, eg Lawsky (for lawyers). Unlike a blocklist which you'd want to be updated automatically, a Starter List is a one-time event to help fill your feed with interesting content, rather than algorithmic random garbage.

So what's wrong with Bluesky then? It sounds quite nice so far. And I'm poised to agree, but there's some history to unpack. In very recent news, Bluesky the organization received more venture capital money, which means it's worth mentioning what their long term business plan is. In a lot of ways, the stated business plan matches what Discord has been doing: higher quality media uploads and customizations to one's profile. The same statement immediately ruled out any sort of algorithmic upranking or "blue checks"; basically all the ails of modern Twitter. You might choose to take them at their word, or not. Personally, I see it as a race between: 1) ATProto and the Bluesky infra being fully decentralized to allow anyone to spin up ExampleSky, and 2) a potential future enshittification of Bluesky in service of the venture capitalists wanting some ROI.

If scenario 1 happens first, then everyone wins, as bridging between ActivityPub and ATProto would make leaps and bounds, and anyone who wants their own ATProto instance can do so, choosing whether they want to rely on Bluesky for any/all features or none at all. Composability of features is something that ATProto can meaningfully contribute to the protocol space, as it's a tough nut to crack. Imagine running your own ATProto instance but still falling back on the T&S team at Bluesky, or leveraging their spam filters.

But if scenario 2 happen first, then we basically have a Twitter2 cesspool. And users will once again have to jump ship. I'm cautiously hopeful that the smart cookies at Bluesky can avoid this fate. I don't personally use Bluesky, being perfectly comfortable in the Fediverse. But I can't deny that for a non-tech oriented audience, Bluesky is probably what I'd recommend, and to opt-in to bridging with the Fediverse. Supposed episodes of "hyping" don't really ring true to me, but like I said, I'm not currently an invested user of Bluesky.

What I do want to see is the end result of Masnick's paper, where the Internet hews closer to its roots where interoperability was the paramount goal, and the walled gardens of yore waste away. If ATProto and ActivityPub both find their place in the future, then IMO, it'll be no different than IMAP vs POP3.

Pew Research has survey data germane to this question. As it stands, a clear majority (79%) of opposite-sex married women changed their family/last name to their husband's.

But for never-married women, only a third (33%) said they would change their name to their spouse's family name. 24% of never-married women were unsure whether they would or wouldn't change their name upon marriage.

From this data, I would conclude that while the trend of taking the husband's last name is fairly entrenched right now, the public's attitude are changing and we might expect the popularity of this to diminish over time. The detailed breakdown by demographic shows that the practice was less common (73%) in the 18-49 age group than in the 50+ age group (85%).

However, some caveats: the survey questions did not inquire into whether the never-married women intended on ever getting married; it simply asked "if you were to get married...". So if marriage as a form of cohabitation becomes less popular in the future, then the change-your-family-name trend could be in sharper decline than this data would suggest.

Alternatively, the data could reflect differences between married and never-married women. Perhaps never-married women -- by virtue of not being married yet -- answered "would not change name" because they did not yet know what their future spouse's name is. No option for "it depends on his name" was offered by the survey. Never-married women may also more-strongly consider the paperwork burden -- USA specific -- for changing one's name.

So does this help answer your question? Eh, only somewhat. Younger age and left-leaning seem to be factors, but that's a far cry from cause-and-effect. Given how gradual the trend is changing, it's more likely that the practice is mostly cultural. If so, then the answer to "why is cultural practice XYZ a thing?" is always "because it is".

I've seen this idea in leeward areas of California wildfire smoke, and while it should work, the caution I would give is to either find a mask which has little air resistance when breathing through it, or to be mindful of that restriction and not try to go all-in on exercise. Masks are breathable and effective at intercepting particulate matter, but I don't think they're tested for the sort of heavy, rapid breathing from exercising. And the longevity of the filters under such heavy loads is unclear.

But it's certainly worth a shot. Just make sure the mask is still snug, since a loose mask will diminish effectiveness.

The American Lung Association has this to say:

If the day's air quality forecast is code orange [AQI of 101 to 150] or worse, adjust your plans for the day. Avoid long periods of activity outdoors. The health effects of pollution are worsened over extended periods of exposure, and by the deep, rapid breathing that comes with exercise. Stay away from high-traffic areas, and do not exercise near those areas. On really bad purple [AQI of 201-300] or maroon [AQI: 301-500] days everyone should try to stay indoors as much as possible.

Those AQI levels and colors come from the US EPA, and use a different scale than the India National AQI. However, having reached the "very poor" threshold under the Indian National AQI system, that would suggest that it's not advisable to go outside for any appreciable amount of time, including for jogging.

For anyone looking at Keygen Church, also see their adjacent project, Master Boot Record for computer metal.

In my homegym I have an AbMat foam pad which I also use as a knee pad. And while I think the thick foam would work outdoors on tougher terrain, it would not meet your criteria to fit in a backpack.

My other suggestion would be a scrap piece of horse stall mat, which are nearly solid rubber sheets commonly employed for homegym floors. This is what I use when working in my yard, for tasks requiring a lot of kneeling. Such a piece -- while heavy -- could be cut to whatever size you need, using a sharp knife or a jigsaw.

A mid-mount gearset is new to me. I wonder how the belt drive behaves when driven slower and with more torque than an equivalent setup using rear hub gears. On the flip side, the tighter integration with the motor could mean the motor can internally rev higher, to prevent lugging and keep the motor running healthily.

I am a software engineer by trade, so when I started cooking, everything and every tool was intimidating, because I had no idea how it worked nor what it was meant for. I knew nothing about knives besides not to drop one, didn't know the difference between a wok and a skillet, and didn't understand how oil creates a non-stick surface on a non-non-stick pan.

What helped me was a book that wasn't like a recipe or cook book, but something closer to a food and kitchen textbook. The Food Lab by Kenji Lopez-Alt goes into some excruciatingly scientific detail about the role of different kitchen implements, and then showcasing recipes that apply theory to practice. Each step in the recipes thoroughly describe what to do, and the author puts a lot of content onto his YouTube channel as well.

It was this book that convinced me to buy, strip, and season a cast iron pan, which has already proven its worth as a non-sticking vessel comparable to my old Teflon-coated pans. And I think for you, reading the theory and following some of the recipes might develop sufficient experience to at least be comfortable in an active kitchen. It's very much a chicken-and-egg problem -- if you'll pardon the poultry pun -- but this book might be enough to make progress in the kitchen.

Also, since it was published in 2015, it's very likely available at your local library, so check there first before spending money to buy the book. Good luck with your culinary development!

I'm fairly pleased with the direction the SacBee has been moving, with regards to their reporting of pedestrian and cyclist fatalities in the past two or three years. Their reporting on the Causeway expansion project and neighboring Placer County's sales tax initiative to fund road construction aptly pointed out that "just one more lane" is only short-term relief (with studies showing the relief is gone in 5 years max) and long-term exacerbates car dependency.

This is a refreshing perspective from a regional publication, and while it's unclear if they did so in response to the road safety crisis, or if their efforts created the necessary awareness surrounding the deadly roads in the area, the result is beneficial for moving towards long-term solutions that balance road user interests.

No one should be dying in the streets and roads of Sacramento, and it behooves the local and regional governments to attack the issue directly.

I was once working on an embedded system which did not have segmented/paged memory and had to debug an issue where memory corruption preceded an uncommanded reboot. The root cause was a for-loop gone amok, intending to loop through a linked list for ever member of an array of somewhat-large structs. The terminating condition was faulty, so this loop would write a garbage byte or two, ever few hundred bytes in memory, right off the end of the 32 bit memory boundary, wrapping around to the start of memory.

But because the loop only overwrote a few bytes and then overflew large swaths of memory, the loop would continue passing through the entire address space over and over. But since the struct size wasn't power-of-two aligned, eventually the garbage bytes would write over the crucial reset vector, which would finally reboot the system and end the misery.

Because the system wouldn't be fatally wounded immediately, the memory corruption was observable on the system until it went down, limited only by the CPU's memory bandwidth. That made it truly bizarre to diagnose, as the corruption wasn't in any one feature and changed every time.

Fun times lol

As there may be regional differences, you might want to specify your area. For example, ice cream in the UK doesn't have to meet the same requirements as in the USA, so oddities like cheap ice cream made with no dairy or cream is possible, using vegetable oil instead. Evan Edinger has a video on UK ice cream in particular: https://youtu.be/CfM7yZD0PlE