I just officially migrated my account over from tech.lgbt to here! so apologies to anyone who decided to unfollow me on cryptid.cafe and is now following me again
I don’t know much about DAWs but I’m pretty sure that trackers are the vim of the DAW world. like they’re super technical and hard to learn but really powerful and have a small, nerdy following
(context: I’m making a webapp that lets you do more powerful searches in subreddits like r/GoneWildAudio that include tags like F4F. my webapp can parse the tags and filter stuff out, like anything that’s M4* or *4S)
If I make this more user-friendly and expose all of the filtering options to the UI, would any of y’all be interested in using it?
I’m trying to decide if I’m okay with leaving this pretty arcane for my own use, or if it’s worthwhile for me to clean it up and post it publicly
I just officially migrated my account over from tech.lgbt to here! so apologies to anyone who decided to unfollow me on cryptid.cafe and is now following me again
@drawnto ooh omg really? I didn’t think anyone would be that interested. so far everything is pretty arcane because I’ve just been making this for me, but would you be interested in using it if I make it more user-friendly?
also I could show you the GitLab that I have right now if you want (it’s private but I could make it public) if you’re feeling up to reading my mostly-uncommented code lol. and I could explain how to use it in its current, rough state
@OctaviaConAmore yess omg I was so tired of all of the F4M on r/GoneWildAudio (and when it’s not F4M it’s usually M4F) and I was so happy to have found it! it’s such a nice little community. tbh you’re the first being I know of who also knows about that sub!
also all of the CSS and HTML is handwritten and Lucifer herself must have blessed me with good computer-touching because I have no idea how I managed to make this look even half-decent
it wooorks! I can not emphasize enough how little I know what I’m doing lol, and yet look at this. I made this. how the fuck did I make this?
so, I haven’t exposed these options to the UI yet, but this thing fetches Gone Wild Audio posts through the reddit API, then parses the tags and automatically removes anything that:
the tag parsing is very very robust and can handle a lot of weird edge cases (including multiple tags! like F4M and F4A in the same post). it paginates lazily (fetching more results from the reddit API as-needed) but it can also navigate to any arbitrary page, and gracefully handles if the user navigates to a page that’s out of bounds. it also keeps a cache of the results of its API requests so that it can avoid the speed penalty of constantly talking to reddit
@liese omg my partner Rowan is always talking about how much she loves Elixir. she started by learning Erlang and loved that language and then moved to Elixir
and tbh I have really similar thoughts about JS: to me it feels like this cursed agglomeration of cludges in a trenchcoat, that now has been molded vaguely in the shape of a modern multi-paradigm scripting language like Python or Lua. although it’s definitely much better now than it was before, because I feel like the JS community has (as much as can be expected) figured out how to work around the terrible footguns baked into the language
to me JS is the language that you use because you have to. because you need something from the ecosystem, or it has to run in a browser, or etc. it’s definitely not a language that you go out of your way to use (except for Node people, apparently lol)
also I’m ngl I’ve had such a hard time wrapping my head around how OOP languages are meant to be used. not nearly as much as with functional languages but I still can’t wrap my head around, for example, not being able to have a function instead of a method. also in C# most people leave off the this. when referring to instance properties, which seems extremely cursed to me but might be fine; I wouldn’t know
@ghostlyash how do you have an incredibly hot voice too?? 
I don’t know whose idea it was to decouple generating HTML/CSS with the rest of the backend code but that really seems like a bad idea to me because:
render() to render a Jinja template from inside of Python, my LSP is unable to verify that I’m giving it the data types that it expects, or even that I’ve typed the names of all of the variables correctlyrender() calls for my Jinja templates, to make sure I don’t give them the wrong kind of data by accidentrender() stubs to make sure that it matches, or my templates will fail silently (Jinja’s response to getting weird data or no data at all is to just try to punt, which is understandable in production but I would really like it to fail hard if I’m in debug mode)all of this could have been avoided if they’d just let me write the templates in Python as well
I feel like the phrase “don’t fetishize #trans bodies” is misleading to the point of being harmful, because it frames the problem as the attraction itself. like “you’re a sex pest if you find trans bodies attractive, or if you have a kink or a fetish for trans bodies”
I think that’s harmful for two reasons:
but “fetishizing” is not what this phrase is trying to express at all. it’s trying to say “don’t objectify trans people”
I feel like the word “objectify” has gotten pretty diluted but here I’m using it to mean “to treat someone as an object that dispenses sexual gratification, and not as a being that deserves respect”. it’s the mentality that a lot of “pick up artist” type people have, where it’s like they’re trying to find the secret password that can make {women/trans people/etc.} dispense free sex, as if we’re sex toys instead of people
so I think the phrase should be “don’t objectify trans people”. or ideally it should use a less diluted word than “objectify”, but I don’t really know of one right now