James Fenn @james@is.a.horrific.dev
- Website
- https://jfenn.me/
- Horrific Dev
- https://horrific.dev/
- Unicorn Utterances
- https://unicorn-utterances.com/
Enjoys talking about software with other people that enjoy talking about software. Skeptical of blockchain, cryptocurrency, AI, and technological utopianism. he/him
Got around to publishing the JVM & Android targets for my multiplatform git REST API wrapper. I ran into a bit of trouble publishing specific build variants, but my poke-it-until-it-works development methodology appears to have succeeded!
Next on the agenda, I'll be implementing some form of request caching and improving its error logs...
I would say that about 30% of being an applications software developer is learning technical formalisms, maths, and reasoning skills. The rest is being so immersed in this garbage that you can sort of guess what most of it means.
should have my website show a message if you _don’t_ have an adblocker installed recommending that you get one
it sure would be nice if more people realized that the right to free speech does not at all give you the right to a platform
I wonder if all the emphasis on the importance of "having a code of conduct" hasn't just resulted in a bunch of communities only writing one so they can appear safe & miss the criticism, then failing to actually act on it when it counts or enforcing whatever the heck they want instead.
They're just as unsafe, except now it's harder for people to tell...
Well, apparently I've already managed to boost some bigoted racist arse (one of their more reasonable posts) without recognizing them. That's great. I feel great. This is all fine.
I realize it's too late, but at least I've blocked them now. And I'll ban their instance too, if they don't moderate effectively. I have no sympathy for your "broken federation." Get off my server.
You'd think an instance that *actually has a relatively fair code of conduct* might do the bare minimum of holding themselves accountable to enforce it...
I've just finished a new version of Attribouter (about screen library) with a major design makeover thanks to https://221pxls.com/
https://jfenn.me/projects/attribouter/
This also adds support for GitLab and Gitea, making it easier for projects on those platforms to use it - and for others to migrate away from GitHub, which continues to spew empty dialogue while ignoring their complicity in the widespread human rights abuses of their clients.
Admittedly, my insistence on moving has a trivial effect on the grand state of things, but it's the collective support of the OSS community that affords GitHub their dominance, and I can't justify supporting them any more than I need to.
Horrific.dev is still in the process of developing our hosting services, and I'm gradually moving all of my repos there as it becomes more scalable & we have an interface for public contributions + open membership. I haven't really been working on my open source stuff as much until recently, but I do hope to continue it in a space that lives up to its expectations and isn't representative of all the moral and ethical failings of the tech industry.
Microsoft is so insidious... they're worming their way into every major language community and are doing their absolute best to ingratiate themselves with the FOSS community while they continue to destroy computing for consumers
Just want to give a shout-out to Audacity, which as far as I'm concerned is the open source creative tool that actually achieves the promise of open source creative tools. It gets significantly better every release and releases every few months, and the UI gets better and better (the key thing most open source tools don't achieve). If you tried Audacity a few years ago or more and decided it was unstable or clunky to use, download the latest version. You might be pleasantly surprised.
Really though, I'm only ever going to use this library's npm package in conjunction with other JavaScript projects like 11ty.io, which will all be server-side anyway, so I guess I don't see this being a problem.
Admittedly, even 2.5 MB is a pretty considerable amount for how little it actually needs to do. I'm hoping this size can decrease in the future, though, as the Kotlin-for-the-browser ecosystem develops.
"What ecosystem", you ask? Heh, well...
NPM lists my git-rest-wrapper library's "unpacked size" at a worrying 31.4 MB...
The browser JS bundle is 2.5 MB. There's roughly 28 MB of unused dependencies included in the package. Which I can't get rid of. I'm not sure how to feel about this.
I mean, at the same time, it could be more...
there is nothing like profiling and patching the performance of my own code to make me feel both utterly incompetent and maybe kinda good at things at the same time
I also need to add some contributing docs, which will be... interesting, as there's no way for external contributors to create a PR in gitea without an account.
It'll probably end up being "send me a patch file", "push your changes to another remote & send me the link", or something along those lines... temporarily, until I get the time/energy to look at hacking some sort of public contribution interface onto our gitea instance.
Got around to publishing the JVM & Android targets for my multiplatform git REST API wrapper. I ran into a bit of trouble publishing specific build variants, but my poke-it-until-it-works development methodology appears to have succeeded!
Next on the agenda, I'll be implementing some form of request caching and improving its error logs...
The UX can be changed, right? Use short media by default, provide an alternative (some form of "expand" button, like in gmail's compose interface?) for longer posts... same with how articles work in Hometown (https://github.com/hometown-fork/hometown/wiki/More-content-types).
And besides, "the fediverse" doesn't bend to Mastodon's UX. Other software & instances (like https://writefreely.org/) already use long-form posts - and IMO Mastodon that should support them. Otherwise, it's bad UX.
Also, char limits are bad UX.
The *one* thing I've found troublesome about setting up Mastodon so far is the char limit; it's not a vital change, sure, but I *really* don't like being told my single paragraph is too short in the middle of a rant and having to split it into multiple sections just so it "looks nice" in the UI.
There was a PR to implement a char limit variable (https://github.com/tootsuite/mastodon/pull/5697) a while ago - but is there any drawback to it other than "the way our UX is designed"? Because I'm really not getting it.
Someone suggested "is.a.horrific.dev" as our fediverse domain a while ago, and I felt the need to switch from Pleroma to Mastodon (mostly for a cleaner interface - but also some accessibility reasons)... and granted it's a pain to switch identities *again*, but I believe it's worth it in the long run. After this, my account probably won't be moving from there for a while. Luckily, noone else is using this instance yet, so I'm the only one moving! (that made this decision significantly easier lol)
To conclude, err, to my 23 followers: I'm sorry for the spam & making you press another button. But yeah, follow @james please, it's worth it for the cool domain kthx
- Website
- https://jfenn.me/
- Horrific Dev
- https://horrific.dev/
- Unicorn Utterances
- https://unicorn-utterances.com/
Enjoys talking about software with other people that enjoy talking about software. Skeptical of blockchain, cryptocurrency, AI, and technological utopianism. he/him
