gbl08ma
@gbl08ma
I'm a software developer; preferences (descending): Go, Svelte, TypeScript, C#. I built @pds.labeler.tny.im, jungletv.live, underlx.com, and more. Disillusioned with Android; open web FTW. Slightly into game modding. Sometimes I make music. I use Arch BTW.
I dislike how my list of ideas for blog posts is pretty much all about the impact of LLMs on my profession... ...except for that last one, but it'd need so much visual support it's probably best as a video, and at that point it gets into "requires too much effort" territory.
BTW you should know that pulling via the web UI is broken after publishing standard.site records
Sadly it fails on my particular website when it tries to process a specific post. I don't know enough Rust but to me it sounds you're trying to trim a string in a naive way that Rust is not happy with?
You're right, I think it's a logged error but it still pushes. In the meantime it has developed a new error when I try to push via the web UI. When I try it on the terminal the message is more descriptive and actionable... but shouldn't this be something lichen handles itself?
This is the result of resolving the relevant DNS record within the lichen-server container. I'm at a loss...
Hmm, weird... when I run this test on my local machine (not the container where I have lichen-server running), it **passes**. I don't have more time to investigate now but I think I'll have to rule out DNS issues on the machine...
No dice yet, new error message but it still sounds like it is attempting HTTP resolution / not ignoring the error it gets while trying HTTP resolution. I suspect this is a problem somewhere within tangled.org/ngerakines.m... but I don't know enough Rust to be able to quickly put up a repro case.
Also, I'm not sure if this is intentional (I suspect not, and I suspect it's kinda broken... it created folders for these on my instance...) the test websites I created on your official instance show up in the listing on my instance
Yeah that doesn't look right. The PDS remote thingy is failing to resolve my handle to my PDS and instead is just fetching my old wordpress website at gbl08ma.com. I think it is trying to do HTTP handle resolution, but my handle is set up via DNS records.
My #BandcampFriday haul. All over the place genre-wise, as usual. Feat. works by @deadposssociety.bsky.social, @nthercyte.bsky.social, @arikxu.bsky.social and others + the latest experimental music compilation by @brokecore.bsky.social (@zovi.bsky.social, @masr.bsky.social...) Links in alt text.
@illegal.trading there's a timezone handling bug on lyda.app. This happens in other places on the app where relative timestamps are shown, too.
Man, your music and videos are so cool but spamming (un)follows and likes is really uncool.
Nothing like a good old unscheduled server downtime to make me waffle about atproto internals to uninterested non-technical users in hopes of making them understand what the "Create a rotation key" in PDS MOOver does 😭
How are you keeping track of this? The impression I got months/weeks ago, from looking at the logs of my labeler, is that many or even most did:webs are broken in some way. Your stats don't seem to deny that 😅
"You can dismiss it," they say right as I find out there's no way to remove it without using third-party tools. So yeah, today was the day I started using uBO to "fix" the official Bluesky app. It is now joining the ranks of such great apps as Discord, etc.
I continue to annoy my friend with long-winded explanations of my ambitions for a decentralized approach to plc.directory. Keep in mind this is being sent to someone who barely uses bsky and who, I only realized today, didn't even know what did:plc was. I often wonder how people put up with me.
Does anyone know what are the rate limits on GETs from plc.directory? I don't see mentions to them in the spec nor in the API docs.
OK I just realized this message is gibberish to 99% of people, but hopefully this makes a bit more sense.
Not only does the official did:plc server implementation not check this, there are operations in the PLC that have duplicated keys, so I'll have to remove this check. The did:plc spec is "great": there are things it doesn't specify, and some of the things it specifies are not actually enforced.
On the did:plc front, I've been toying around with some ideas that are likely to be controversial. Some of the reasons will probably be valid, but I bet there is mostly going to be a lot of knee-jerking going around. Maybe it won't matter: I might never get this to a state I'm happy publishing.
*11pm takes 4 characters at best duh. I swear I didn't get my spreadsheet wrong
My haul this #BandcampFriday. This time it's too much for me to share individual links, go through my collection instead: bandcamp.com/gbl08ma Feat. work by @debiscomusic.com, @arikxu.bsky.social, @senpimusic.com, @theastonshuffle.com, @elke.cafe, @nthercyte.bsky.social, Kettama, Bad Suns and more
Saying goodbye to my old bio. It all still applies, but I wanted to pack more/different stuff in. One of these days I'll work on a better pinned post, too, and get a banner image like the fancy kids.
Within my bubble, I feel this is the state of ATProto decentralization as of late:
The other day, I grabbed a Bitwig Studio license for a pretty good price. I figured I could splurge a bit, considering I've spent more hours in DAWs than in most of the few full-price games on my Steam library/backlog. Now, if only turning this into a complete track was as easy as spending money...