yep, definitely. i just thought "hey wouldn't it be funny if two dudes just ate some undefined substance because it's cheap" and, uhhh, yeah
i genuinely love it when people make their own meaning about shit i make sleep deprived out my mind because i thought of a funny word
[alt: Tumblr post from the purple geologist:
in my own experience with geology most precautions with smallest are to preserve the life and safety if the geologist, most of the rocks are fine
reply by laboradoresence:
i am continually reminded of one of my colleagues, who wanted to collect a sample of gypsum on a field excursion but was too lazy to take off his backpack and get his rock hammer. so he said "eh, it's soft enough" just fucking punched the rock until a piece fell off like it was fucking Minecraft]
[alt: inspirational quote from an air conditioner:
be the reason a building is cold inside]
(stolen from https://www.reddit.com/r/thomastheplankengine/comments/1evhufi/i_had_a_dream_that_this_was_an_inspirational/)
Simply by choosing a lesser used fedi software you're helping keep the fediverse from being dictated by a single software's whims. So that's a big plus there. Federation issues with kbin/mbin/azorius/other lesser used instance software will inevitably happen as people only test against the largest player in the field (in the ""threadiverse"" that's Lemmy, in the microblogging fedi that's Mastodon). So simply by not picking the largest you're, even if in a small way, helping not only mbin but all the lesser used fedi software as a whole.
Your own local communities being "dead" mainly boils down to communities themselves having a network effect around them where the largest one keeps growing larger as everyone focuses on it. And the largest communities are usually on lemmy.world (or occasionally other Lemmy instances). There isn't that much you can do there.
In my experience, it's always the smaller software that innovate. The same is true in the microblogging fedi (emoji reactions, quote posts, markdown, nomadic identity, reply permissions) just as it's true in the ""threadiverse"" (combining communities together, the ability to follow people, polls apparently (?)).
So really, don't worry about the size of your own instance's communities. As long as you trust your instance's staff to keep you safe there's no real reason not to get on a smaller instance, or on different software. Especially on here, where "discoverability" is not as much of an issue as it is in the microblogging fedi.
Am I understanding right that this has a low percentage chance of triggering on every tick
yes!
but will release a bunch of angry Enderman when it finally does?
no. you'll get teleported to where the enter pearl is and the potions will be shot towards you, killing you instantly.
[alt: reddit post titled "minecraft redstone machine idea to spice up your survival world"
the post contains the below image:
a diagram titled "heart attack simulator", where two sugar cane farms are connected to an and gate that activates when both farms update at the same time. the gate is connected to dispensers with 100 splash potions of harming, aimed towards an ender pearl statis chamber]
[alt text: dialog from YouTube Premium: "This could be your last video. Reactivate now to keep your life"]
[alt: safety warning thingy, big red header simply saying "dan"
on the left is an icon of a person, presumably dan, with a giant "no" in front of it.
on the right is text edited to say "do not connect no matter how much it asks"]
[alt: blatantly edited google results page, all the new text is in comic sans.
search for "soup definition" returning an ai result saying "you can write literally anything on here and people will eat it up and blame it on ai. look im not even using the right font its not like anyone cares"]
[alt: youtube thumbnail with the caption "this is the best keyboard according to ai"
all keys are either : or 3. the space bar is meow meow meow meow meow meow]
the difficult part isn't getting in the shower the difficult part is getting out
mnmmgrh worm worter
tallarico's really outdone himself this time
TLDR of linked gist: wayland is not X therefore it is bad. end of.
Wayland breaks Xclip: As you said it yourself, Xclip is an X11 application, so it doesn’t work on Wayland. Of course it wouldn’t work on Wayland. With Wayland, we’re trying to prevent what happened with Xorg from happening again, or am I wrong?
also, https://github.com/bugaevc/wl-clipboard. perhaps all OP (of gist) needs is a simple shim that can convert calls to xclip to wl-copy/paste? that doesn't seem too hard to make compared to keeping X.org alive I'd say (perhaps they should try making it if it's that much of a problem)
Wayland breaks screensavers: Yeah, that seems to be the case.
from the dev of xscreensaver at https://www.jwz.org/blog/2023/09/wayland-and-screen-savers/ :
[...] Adding screen savers to Wayland is not simply a matter of "port the XScreenSaver daemon", because under the Wayland model, screen blanking and locking should not be a third-party user-space app; much of the logic must be embedded into the display manager itself. This is a good thing! It is a better model than what we have under X11. [...]
[...] Under X11, you run XScreenSaver, which is a user-space program that tries really hard to keep the screen locked and never crash. It is very good at this, but that it needs to try so hard in the first place is a fundamental design flaw of X11. [...]
other people can comment on the parts they know about, these are two i know of off the top of my head
as far as i can tell this particular image is fake. and as far as i know pluton does not work like that.
Security? Probably. I wouldn't expect any measurable improvements to performance but the with compiler being able to do more checks it might enable some clever optimization trickery that would be harder to maintain in C.
Still, Rust on the kernel probably won't leave the realm of drivers any time soon, so it all depends on if you have the hardware that will use a driver written in Rust.
A popular misconception is that Firefox runs Gecko. And while that is kinda true, the real problem is much more interesting when you come down to the technical details.
Because it's the other way around. Firefox doesn't run Gecko, Gecko runs Firefox. Firefox is built in Gecko. In a similar vein, Thunderbird also runs inside Gecko. It's why they look so similar despite one being a browser and the other being an email client. Gecko is, in a way, a proto-Electron.
You cannot "rip off" Gecko from Firefox and embed it inside something like you can do with Blink/Chromium (unless you're on Android and use GeckoView), which means the only way to have a "Firefox based browser" is to fork the entirety of Firefox. There are forks like the TBB or Librewolf that do this, but the embeddability of Chromium makes it much easier for devs to make something that diverges from Chromium in major ways (stuff like Qutebrowser, for example)
i'm pretty excited for fedify since i'm unsure if there has been any other activitypub abstraction that feels as comprehensive as it seems right now (from a brief skim, anyway).
one thing i had in mind ever since i first skimmed the docs some time ago is this:
i would really recommend you to NOT tell people to use handles here. i assume this is just naming and the framework doesn't actually require a handle there, but documentation matters and if you follow on the footsteps of mastodon, pleroma, lemmy, and friends everyone who follows your docs will lose the ability to change usernames down the line without more pain than it's worth (and yes, there are software out there that allow it right now! please do not build fedi software assuming usernames are immutable jsut because mastodon doesn't let people do it)
just like how you wouldn't use a natural key in a database, you should tell people to use a surrogate key like an autoincrement id or a uuid on the actor IDs, as they're effectively permanent. while it may be probably fine for a quickstart thing like this to omit that, a lot of permanent codebases do start up by following these kinds of guides, and nudging people to do the correct thing when it's not that hard is always a good idea IMO