@sun @wowaname @BeedleDave There were a bunch of Twitter users who threaten to jump ship but I bet most of them will abandon their accounts within a month. Most of them just hate Elon Musk, but for the wrong reasons.

But I wouldn't really care if BlueSky somehow manages to make a dent in Twitter's userbase given what Elon Musk plans to do with it (making it an "everything app" which to me sounds like Digital ID). Granted, BlueSky can still do the same, but I don't expect that to happen any time in the near future.

@xianc78 @wowaname @BeedleDave I actually think a lot of the people on this network should actually be on bluesky, it is a better network for them. Charitably, it has the "better moderation" that they demand. Uncharitably, they aren't built for and don't deserve freedom.

@sun @wowaname @BeedleDave I disagree. It's run by a company and these fedi leftists hate capitalism enough to avoid for-profit services like the plague. Best thing for them is to just have a whitelist of servers to federate.

@xianc78 @wowaname @BeedleDave they won't do that because they are children and need the moderation done for them

if you remember snouts.online, it was filled with the kinds of people who wound up on cohost. with cohost gone it looks like they're headed for bluesky but a few are coming back to fedi

@WALFTEAM I barely ever interacted with any of those pricks. I tolerate furries but not that kind

@sun @xianc78 @wowaname

And it seems to be sucking up most of the shitlibs, which I do not mind at all.

@sun @wowaname @xianc78 @BeedleDave

Certainly bigger than our micro-side of Fedi. We are not the great Fedi of 4 years ago

@wowaname @xianc78 @BeedleDave the name server and yes the actual purpose of bluesky is to be twitter 2.0 but with reduced legal liability for content while having effectively the same amount of control

@sun @xianc78 @BeedleDave it's called the "name server" in spec? i just wanna see how exactly they use it cus i'm curious how badly they fucked up. reminds me of matrix identity servers if it's at all similar

@wowaname @xianc78 @BeedleDave https://github.com/did-method-plc/did-method-plc plc literally is short for "placeholder"

@sun @xianc78 @BeedleDave thanks yeah i see it here too https://atproto.com/specs/did#blessed-did-methods but it also mentions did:web which relies only on standard dns, correct?

@wowaname @xianc78 @BeedleDave I am familiar with did:web but not how it's used in bluesky, it's possible my info is out of date.

@BeedleDave @wowaname @sun I thought Bitcoin Cash only exists because vanilla Bitcoin wasn't truly decentralized.

@xianc78 @BeedleDave @wowaname @sun bch has a long history at this point. Block size is generally cited as the main difference today. However, the original reason for bch was to avoid segwit (segregated witness) addresses. Block size came a little later. Today bch also has tokens and some smart contract functionality. Full disclosure: I own some bch and continue to buy small amounts of it when I am able.

@Rocket @xianc78 @BeedleDave @sun better answer than i had, thanks

@xianc78 @BeedleDave @sun bch exists because btc is "more like the gold trade" and tx times are slow. nothing to do with fixing any centralisation

@xianc78 @wowaname @sun

Sort of. bitcoin devs wanted to keep block size small so that anyone could run a node, then build services on top of it to facilitate higher transfer rates. BCC wanted to get those transfer rates *now* by just increasing block size and didn't want to rely on proprietary services for scale.

I saw segwit mentioned, haven't heard that term in a long time.

yo @BeedleDave! how's it been 😁 haven't seen you in a while! 👋

@wowaname @xianc78 @sun

@ehhh @wowaname @xianc78 @sun

Things have been pretty good. Stopped being a NEET and got a job. Also stopped drinking, went cold turkey and I recently hit my 1-year mark. Sobriety is great, so is having a normal job and a reason to get out of bed. Been pretty content overall, that's the main reason I'm not on as much.

Decided to get back into coding, so I made a leetcode account, been doing dailies and the weekend contests, already hit the Top 10% in contests, now I'm realizing if I had just focused on that when I got out of the service, I'd have been a senior software engineer when the COVID tech boom hit, and might have been a millionaire by now. Bit late to be trying to get into coding now though, doubt most companies would hire a junior in their mid-30s, especially in the current market.

But, when I was brushing up I did automate some workflows at work, and it made me realize that if I found the right *remote* office/admin job, I could automate most of it, and get to where I've got a lot of free time again.

Updating my resume this weekend, already found a couple jobs that would fit the bill, gonna start applying on the weekends, hoping it pans out.

@BeedleDave @wowaname @xianc78 @sun Oh nice nice. I never drink so uhh... Cool! 😁 non-drinking buddies!!

is leetcode like duolingo for coding? lol.

I've been learning Python recently as well. I don't have any plans to use it atm but at least I can read and understand what open-source python-based things can do now if they're not formulas for machine learning, lol. nice that you got a job in this current economy tho. nowadays it seems like winning the lottery is more likely than finding a job that you can actually keep and sustain. And because *we live in a society*, this job recess is spreading to areas outside of IT too. 😕

@ehhh @wowaname @xianc78 @sun

Sort of, though it's a little more serious, in that actual software engineers use them for interview prep, not just casuals trying to learn to code. The problems you're solving can be quick things you can solve in a few minutes once you start to get good, but can also take an hour plus especially when you're new to coding.

Nowadays strong leetcode numbers alone won't land you an interview by themselves, though during the height of the tech boom they could. But grinding leetcode problems will still help a lot with the types of problems you'll be asked to solve *during* the interview to gauge whether or not you know how to code.