lemmy.world admins made a bot that used MBFC and many considered it a bad move. I'm sure there are others but here is a thread on the topic. https://lemmy.world/post/18073070
I feel inclined to point out that even in the context of Christian myth, God said he would destroy the world again with fire after "Noah's reboot" (actually God's reboot, he just spared Noah), he just said he wouldn't use water next time. This isn't really a shower thought so much as it is a fact of Christian myth. God said he'd return and destroy the world multiple times.
Instead of "with an algorithm" say "with a recommendation algorithm". Algorithm is a very generic term that can mean anything.
Re 1: It's just a meme, you don't look at comedians and accuse them of lying. Also, it says "what can happen", not that it did.
It's not like I notice it more when I have a frame rate counter turned on, I'm just not questioning how bad or how often the drops are when I have it enabled.
Around maybe 40 or so I start to notice it. 50 and higher I'm content. My monitor only supports 60 Hz. Around 20 or less I'm annoyed. It's tolerable for turn based games though. Not enjoyable, just tolerable.
If they want me to watch they need to add power ups. At least a banana peel would be nice.
It's not that it's "too hard", it's that even a tiny set back for something that someone is already hesitant to do can be enough to make them not do it. It's just easier to call that "hard" or "confusing" than say "even a tiny set back for something that someone is already hesitant to do can be enough to make them not do it."
You have links to posts, but not the community. I know it sounds like I'm just being overly pedantic, but with the way federation works you can't know where a community is without the instance. You only ever call it ITAP, not [email protected].
You have to think of it from a micro blogging perspective. Imagine I have a ton of followers and have created a culture of them attacking anyone I attack. It makes more sense how it is bullying in that context.
Edit: Also, to be clear, I'm not arguing against this feature, just explaining how it can be used for bullying.
I don't want users adding their own editorial takes.
Two different webs very close together. I like to imagine they'd chat about their days of they could!
For the unaware, there is a thing people do at Dragon Con (and possibly other conventions) called Swag and Seek where people make trinkets and leave them around the convention for people to take. This is probably the coolest one I found this year.
3
Make IntelliJ IDEA warn for potential NullPointerExceptions during unboxing without assuming everything is @Nullable?
(stackoverflow.com)
Link to a (frustratingly) deleted question on Stack Overflow. Text and image copied below incase you don't have the ability to see it. (Not sure why the image shows multiple times.)
Is there any way to more granularly control IntelliJ IDEA's inspections' "Nullability and data flow problems" option "Treat non-annotated members and parameters as @Nullable"? Preferably for unboxing specifically?
I am aware I can use a variety of @Nullable annotations in a variety of places in the code to make the warnings appear. That's not always an option as the place the boxed primitives are coming from may be other libraries you don't have control over. (Imagine if the Holder record below was from a different project.) I included other examples below to illustrate my point.
public class Sample {
private final Boolean value;
public Sample(Boolean value) {
this.value = value;
}
private boolean isValue() {
return value; // I would like a warning here
}
private static Boolean boxedTrue() {
return true;
}
private static boolean unboxedTrue() {
return boxedTrue(); // No warning here, but that's understandable since never null
}
private static Boolean boxedNull() {
return null;
}
private static boolean unboxedNull() {
return boxedNull(); // Only warning in the file (by default)
// "Unboxing of 'boxedNull()' may produce 'NullPointerException'
}
public record Holder(Boolean value) {}
public boolean openHolder(Holder holder) {
return holder.value(); // I would like a warning here
}
}
When "Treat non-annotated members and parameters as @Nullable" is enabled, the following gives warnings. While that makes sense given the name of the option, there is code like this literally everywhere. It adds hundreds of warnings to my project. I'm trying to find more granular choices.
public static ZonedDateTime timeStuff(LocalDateTime localDateTime, ZoneId zoneId) {
return localDateTime.atZone(zoneId); // I do not want warnings for this
}
I see that the Java Class Library has JetBrains annotations despite not actually being annotated. Is there perhaps some way to add these automatically to libraries if there is no better way to control the inspection?
The bot used the same site for its ratings, so yes.