Buy a keyboard and monitor
Buy a keyboard and monitor
NGL, this looks kinda terrible
Parts of “Rift of the Necrodancer”
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.
“Discord said users will be able to turn off the ads in their settings.”
Remote Desktop
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.
Your own rock, in this economy?
If you’re using assembly, then you’ve already given up on the easy ways.
The only engine with even worse licensing than Unity
It’s federated, so the local user count is completely irrelevant.
Especially when OP even specifically said that you would see the SAME content, just with different sorting.
As terrible as Unity’s API design is, Unreal’s API design is 10x worse and still feels stuck in the 90’s.
And as soon as they have any competitors we might consider it
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.
Semantic versioning. Moving from v2.3 to v2.4 shouldn’t require major changes, but moving to v3.0 can.
Way too long to actually be useful for converting anyone.
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).