You wish it was like that in the medical industry, but it absolutely is not
You wish it was like that in the medical industry, but it absolutely is not
And the only thing even worse than SCRUM is literally every other option
No, that’s not how that works.
Users can generate their own keys, and you know it’s the same user as long as they have the same key, even if they’re on different servers.
No certificate authority is required for this kind of use case.
What this shows is how terrible raw JS is, when all of this crap is required to fix all of the edge cases and make things actually work the way it’s supposed to.
Using tools to break the encryption for backup purposes is legal in the US, but distributing tools to do so is not legal because the tools can be used for non-backup purposes.
I definitely remember hearing that term in the 90’s.
Your own rock, in this economy?
Lemmy has Hot, Active, and Top sort modes, all of which are different indicators of engagement.
Also, for whatever reason I actually do have ONE single post originating from kbin, from 3 months ago:
https://lemmy.megumin.org/post/128103
I’m guessing this is the first one I tried subscribing to… so for whatever reason I managed to receive that one post, but then no subsequent posts, comments, or votes.
All of my Lemmy subscriptions seem to be working fine.
Mine is definitely more than just “a bit” broken. I have 20+ communities subscribed for over 2 months and 0 posts. No issues with any Lemmy communities.
Way too long to actually be useful for converting anyone.
And one of those flaws is thinking that the world needs to be full of shitty people just so it’s not “boring”
Git was specifically CREATED to facilitate this exact mailing list workflow.
Considering that the vast majority of comments on every thread (including this thread) are from users on different instances than OP, I’m going to answer: “literally everyone on Lemmy, constantly, and on every post”.
It sounds like what you meant to ask was more about interoperability between different platforms, but keep in mind that even if other platforms didn’t exist, Lemmy would not be what it is without ActivityPub federation.
… exactly?
Someone pointed out an advantage of smaller instances and you were the one that said small instances have a problem (lack of communities), and I’m the one pointing out that your supposed problem does not, in fact, exist.
TL;DR small instance good
You can join any community on any instance from any other instance, as long as the admin hasn’t blocked it.
Local communities are totally irrelevant when deciding which instance should host your account.
If you have red hair, that might be the reason.
If you’re branching logic due to the existence or non-existence of a field rather than the value of a field (or treating undefined different from null), I’m going to say you’re the one doing something wrong, not the Java dev.
These two things SHOULD be treated the same by anybody in most cases, with the possible exception of rejecting the later due to schema mismatch (i.e. when a “name” field should never be defined, regardless of the value).