hawkwind

joined 2 years ago
[–] hawkwind@lemmy.management 22 points 2 years ago* (last edited 2 years ago) (7 children)

Shocking research by Statistics Canada uncovers surprising economics discovery: people with lots of money lend it to people with less for more than it's worth: rich people get richer, and poor people get poorer!

"We were so focused on how fast people got sucked dry, we never stopped to realize why," said Mike Hunt, an assistant-upper-middle-deputy-manager at Statistics Canada.

Mike goes on to say: "We've been struggling to classify "monetary gains," for the lower class. We decided that getting two-for-one coupons, or winning a toonie from a scratcher counts. That way we can say for sure everyone is gaining!"

[–] hawkwind@lemmy.management 1 points 2 years ago

kbin posts DO show up in the details table. you would need to know the ip they are coming from. they don't include their instance host name in the header, which is why it's not in the table and instance is null for some IPs. also I don't scrape and subscribe kbin magazines like i do for lemmy ATM, so the traffic will be low. probably just a few from kbin.social.

[–] hawkwind@lemmy.management 2 points 2 years ago

Should already be able to:

https://redash.io/help/user-guide/integrations-and-api/api

For example: https://aftershock.lemmy.management/api/queries/4/results

The API key for public users is the same as the dashboard slug: oT7pdcoeHWccpvZCNmTpJKoGZND8ZdRO3wDWpMug

[–] hawkwind@lemmy.management 2 points 2 years ago

aaaaaand we’re done.

[–] hawkwind@lemmy.management 15 points 2 years ago

a revolution starts with a single bean

[–] hawkwind@lemmy.management 1 points 2 years ago

Commendable that you want to help, but the software needs to handle dead installations as there is no possible way to enforce people to decommission. :) Might be worth dropping just to help the use case of how this gets handled. I feel like you did everything you could.

[–] hawkwind@lemmy.management 7 points 2 years ago

Keep in mind this is a one hour snapshot. I am working on a historical rating as well to give a better indication of overall long term stability.

[–] hawkwind@lemmy.management 7 points 2 years ago* (last edited 2 years ago) (1 children)

Fixed! The regex was not getting content from < 0.18.0 instances. Thanks!

EDIT: I am wrong, it was something else in feddit.de's messages I THOUGHT was a version thing, but must be a localization thing. A string in the JSON was breaking some regex. Regardless.. fixed.

[–] hawkwind@lemmy.management 7 points 2 years ago (2 children)

I am actually working on that! Stay tuned. Like days though, don't get too excited. :)

[–] hawkwind@lemmy.management 11 points 2 years ago (1 children)

No beans for beehaw.org :(

[–] hawkwind@lemmy.management 10 points 2 years ago

What instance is used as a reference for the delay? One you self-host (lemmy.management)?

Yes. lemmy.management. It is purposefully updating subscribed communities to as many as possible (via automation.) This doesn't correct for network lag, but the idea was to capture the "federation" lag. There's no code I'm aware of that allows admins to prioritize outbound federation traffic. I could be wrong though.

Sooo … what’s the deal with lemmy.ml … that seems to have gone beyond lag and is basically falling over … seems like the devs have neglected their own instance’s health?

I just collect the data.

What’s that Redash? Is it a plotly thing or some other product that just uses their graphing library? How have you found it?

https://redash.io I don't remember how I found it. Probably an "awesome" list on github.

[–] hawkwind@lemmy.management 5 points 2 years ago (1 children)

I didn't even load it on mobile. I will check it out tonight and maybe just create a separate "mobile friendly" dashboard.

view more: ‹ prev next ›