It might look like this, but thinking about it, I guess it's still useful in reducing unwanted interactions. People are lazy, and thus adding even a little friction can help a lot in preventing them from doing stalkering, spreading hate etc.
I.e. of course it's possible to login with another user, find the one who blocked you, make a screenshot or something and then quote it or perform any other interaction in your main account. But it's obviously not very easy.
So I'm sure it worked as a solution to reduce negative interactions on the platform. However, Musk doesn't want reducing these, his goal is spreading chaos and forcing his narratives, so the decision totally makes sense for him.
> his goal is spreading chaos and forcing his narratives
It may be as simple as revealing blocked content is a short path to increasing outrage and thus engagement. Like, I could see Facebook doing this on Threads.
I can never tell to what extent people believe things like this when they say them... Do they genuinely model people they dislike as wanting to maximize evil or are they simply trying to signal their dislike?
I am actually very sure that Elon is an extremely smart person. I can also see that he amplifies and posts disinformation posts that spread hateful narratives. That's why I make a conclusion that his intentions are reaching his goals in this, quite evil and harmful for the society way.
Even if I liked him, this still would had hold true.
It provides friction for further misbehaving. Imagine you blocked someone who has serious issues with people who #foobar. It's better for you if they can't easily find you and repost your content to their community who also hate #foobar. It's not perfect, but the friction helps prevent drive-by bad behaviour.
> repost your content to their community who also hate #foobar
This is valid. I don't think it rises to the level of preventing them from seeing my public content. But perhaps a brake on their ability to repost it would be courteous.
To be fair, you can barely view any post while unauthenticated these days. Sometimes I click on a link to a tweet on my work laptop (where I'm not authenticated) and I get immediately assaulted by several pop-ups and cookie bars and redirected to the landing page when try to dismiss them.
I thought so too, but also fun to see people posting they've been blocked by person they're debating... well arguing with, whether the blocked deserved it because they're being an ass, or whether the blocker was simply thin skinned. I think the latter, seeing people rage quit because they can't rationalize their position, is actually pretty useful signal.
But the point is you can’t see these posts from a particular account. It makes interaction between the two accounts a bit more difficult and so a bit less likely.
The blocked person can obviously create a new account and bypass that block to some degree, but as other have mentioned it will prevent them from reposting on their main account
Yes, the article says “engagements are still not allowed under blocks”. Then again, interaction in the general sense can still happen (you can always take a screenshot and post that).
the date tag on posts is not to indicate whether an article is deprecated vs current. presumably nearly every article posted is currently true (that's the "news" part). it's useful to hint whether it's interesting as a new thing, updated thing, or old but of current interest for some reason.
for the same reason that clickbait headlines draw you in, dates are good to wave you away.
Indeed. It looks to me like the export here is probably ThreeJS STLExporter? It is known for creating non-watertight models, unfortunately.
PrusaSlicer seems to do an adequate job tidying these up automatically.
I think it's not particularly uncommon for STLs exported from common CAD packagers to have some of these issues, though this is a lot.
Super-nice otherwise though -- a neat design. And in general I think client-side tools like this have a lot of potential. Three.js opens up potential for doing task-focussed things without using OpenSCAD on a server or a full emscripten build of OCC (like Cascade Studio does)
I only skimmed the article. But my stance is, anyone that ever used cherry-pick or reverted multiple commits is impacted by clean git history. Unclean git history could make a simple 2 minute cherry-pick or revert task to a 30 mins+ job.
Took me a bit to see what it was actually doing. In the doc folder it has some pictures. It appears to be sort of a linear actuator that pushes the spaghetti forward or backward, which makes/breaks the light path in the optical sensor on the other side.
I have one of those wireless magic mouse that takes 2x AA batteries.
The optical sensor started behaving in a weird way back in 2018 I think, so I stopped using it. I wouldn't mind risking breaking it by trying to fix the sensor (cleaning the lens from the inside is probably enough), adding a rechargeable battery (and whatever circuitry that entails) and maybe even enhancing the ergonomics if it still works after that.
Looks like it's only available to members with an account, but accounts can only be obtained via "contact us" (and probably a very expensive subscription).
I mostly agree with the points but I hard disagree with point number 3.
Clean code makes the project more easily maintainable. We generally try to keep a standard in code quality (and I would say 98% of the codebase we touch is well written). We also try to schedule refactoring rounds (but that doesn't always happen because of time constraints).
That isn't true either though. Sure, they don't care about it as a first order thing, but they care about development not slowly grinding to a halt over time. And writing well structured code is one of the things the software side of the house does in order to do a better job delivering on that desire from the business. If nobody on the technical side has the credibility or trust to make that case, then that's a problem.
>Sure, they don't care about it as a first order thing, but they care about development not slowly grinding to a halt over time.
Most only care when it affects them or sales, not when devs are asking to allot time to clean up code or pushing off a release to fix wonky stuff. In my mind that's not caring.
That's like people care that they can't walk up stairs without huffing and puffing, but not enough to actually diet and exercise. That's not actually caring, that's really regret.
I'm fortunate though, my company gives a lot of credence to dev.
That situation sounds to me like the problem of the development org not being trusted by the company's leadership when they say "this will slow down short-term initiatives but speed up long-term ones".
Yes, it's pretty common in my experience. Of course executive bonuses are granted based on short-term initiatives more so than long-term ones. When they finally reap what the sow, just blame dev. You don't get to be an executive without knowing how to politic.
> Don't get me wrong, people will expect you to write good and clean code.
I can agree with this. Clean code is not "celebrated" because it is expected as normal. You won't get a raise for it. You could get problems for not writing clean. But when the business gets into a tight spot, they will accept shitty code that fulfills their desired goal over a nice clean and elegant solution delivered few days later. In this case, the shitty code could get you a raise.
reply