For a user to correctly answer a permissions dialog, they need to learn programming and read all the source code of the application. To say nothing of the negative effects of permission dialog fatigue.
In practice, no-one who answers a web permissions dialog truly knows if they have made the correct answer.
Asking the user a question they realistically can't answer correctly is not a solution. It's giving up on the problem.
You'd be better off believing neither, but taking the participants' stories as what they believe happened.
Then drawing your own conclusions.
(Sorry, not picking on you in particular; I'm just quite annoyed to see this thread treating the incident as a spam problem to be solved technically. There were also people who really did not like Wil Wheaton, and then suddenly found him in their online home.)
Sure, and these are good points, but they solve a problem far less interesting than the real problem.
Of the (let's guess) 60 people telling Wil to go do one, up to about half[1] might be the shitposting crew taking advantage to troll a not well-liked celebrity, but the rest were people and their friends who were genuinely incensed at his appearance in their graph.
For the latter, you might argue they should block him, but if he's on the same instance then effectively he's come in and sat down in their home. If he's on a remote instance, then there still exists the desire for retributive justice for past wrongs (yes, including perceived).
In this specific case, there was no-one (except the moderator!) sticking up for Wil. The groups that dislike him are small, but genuinely plural. (e.g. 4chan doesn't like him, a number of trans* artists don't like him, some Star Trek geeks...)
Given that he came to the fediverse to escape harassment and trolling on _mainstream_ platforms, I don't think there is a great solution.
So here's two options, instead:
One: Don't join the platform as "Wil Wheaton". If you want to join a community as another face in the crowd, then use an internet handle. Then you can interact as equals.
Pseudonymity is one of the great gifts of the internet.
If you come as a celebrity to link your blog posts and try and talk to fans, then I don't think the fediverse makes any sense. It's too small and people are territorial of the instances they adopt.
Secondly - a more social solution - find some way to calm the people involved. This may involve temporarily suspending instance links, or saying that (as moderator) you need time to discuss this and are working towards an acceptable solution, etc. Don't know what you do next.
Finally - and the point of my rant: Dismiss those you don't understand / greatly simplify social problems at your peril. (Sure is great reading a bunch of trans artists arguing in earnest turned into "abusers" - nice!)
As humans, we make great changes and build general solutions based on one-off undesirable acts, and if you don't even make an effort to completely understand the problem then you WILL build the wrong solution.
[1] Possibly more than 50%? There were people involved who kept saying they had just joined Mastodon and didn't know how to use it, which is weird.
How do you implement co-operative multitasking in WebAssembly?
Do you have to analyze the source program & know where every possible call to a yield is, and store all resulting suffixes of a function as new functions?
I managed to log in, but the system is pretty barebones.
Trying to change or apply for a new banking product just takes you to a help page saying the ability to do this is 'Coming soon'. (Some other features are scheduled to be available by the 'End of April', for comparison.)
Also, in the 'pending transactions' popdown, e.g. £38.60 is displayed as '38.6'...
They're planning both. Reference counting/bump pointer allocation in-frame for temp stuff & no GC & manual memory management for the upcoming high-performance restricted C# subset data-oriented jobs code, and for full-fat real C# code they're slowly working to clean up their (C++ coded) runtime so that a non-conservative garbage collector can work.
Re. Boehm, that was the garbage collector Mono shipped until they wrote SGen some years back.
I'm quite excited by the work they're doing on performance. It looks great.
There should be a link on the page. I started binding it to C# over Christmas out of frustration of one not existing, and someone else quickly picked it up and made a cleaner binding that I recommend more. Google NuklearDotNet for the latter.
That would be a bit inaccurate though - the core library doesn't have a backend. The example you found e.g. implements an OpenGL backend.
It doesn't reference any external libraries (maybe C runtime). IIRC it does not assume you have a malloc() function by default; you provide one or use a #define before include to tell the header it can rely on standard malloc.
The point of single-file header libraries is that generally they are relatively small, and do not rely on linking with other libraries (outside the C runtime).
I guess you could have just read a lot of books. I don't know if libraries are being closed down in the US, but that's happening a lot now in the UK for cost saving reasons/due to lack of demand.
With a computer & internet access, it's easier to stay isolated. Though I guess TV and radio, even newspapers and writing for pen pals also provides the same substitute sort of-interaction without actually having to interact.
For all the negatives (assuming we say 'all these people should just go out and socialize' - unfairly), I think online communities make a huge difference to those who are physically disabled, need to stay home to care for someone all the time, or are stuck in the arse end of nowhere.
There's still a certain sense of egalitarianism in internet forums. One commenter's opinion is (by default) worth the same as another's.
That said, in most open comment sections in modern times the actual 'community' part is underdeveloped. Everyone is so loud, there's always someone positively thrilled to play devil's advocate with maximal cynicism, always someone there to interpret a comment unfairly, precious little sympathy for the views of others.
I think the expectation the Go lot have been working towards is the expectation that individual pauses are very short. Contrast to a Java server GC, aiming towards overall efficiency. (Tell me if I'm wrong, I'm no expert.)
Interesting! IMO it showed that garbage collection isn't some silver bullet (of course), but that with a kick to a quite coarse control it's possible to achieve very good performance indeed.
I am surprised that the difference is so great - and that the GC seems to think it's a good idea to keep collecting 4 MB of data at a time - but I guess the Go team have been tuning heavily for interactive performance i.e. small pauses.
I guess in a situation like this you'd prefer something more like 'server' GC - maybe wait until you've allocated 1 GB then run through and collect everything you can.
In games, I wonder if you'd like to turn the GC off during frame rendering then collect while presenting the frame/waiting for VSync.
For soft real-time audio - synthesizing a few samples at a time - what would you do? OpenAL wants you to queue up thousands or tens of thousands of samples, but that sucks if you need to react very quickly.
If anyone has any ideas, please say. I'd love to do soft real-time audio in a thread even in e.g. C#. (Edit: Maybe JIT some code that doesn't allocate? Or even have a separate interpreter written in C that has a constant-ish upper performance bound & no malloc.)
It sucks that it's gone - it took me months to retrain my muscle memory to stop using backspace - but I've definitely accidentally navigated back from a form before.
I've adjusted. It's a hard decision but imo the right one. Future generations shouldn't have to deal with this.
To anyone reading who needs a keyboard-based substitute: Alt+Left Arrow.
Wow! I honestly thought they were references to the Church of SubGenius and Discordianism respectively. Odd how the names still make sense when viewed with the hacker sense of humour as if they were references...
In practice, no-one who answers a web permissions dialog truly knows if they have made the correct answer.
Asking the user a question they realistically can't answer correctly is not a solution. It's giving up on the problem.