Yes because again it’s the mismatched ram sizes and the different clock speeds. IMHO the clock speed issue is way more likely to throw things off than the different stick sizes, although neither are ideal.
Reddit refuge
Yes because again it’s the mismatched ram sizes and the different clock speeds. IMHO the clock speed issue is way more likely to throw things off than the different stick sizes, although neither are ideal.
*Matrix
“Personware” sounds like Elon’s brain implant plan
Don’t buy any of those toilet tank tablets. They often will corrode and wear down the tank valve over time, and your toilet will start to run on its own (or could even break).
White vinegar is good on any wood or porous surface because it’s small enough to get inside and kill the biological things (black mold, etc) while bleach just tends to just clean the surface and evaporate quickly.
And yet you’re still here
The thunk and all the silverware and glasses rattling lol
This take is riddled with naivety.
Not only will Meta read, train AI on, aggregate and datamine, and correlate this data with your real identity, but when Meta announces that “the easiest way to be on the fediverse is to just use Threads” then all the people who avoided Mastodon because it was “too complicated” to sign up, all the people who are basically already signed up because they scroll Insta all day, will go with Threads instead of spreading the load out.
As smaller instances start to drop off under the load, under the lack of interest as threads grows and they shrink, merely mirroring the traffic of a centralized corporate entity, users start to flock to threads for its reliability and speed.
Then Meta pulls the plug, since “no one really used this ActivityPub thing anyway, it was too technical”.
Threads isn’t about beating “X” (lol X is in a death spiral, it’s only a matter of time), it’s about ensuring the Fediverse never rises up.
See what happened with Google Talk and XMPP.
Processes that run on the same system can run as different users (including kernel) which is used for privilege separation. This can still allow a program in userland to peer into otherwise restricted system processes or the kernel. Every system is a “multi-user” system, even if there is only a single human user.
Front-loaders usually restrict you from opening the door before they’re drained, or else some idiot would flood their apartment.
No, the second one says “Sept. 8th 2023” and that last panel is obviously British (you can tell by the teeth) /s
EDIT: Kinda fixed? Is Lemmy stripping special characters? Is it my app client (Memmy)?
It’s worded confusingly. Let me see if I’m correct here:
If people prevent something being used by tons of other people for no good reason
This is not in reference to the lemmy.world users being prevented from using the instance, but instead is about the possible motivation of said attack
then this would be a very good one to “hold a grudge” against them for.
Continuing on to say that you could understand how a person could hold a grudge over a perceived slight
The way you worded it make it sound like you mean lemmy.world users should hold a grudge against the attackers for preventing them from using lemmy.world, which is why people are confused. It might have been better to say like “The attackers are probably retaliating for being banned or something”
Probably important to also include that personal property is not private property. Private property would be means of production such as farms or factories - they are owned by the workers collectively. You still can have a house, a bed, a refrigerator, a TV, etc.
You wouldn’t be able to lift the door without the spring acting as a counterweight. It’s usually a big roller just above the doorway on the inside (right near where the track curves in) with cables that run down to the bottom door panel.
So yeah, huge spring under constant tension.
Lemmy is AGPL v3.0. From what I understand, that means anyone running Lemmy (or a fork of Lemmy) needs to make their source code public, even if their code changes are strictly to support their own network infrastructure.
it really doesn’t matter though, as a corporation only needs to implement an interface to Lemmy via ActivityPub protocols; in other words it they could write a completely closed-source backend to use for profit and as long as it can poop out the correct data structures over ActivityPub to allow Lemmy instances to understand it, it will work.
This already happens as we can see and subscribe to kbin magazines, and Mastodon users can be @'d and IIRC can reply to comments via Hoot (or whatever they call it). Kinda wild, but it also leaves the door open to literally whoever.
I think the real interesting question is will a large corporate player be able to maintain a captive userbase? None of the doomsday scenarios play out in their favor unless they can capture users and communities - because then the usefulness of the whole thing rides on their server being available. At that point it’s reddit with more steps - they can do what they want.
It’s easy for really old posts to get necro’d in Active sort. Not necessarily a bad thing, but if you use the “feed” to keep up with the latest then it’ll cloud your listings a bit. A lot of people don’t look at the post date right away (especially those of us from alien site since we’re still operating on old habits).
Hot also had a bug that pushed old posts up, IIRC? Maybe i’m thinking of Active; I can’t remember off the top of my head as I type this. Anyway I think Active is based on recent comment activity and Hot is based on recent voting activity. Nothing wrong with either, but I am honestly appreciating the “Top X hours” methods to keep up with recent news and events and to keep things fresh.
We’re still in the “oh shit activity has increased by a factor of a thousand, we need to make the database not crash” phase of development of Lemmy (and kbin) so I’d expect that eventually the feed sorts will be looked at and tweaked. Just needs a bit of attention to get what you are looking for at the moment.
Passkeys rely on you holding a private key. The initial design was that a device (like a browser or computer/phone) stored the private key in a TPM-protected manner, but you can also store it in a password manager.
This is more secure than a password because of the way private/public key encryption works. Your device receives a challenge encrypted with the public key, decrypts with the private key and then responds. The private key is never revealed, so if attackers get the public key they can’t do shit with it.
Just be sure that your private key is safe (use a strong master password for your PM vault) and your passkey can’t be stolen by hacking of a website.