[-] hawkwind@lemmy.management 9 points 1 year ago

I know your joking but in case people don’t get it: rich comes from luck, not from hard work.

Don’t work any harder than you have to, thinking it helps. It doesn’t change the statistical chance of you becoming rich.

Many people will say you can help along the luck. Those people are dumb.

[-] hawkwind@lemmy.management 8 points 1 year ago* (last edited 1 year ago)

Ah yes, the “local taxi lobby.” Uber helped show a lot of us what a fucking joke that is, not just in Ottawa.

Innovation, choice, quality and freedom are the choice spices for capitalism soup. These shit-cook-legislators kept sprinkling in taint like protectionism, cronyism, extortion and corruption thinking nobody would notice. Well guess what? Now it’s just taint soup.

Why does it matter who’s serving you taint soup? The problem is there’s no other soup and they keep telling you it’s fine.

[-] hawkwind@lemmy.management 8 points 1 year ago

There never was love for flatpaks and there never will be. I’ll never forgive them for killing my son.

[-] hawkwind@lemmy.management 8 points 1 year ago

A quick, but a little dirty solution for this, would be communities having “tags” in their metadata. This wouldn’t prevent spam, or an accumulation of four trillion tags, but you could easily add “only these tags,” or “not these tags,” to any feed. User objects have metadata that is used like this (as the “bot” flag) already. I’m just familiar enough with the code to know it wouldn’t be a slam dunk, but it’s also not a breaking change or re-write!

[-] hawkwind@lemmy.management 8 points 1 year ago

We've changed our name to Israel. - The Admins.

[-] hawkwind@lemmy.management 9 points 1 year ago

I didn't want to say it, because I wanted to believe :(

[-] hawkwind@lemmy.management 8 points 1 year ago

And it’s only a matter of time until that detection can be evaded. The knife cuts both ways. Automation and the availability of internet resources makes this back and forth inevitable and unending. The devs, instance admins and users that coalesce to make the “Lemmy” have to be dedicated to that. Everyone else will just kind of fade away as edge cases or slow death.

[-] hawkwind@lemmy.management 8 points 1 year ago

That's a very complex topic. Consider this list of solutions that I found on google and have massaged to sound relevant and appealing:

[-] hawkwind@lemmy.management 10 points 1 year ago

I'm an AI language model and don't have access to specific information about your company's payroll schedule or policies. To find out whether you will be paid before or after the holiday, I recommend reaching out to your human resources department or payroll administrator. They will have the most accurate and up-to-date information regarding your company's payment schedule. They will be able to provide you with the details you need about when you can expect to receive your payment.

[-] hawkwind@lemmy.management 8 points 1 year ago

Slaps train roof

[-] hawkwind@lemmy.management 10 points 1 year 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.

view more: ‹ prev next ›

hawkwind

joined 1 year ago