Well hot damn. It worked!

Thanks.

Now I'm off to follow the rest of the steps. Wish me luck.

The unexciting part is that the obvious best strategy would be to ignore the regular part of quidditch and just focus entirely on helping their seeker get the snitch and shutting down the opposing seeker.

Happy to share my notes.

Holding off for a bit though. The changes I made seemed to move me forward but I'd like to confirm that my changes at least work for me before I start recommending them to anyone else :)

That's exactly what I'm looking for!

I'm gonna go test out Boost. Do you happen to know what API endpoint it hits?

update: It looks like Boost is only available on Android and I don't have one.

He was clearly chosen for the votes he's likely to bring in. That's smart strategy on Harris' part.
As near as I can tell "the media" spent a few days wildly guessing about who her VP pick would be and many of them where white males. There are many articles that predicted that she would pick a white male but I couldn't find any that argued that it should be a consideration.

I don't know. The 6 finalists that we know about were all white males but we can only speculate who she interviewed to get down to those 6 finalists.

While it's always a reasonable guess that a white male's identity played a role in their hiring process, we don't seem to have any evidence to support it.

Calling someone a "DEI hire" doesn't just mean that they're a different race than other people in an organization. It's used to imply that the person is otherwise unqualified for the job and was specifically hired to fill a diversity requirement.

I don't think that's an accurate description of Walz and I'd do some pretty serious eye rolling if MAGA starts trying to portray him as such.

Thank you. I tried that and got:

curl: (7) Failed to connect to localhost port 80 after 0 ms: Couldn't connect to server

When I put the port number back in:

curl -I http://localhost:8536/api/v3/site

I get the same 404 errors, with different time stamps.

journalctl -u lemmy

shows the same thing. Entries like:

Sep 27 20:26:04 ip-172-31-44-10 lemmy_server[12299]: 2023-09-27T20:26:04.726387Z INFO actix_web::middleware::logger: 127.0.0.1 'HEAD /api/v3/site HTTP/1.1' 404 0 '-' 'curl/7.88.1' 0.000054

I assume that /ap/v3/site is dynamically generated and there isn't a location I can look at in the file system to make sure that everything is correct there, right?
The instructions have you create /usr/bin/lemmy, /etc/lemmy/lemmy.hjson (outside of stuff you download to the user directory) so I don't think there is.

Thanks. Those look like they're likes per post or comment rather than per user but it's pretty close to what I'm looking for. I'm gonna test that out when I get back from my conference!

Can you elaborate on that? I'm not at all familiar with nginx configuration.

That was merged into lemmy-ansible on June 22. The instructions say to run:

curl https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/templates/nginx.conf --output /etc/nginx/sites-enabled/lemmy.conf
# put your actual domain instead of example.com
sed -i -e 's/{{domain}}/example.com/g' /etc/nginx/sites-enabled/lemmy.conf
sed -i -e 's/{{lemmy_port}}/8536/g' /etc/nginx/sites-enabled/lemmy.conf
sed -i -e 's/{{lemmy_ui_port}}/1234/g' /etc/nginx/sites-enabled/lemmy.conf
nginx -s reload

Do you mean that I need to also do something like:

curl https://raw.githubusercontent.com/LemmyNet/lemmy-ansible/main/templates/nginx_internal.conf
--output /etc/nginx/sites-enabled/lemmy_internal.conf