I wonder why people toot if they don't want any reply.
Get yourself a website!
Set up a feed for your #propaganda!
But if you are in a public space and you speak to the public you are ASKING for objections!
I wonder why people toot if they don't want any reply.
Get yourself a website!
Set up a feed for your #propaganda!
But if you are in a public space and you speak to the public you are ASKING for objections!
Ehm... thanks! ?
Actually, one could say that I'm trying to turn the totality of the human population into a diverse and very anti-authoritarian group of people (the hackers).
Fortunately, nobody will notice my success until it's too late... ?
Let's people think I'm just a crazy guy! MUHAHAHAHA ! ! !
Not exactly the same, but it's true that we need to break turing completeness of CSS3 too.
But the attack surface is at least one order of magnitude smaller than HTML5+JS.
Still I agree, we'd need to dramatically polish the API surface...
I'm AMAZED by the deepness of #technical #conversations I can have over the #Fediverse.
It's addictive: join at your own risk!
But... really, great #hackers hang out here.
That's the goal of WebAssembly but I think it's a bad architectural mistake.
HTML + HTTP + TuringCompleteLanguage is not a properly designed distributed operating system.
I feel angry by just reading the title.
It's not just disingenuous.
They are lying to their users.
... a responsibility to be proud, without giving them too much power.
In the long term, if the license succeed in its goal, such asymmetry will become irrelevant: when EVERYBODY will be able to hack a software, there will be no way proprietary software could held an edge over free software.
So that responsibility will be less relevant and the power totally pointless.
I want to free people by turning them to hacker, subverting the mechanics that give corps an edge.
Do not aspire anymore... just #hack!
Don't let ESR like bullshit slow you down. #hackers don't need recognition: they simply don't care.
Hackers strive for knowledge.
We are lead by our #Curiosity.
Freedom, condivision, collaboration, intellectual honesty and irony are our tools to maximise our access to knowledge.
The more people learn fron us, the more they can teach us.
So... please #hack!
I love when people block me for something like this: https://web.archive.org/web/20181030215625/https://mastodon.xyz/@moggers87/100985275930288507
and later comment: "Should have seen that coming - a person was arguing with me trying to wheel the conversation around to some blog post they'd written. Just no."
?♂️
No, dude, I didn't.
But, actually I think I have a few good read that people spreading the #CoC worship should see.
Here for example, a great story to show how you do not need a #CodeOfConduct to ban someone you do not like: https://dev.to/shamar/i-have-been-banned-from-lobsters-ask-me-anything-5041
Here why a CoC does not protect users from #hypocrisy (nor by severe #security flaws): https://dev.to/shamar/the-meltdown-of-the-web-4p1m
CoC don't protect minorities, they exploit their naiveness to protect and empower community leaders. Live with it.
You can kill the person not the idea.
I have been #banned from #Lobsters, ask me anything at https://dev.to/shamar/i-have-been-banned-from-lobsters-ask-me-anything-5041
(or on the #Fediverse... :-D)
If it supports #JavaScript (or #WASM for what it count) and it honour standard HTTP headers, it is affected.
I can understand your arguments, but I cannot agree with you.
We face two issues here and the easier to fix and less dangerous is the technological one.
I do not want to live in a world where people wear parachutes because civil engineers don't care to fix a dangerous bridge that they built in the wrong way.
As long as #software engineering require marketing to get bugs like these fixed, we are all doomed.
I refuse to play this game. We need to fix the field more than JS.
@Ninjatrappeur @ekaitz_zarraga @sirikon
I didn't talk with uMatrix/NoScript devs because I think #privacy and #security should be the default working mode of the #Web.
You should opt-in #JavaScript, not opt-in into safety.
Also I think they would have a hard time at fixing some of the aspect of this issue (think about view-source, for example).
Finally the just protect #Chrome and #Firefox users.
I talked with #Mozilla because the write the #LivingStandards and they can fix them with FF.
@ekaitz_zarraga @sirikon @Wolf480pl
... but feel free to do something better.
However I think we should raise TWO bugs here.
The #JavaScript/#HTTP vulnerability that is a technical one and a deep #social vulnerability in the whole #IT sector.
I think we should try to raise awareness about both issues, using one to make the other evident.
It's not just #Mozilla or #Google: we should really not need #marketing to get vulnerabilities like these fixed.
And people #trust them.
They should not.
tiflolinux.org - GNU Social is a social network, courtesy of tiflolinux.org. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.
All tiflolinux.org - GNU Social content and data are available under the Creative Commons Attribution 3.0 license.