reference to ableism
@inkblitz I suspect that the difference would be mainly because fedi is full of folks who have been unhelpfully told "just fix your brain" for many years when what they really needed was disability accommodations. So I would expect recommendations to lean more towards "accept that things don't work optimally sometimes, and find ways to live your life under those constraints anyway".
@pho4cexa There are a few that are supported by sigrok, if you want to do analysis with something other than the device itself or the crappy vendor apps: https://sigrok.org/wiki/Category:Energy_meter (I have some of the RDTech units and documented the protocol there but it seems more have been added since)
wordpress, wp engine
The most darkly ironic thing about the whole WP Engine situation is that I never liked WP Engine very much, due to their intensely capitalist way of doing business, and they've long been on my mental list of "this looks like a FOSS profiteer that doesn't sufficiently contribute back".
And now, if anything, Mullenweg's bullshit has only increased my sympathy for WP Engine. They are still a capitalist enterprise, of course, but *so is Automattic*, and I'm no longer sure that the lack of contribution was actually caused by WP Engine's choices, as opposed to Mullenweg just getting in their way of doing so.
re: serious answer
@0x57e11a Yeah, I'm out of suggestions here unfortunately 😔 Pretty much every time I try to work with impl return types I have different but similar issues
@ben It never ceases to amaze me how Discord seems to manage to have all of Matrix's weird-ass federation bugs without actually being federated
Yikes! Other authors, be very careful and make sure you, or your agent, keeps an eye on contracts! Because mine is more experienced, he spotted the below right away, but keep an eye out for the below.
1. Do not give publishers permission to train their AI on your work, even internally. WTF? A publisher tried to sneak this in!
2. Despite what publishers tell you, demand your audiobook should be done by humans and your cover should be done by humans. Publishers love AI despite what they tell you!
3. Do not let publishers dictate giving you a lower advance *because* you don't have a platform. This is bullshit, especially since they have all the PR connections.
4. Do not let them say anything about how many hours you should spend promoting your book. Make this low as possible or even eliminate it altogether. They have all the PR connections. You don't. Make it their fault you don't make back their advance, not you, because they can decline to publish you in the future and you won't have numbers to prove they failed in PR.
5. Don't let publishers tell you virtual book tours don't generate returns on investment and isn't worth having their publicist do. No, fuck that shit! Because my agent is experienced, he said fuck that straight away! If you want your releases to be virtual, say so!
And finally,
6. Do not let them give you a low advance. A lower advance says they don't have to invest in you as much to get back that investment. They should do the bulk of the publishing work, not you, so always ask for higher advances, always! Even if you don't think you'll make back that advance. Go higher. This will force them to do something about their investment in you!
re: serious answer
@0x57e11a (Also you could probably force it into the correct shape by providing some sort of explicit type declaration for `clos` but that's... not great, and I'm not sure what declaration that would be exactly)
re: serious answer
@0x57e11a So my best guess as to what's going on there (although I'm not a Rust expert by any stretch of the imagination) is that the closure can be interpreted/typed in multiple ways, and in the first case, it gets a type hint from the specified return signature so it knows the type to interpret it as, but in the second case it doesn't have that information (as I don't think the type hint propagates backwards through `clos`?) and so it guesses the wrong type.
That doesn't really explain the error message, which I think is just wrong/vague and probably should be filed as a bug (error clarity bug at least). Maybe you can get more insight into what it expects by looking at the supposed type that the language server thinks `clos` has, and see how it differs from the return value signature?
serious answer
@0x57e11a Without seeing the code, I would guess that it means there are some ways in which it can be called that the implementation does not support (at least according to its signature)? In other words, the coverage of possible call signatures is not complete
This is a graph from a Dutch news article about changes in revenue (blue) and sales volume (red) in the Dutch retail industry. Above 0 means it went up, below 0 means it went down, compared to the previous year. The massive dip in volume are the years in which there were COVID measures.
But I want to draw your attention to the "revenue" line. Notice how it doesn't meaningfully dip compared to previous years, and revenues continued to climb, *even though* the sales volume decreased?
Next time someone tells you that ever-increasing consumerism is necessary to keep the economy running, remember this graph.
(The CBS, which is the data source for this graph, is the Dutch governmental statistics agency.)
The lamp has been reinstalled with 100% less ballistic events than its preceding uninstallation
a surprising number of instances dont have rules against ai. it really surprises me. please dont allow the proliferation of anti-artist, anti-labor ideologies.
ableism
It is absurd to expect any one person to have expert or even basic knowledge about every possible topic, in societies as complex and multi-faceted as ours, and it's just as absurd to expect people to have that knowledge in whatever topic happens to be *your* specialty.
In other words: complaining about how "everyone should know the basics of X" or "people are too dumb to understand X" is being an asshole and gatekeeping at best, and most likely you're also being ableist. Cut it out. I don't care what the subject is.
Like, work on making things more accessible and approachable instead?
A lot is going on today: A few colleagues are sawing a yew trunk into boards, while other millers are planing some wood for a customer. I started cleaning and setting saws, as we do not have that many sharp saws left.
We set the saws before sharpening them.
We usually do not sharpen saws when there are visitors in the mill, because the sharpening machine makes a lot of noise.
Als een staatssecretaris opstapt vanwege racisme, dan zeg je niet: ‘Oh we gaan haar missen en kunnen jullie de rechtsstaatverklaring nog een keer ondertekenen?’ Dan eis je dat degenen die zich racistisch hebben geuit uit het kabinet worden gezet. (Jesse Klaver).
#racisme #wegmetschoof
Technical debt collector and general hype-hater. Early 30s, non-binary, ND, poly, relationship anarchist, generally queer.
- No alt text (request) = no boost.
- Boosts OK for all boostable posts.
- DMs are open.
- Flirting welcome, but be explicit if you want something out of it!
- The devil doesn't need an advocate; no combative arguing in my mentions.
Sometimes horny on main (behind CW), very much into kink (bondage, freeuse, CNC, and other stuff), and believe it or not, very much a submissive bottom :p
My spoons are limited, so I may not always have the energy to respond to messages.
Strong views about abolishing oppression, hierarchy, agency, and self-governance - but I also trust people by default and give them room to grow, unless they give me reason not to. That all also applies to technology and how it's built.