@inthehands because I feel strongly here: negative importance. I don't want people to consider length AT ALL when writing commit messages. I want accurate content and literally nothing else.
@inthehands tech has an *incredible* history of wide-open sharing of information and effort and it's a big part of why I really enjoy it. Just look at how much has been created because of open source software, for instance.
There are definitely problems, but every field has problems. And e.g. Musk-flavored issues are exceptional in a "literally nobody ever has had this much money and power this quickly" sense so I don't think it actually reflects on the field at all. Except maybe to say "open sharing allows abuse too" but like everyone knows that.
@molly0xfff@mkj yeah, and I think that's what most should do. Extremely cheap, generally migratable, and about the only enshittification risk is ICANN which is pretty acceptable. POSSE is great.
It is a shame POSSE social networking isn't a thing yet. Outside very small niches anyway.
@molly0xfff@pluralistic ah, yep, I missed clicking through to that link for some reason. Thanks!
I think my point still mostly stands tho. It's at the end, in a very large linked post, well after the main link's text claims Mastodon (activity pub / federation in general) solves the issue... when "the issue" is "account portability that can't be revoked when enshittified" which is absolutely not true at the moment. Though it may become true eventually, which puts it way ahead of most options.
@molly0xfff@pluralistic tbh if they're a POSSE-doer and that's the message... it would probably be good to get a mention of that in that post or any post it links to.
As much as I enjoy Mastodon, it's really not any better with regards to "ability to enshittify and take your profile" because accounts are linked to sites, and portability is cooperative instead of controlled by the account-owner. Any host that disables that cooperation locks you in just as much as twitter/blusky/email/etc.
@thomasfuchs not a brand, but I personally found "get a really huge one" to be a surprisingly-strong positive change. Partly because it got me to subconsciously keep random stuff further away from my moving hand, and partly because it was noticeable how much less attention it needed due to never hitting an edge.
@jenniferplusplus@malcircuit@frost monorepos are also pretty much all (gigantic) snowflakes, so stuff you learn in one doesn't transfer to any other repo (whether it's a monorepo or anything else).
If you learn to use package managers like a normal person, that knowledge works everywhere, including open source.
@jenniferplusplus@malcircuit@frost I have the displeasure of watching a company move to a monorepo, struggle with education, and then create tons of engineers who can't figure out how to do anything in open source despite needing to understand and modify open source libraries they use on a pretty frequent basis.
So they just *don't*, mostly. They hit roadblocks, have zero tools or experience they can use, and often give up or ship it anyway and label it as a known issue. :blobfoxnotlikethis:
@thomasfuchs I've even got scp aliased to it (with a few flags like for compression) because it does more, more easily, and more quickly, by default. It's just plain great.
I've got idiotically tiny scripts strewn all over to do small backups/copies and it saves me so much time and headache. E.g. it backs up my Switch screenshots in a couple seconds and auto-unmounts the SD card when done.
Slowly figuring things out here, and staking a claim on my username on what seems like a good host.I do a bunch of Go (at work), a bit of Rust (for fun), deeply enjoy teaching and learning, and looove that I get paid to work on open source.