This. It almost only applies to desk jobs. Production workers can’t just work a day less and keep the same output, and if they can’t do it, people like me who are responsible for keeping the production running as part of their job(electrician in my case) also can’t work a day less.
If companies wanted to do this, they’d have to hire more workers to give everyone a 4 day week. But all this would do is create more costs for the company
Most probably not broken at all.
I.hate.password.
l.hate.password.
The first is a capital i, the second is a lower case L.
Voyager is all you’ll ever need^^
That’s technically true and also the reason why a 60FPS locked game can indeed look smoother on a 120Hz display compared to 60Hz. Because 60FPS don’t always hold a steady 16.67ms between each frame so it could happen that on a 60Hz display you’ll see a frame twice and skip another one instead.
Nowadays you ideally have a monitor which supports variable refresh rate so this becomes a non issue because every single frame now gets his own refresh.
There were 360 possible directions he could run and he chose the wrong one
Has she tried turning it on the other side yet?
But it does.
Example: You’re on lemmy.world. Let’s say lemmy.world defederates lemmy.ml today.
Now you won’t be able to see any new posts made by users of lemmy.ml, be it on lemmy.ml itself or on any other instance. You will still see everything that was posted up until the defederation though because defederation just means that your instance won’t request new copies of the content of lemmy.ml .
And they also can’t post stuff on comunities of lemmy.world(I believe they technically could do that, just that nobody could see it, but it may be that by now it’s entirely blocked to even make a post there).
Now as long as lemmy.ml doesn’t defederate lemmy.world too, their users will still be able to see your comments and may also reply to your comments on other instances, but you won’t see that.
So defederation mainly serves two purposes for the users of the instance that defederates another instance:
Everything you post in a beehaw community won’t be seen by anyone else. Everything you post in a community of any other instance will be seen by everyone who isn’t on an instance that defederated yours
Just look at the sidebar:
Donations
If you would like to make a donation to support the cost of running this platform, please do so at the mastodon. world donation URLs:
https://opencollective.com/mastodonworld
https://patreon.com/mastodonworld
Not what I said, but okay…
So you think that being a nazi automatically means that every view you have on anything is bad by default or that you are not able to participate in any normal conversations that don’t touch that topic, like technology or gaming, without writing racist stuff?
Because that would be the only reason defederation would be justified in my eyes.
In any other case, just don’t visit their home instance.
If a bunch of nazis want to run a server and post racist shit all day we can’t stop them. But we can (and should) defederate from them. They can have their own private island.
And what if they post racist shit all day on their own instance but also post normal and helpful stuff on communities of other instances?
Just don’t visit their communities, that’s it. No need to block potentially helpful posts of members of that instance everywhere.
The same thing when there’s a NSFW and your own instance doesn’t want to see NSFW stuff. That’s fine but it’s not like the users of that NSFW instance are running around posting porn on every other community.
If some of them do, block the users. But there’s no reason defederating the whole instance because those users can and do also participate just fine in other topics that have nothing to do with NSFW or nazi stuff.
For example why should a programmer that has a nazi instance as his home not be allowed to post memes in a community about programming humour from a regular instance, when he doesn’t post anything there that is in any way related to him being a nazi?
we’ve been blocked by precisely one actual instance - the predominantly German-speaking feddit.de
Which also was my first home instance until I noticed that a comment chain I accidentaly started using another lemmy instance was not visible when looking at the thread though feddit. Not even my own comments made with an instance that wasn’t blocked. Turns out the user I answered to start that chain was a member of your instance and thus the comment and everything following it was not visible for feddit users.
Which is why I’m a full time lemm.ee user for now bc at the time it had 0 blocked instances and was blocked by 0 too^^
and most importantly, the admins here have explicitly stated that the policy is to avoid defederation at all possible avenues.
That’s the policy of lemm.ee too. It has 34 blocked instances right now but those are all suspicious ones that formed and got >30K users within a couple hours and no activity at all.
But ultimately, new users shouldn’t have to worry about such things, which is why I can’t see Lemmy growing as a whole with the tools available now.
Everywhere it says it’s not relevant where you sign up because you can see all the stuff from other instances anyway, but that’s simply not true, it DOES matter where you sign up and even after that you could be forced to change your instance when the defederation roulette starts spinning again.
and most importantly, the admins here have explicitly stated that the policy is to avoid defederation at all possible avenues.
It just looks like an actual app and not like a tab in your browser(no adress bar for example), plus you can access it quickly that way without having to navigate your browser tabs
The way I always viewed those up- and downvotes was as a quicker way of commenting with “I like/agree with this” or “I don’t like/agree with this” and that would be there for everyone to see too, so why shouldn’t that be true for upvotes?
Though it’s bad design that you can’t see this info on lemmy but you can see the info about lemmy users on kbin. Either have lemmy show that info too or limit the info on kbin to up/downvotes from kbin users only.
It seems that Kbin is also the better entry point for most former reddit users because even if it has different instances too, it’s not that spread out like Lemmy is so new users have less to worry about and can discover the Fediverse more as they go
Return to it and have my knowledge of all the positive and negative aspects erased would be something I’d consider. But having used all the technology for so long, I couldn’t imagine just don’t having it anymore tomorrow
It is, only that on reddit you had the possibility of one r/video and one r/videos but here you have the possibility of 20+ different c/video and 20+ different c/videos so it’ll take much longer to form a main community and then you have the chance of an instance suddenly disappearing for whatever reason and then the whole process starts again.
I had a Sony Xperia Z3 which had its charging port and sim tray covered by small pieces attached to the case that had rubber on them so you could open it and use the port and then seal it again. It also had a magnetic charging port that didn’t need water protection.
But iirc, it was said that the waterproof rating was only true as long as you didn’t use these pieces^^
And had you been on an instance that was defederated you’d have to create another account to acces their community, just like a separate forum, which I exaplained in the other post would be the better choice.
Because it doesn’t make sense to have that kind of manual approval registration system aimed to only have specific users in the community that share their values, so they clearly want to crontrol who can and cannot post there… and then being on a plattform where users can just join another instance or even create an instance for their own and then post what they want on beehaw and the only way to prevent this would be proactively blocking all other instances and working with a whitelist instead.
tbf many of those releases only contain 1 or 2 small things, many other devs would wait to include them in one big release instead of releasing 5 small ones