Notices by Amber (puppygirlhornypost2@transfem.social)

you know what fuck you

@julia@eepy.moe what about constexpr

@julia@eepy.moe I said constexpr, completely different from const.

@julia@eepy.moe @lizzy@social.vlhl.dev become a c++ developer it’s fun here

@lizzy@social.vlhl.dev @julia@eepy.moe I mean languages are fun. Rust is a tool and so is C++, I find it interesting rust’s macros in comparison to C++‘s template metaprogramming

@lizzy@social.vlhl.dev @julia@eepy.moe Primarily though constexpr is something that’s hyped up (I don’t really use it though). Sorry for the "use c++" thing that was not meant to be a childish thing. There are a lot of reasons to stay clear of C++ (I have pain with buildsystems)

@lizzy@social.vlhl.dev @julia@eepy.moe cargo interests me somewhat but the lack of binary builds is a turn off. I also don’t really think that matters in the grand scheme (having a system like cargo vs not… cmake, meson, autotools etc are all um their own can of worms). At least rust actually has a community where people can improve the language (the committee is notoriously bad yea for C++)

linux users when i tell them to sudo apt-get bitches

things that sound like they'll break a fedi instance but don't:
nuking redis

things that sound like they shouldn't break a fedi instance but do:
pruning remote media cache

I give up finding that post. Anyway, I think https://asml.cyber.harvard.edu/fediverseobservatory/ is a cool idea. I sent them an email actually

also the only reason I'm not freaking out about their poor choice of wording "anonymizing your data" is because what they really mean is just stripping it completely. If you'll look at the provided examples (scroll, because they're not just a couple lines) what it does is replace the actual value corresponding to a given key with the expected type.

see:
"replies": { "id": "<uri>", "type": "Collection", "first": { "type": "CollectionPage", "next": "<uri>", "partOf": "<uri>", "items": [ "<undefined>" ] } }

also the poor harvard researcher who is now going to have correspondence with someone named "puppygirlhornypost" providing actual feedback to their project :woozycat:

This is more just "mapping" out how AP objects are represented between each instance rather than gathering the actual object itself. Which is why I suggested that they provide a way for us to feed them information they can't get from a relay like forwarded reports.

@HauntedOwlbear@eldritch.cafe it kind of weirds me out how people have petnames for politicians

for real

#shitpost

also yes I’m using my battery bank in bed when there’s an outlet right there lol

Does anyone have a working NGINX configuration for mastodon (or its flavors glitch-soc/chuckya)? I have a testing environment that's being very annoying with "secure mode" enabled

cc: @ShadowJonathan@tech.lgbt @4censord@unfug.social

@puniko@mk.absturztau.be @igwigg@mk.igwigg.space i post at work too

do i do the thing

for context, here is "the thing".

In programming, there are a lot of things that I consider repetitive/tedious. One of these things includes making unit tests, I find it to be exhausting. Another one of these things is commenting my code. Not just // or my long form comments but XML-doc comments like so:
/// <summary> /// Sends a post request given an endpoint, a body, and optional headers /// </summary> /// <param name="endpoint">A string containing the api endpoint to invoke this request on</param> /// <param name="body">The request body</param> /// <param name="headers">An optional List of KeyValuePairs</param> /// <returns>an instance of RestResponse containing the result of the POST request</returns> internal async Task<RestResponse> WrappedRequestAsync(string endpoint, string body = "{}", List<KeyValuePair<string, string>>? headers = null)
"The thing" refers to the fact that in particular, cardboard.NET's MisskeyRestApiClient class (which basically encapsulates a RestSharp client instance and has all of the functions actually sending requests to the misskey RESTful API) is being refactored. I have replaced some of the underlying functions that the rest of the functions rely on (namely, renamed SendWrappedRequestAsync to WrappedRequestAsync and introduced WrappedRequestAuthAsync along with the nonwrapped variants). I have >60 errors because all of these functions are calling functions that do not exist.

What I have been doing to fix this is taking the time to write out the XML-doc comments describing what the function does, and adding remarks for the required scope just on the off chance we ever get an endpoint to see the current scopes of the token. Why is this important? Because it would save me a lot of time later, I won't have to look up the api doc to see the required scope. I'm doing more work now so I have less work later. Problem is I am bored out of my fucking mind doing this repetitive task. Do I do the thing and just skip over all the xml-doc to work on things I actually care about or do I continue to build my discipline and do things that need to be done but aren't fun