Show more

@saxnot ah, they have since deleted the issues that were opened where they were asked to change the name, because gimp is a slur against disabled people and also has strong sexual connotations making it difficult if not impossible to deploy in educational environments

the maintainers pointed to the FAQ ( and basically fell into the "intent overrides all harm" fallacy.

they also argued on the "if you don't like it, fork it" argument, which is why we have GLIMPSE

This flight boarding was weird as heck. Basically nobody was at the gate waiting to be let in and so they got to group C (back of plane) really quickly, and then only a few of us got on. Then group D was called and it’s the usual madhouse. Was everyone just asleep at the gate or something?

I was led astray by docs and bad defaults. Mastodon auth works correctly now and only gets the minimal permissions necessary (and revokes itself as soon as possible so it doesn’t clutter your app list).

I’d get Mario Maker 2 but I still haven’t finished the first one

I ended up writing my own Mastodon mini-client which does the bare minimum of what I needed. Was a lot easier than trying to work with any of the existing libraries, as it turned out.

For some reason this isn't working with just a read:accounts scope, though, even though the API docs say that should be all it needs.

okay I think that it will work Good Enough for me to just parse out the host and see if can talk to it, and if so assume it's something sufficiently Mastodon-esque-enough to use as the identity broker

okay let me rephrase:

Given a WebFinger address like @user@hostname or a Mastodon/Pleroma/whatever profile like https://example.instance/@username, how can I determine if there's an OIDC/OAuth endpoint I can query in order to authenticate the user?

I don't care about posting or reading timelines or anything else, I just want to authenticate.

I mean really my goal is to find an OIDC/OAuth endpoint that I can authenticate against, and I don't really care what the server is. But for some reason Mastodon devs are hesitant to add a discovery URL to profile pages, even though that would make a lot of federated identity stuff WAY easier.

and, contrariwise, is there some way to determine from a profile URL like https://example.instance/user/username or https://example.instance/@username whether it is in fact a Mastodon/Pleroma/whatever profile? like I don't see any suitable <link rel>s or whatever and I don't want to rely on parsing the Server: header.

Okay so if I'm given an address in the form of @username@hostname is it safe to assume that it's a Mastodon/Pleroma address and there should be an OAuth endpoint at hostname/api/v1/instance that speaks something similar enough to Mastodon that I can use it for basic authentication?

asking for a friend (the friend is me)

The one and only time I'm engaging with this Gab shit 

can people maybe... not put difficult-to-parse abbreviations in their CWs? I see things like "ec" and stuff and it's an extra step of trying to figure out what is meant

Well, this trip sucked as a trip but at least I got a lot done on Publ. I have private posts now! Just need to do a couple little tidying up things before I can release the next version.

wow that was a lot of friend requests holy heck

oh heck, there's a circular dependency in computing the paginations and screw it I'll deal with this later

oh, turns out I'm already doing the more efficient pagination thing I was thinking of, GO FIGURE. so yeah simply extending the pagination later will be helpful

I guess another approach I could take is to have the client-side filtering stuff keep on following pagination until the entry list is full, and then change to a different (and probably more efficient, frankly) approach for computing the pagination as well.

Show more
Queer Party!

A silly instance of Mastodon for queer folk and non-queer folk alike. Let's be friends!