Shamar

@dpwiz

#SMTP for example.
#ICMP is another.
Even #FTP still rocks (in private networks or over a VPN).

#HTTP 1.0 was pretty good to distribute #HyperTexts. Turned to shit as #WHATWG decided to transform the Web into a distributed (and highly insecure) operating system.

@Wolf480pl@niu.moe @technomancy

→ @Shamar@framapiaf.org

@hansbauer @grainloom @mmu_man

@alcinnz is hacking #Memex in this space: a #browser that doesn't need #JavaScript to distribute #HyperTexts, but use a more powerful markup language and more powerful style sheets.

For #Jehanne I'm hacking a file protocol, #FP (I don't have much fantasy 🤣 ) that is simpler but more powerful and expressive than #9P2000 (and probably broken... but you know, you can't learn anything if you are afraid to fail) and will replace #NFS, #SMB and #HTTP.

→ @Shamar@framapiaf.org

@z428 @eloquence @bjoern
I'm afraid you didn't understand the problem.

The #Web is broken at the architectural level.

The problem is not #JavaScript but people blidly executing programs that can be customized for them with perfect deniability.
This class of attacks is wide and totally undetectable under normal conditions (and even if detected, they cannot be proved in court).

We need to separate
A) access to contents (aka #HyperTexts)
B) software execution

#Memex serves A
#Jehanne serves B

→ @Shamar@framapiaf.org

@bugaevc

It's funny how I totally agree with your first toot and DISAGREE with many of the others.

#HTTP is designed to transfer #hypertexts (which include imgs, pdfs...): those you describe (RPC...) are crappy abuses.

I mostly agree about #HTML (which is a #hypertext markup language, Troff is not, try to put music in it) and #CSS.

I STRONGLY disagree on #JavaScript. The whole idea to fool people to blidnly execute custom programs written in a shitty language is broken and we should fix it.