Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Web Origami, for making websites where you can understand how they’re made

weborigami.org

Post reply on HN
Print view View original

21–30 of 77 posts

Re: Web Origami, for making websites where you can understand how they’re made

#21

Post by tarxvf »

optymizer wrote: post #20
soco wrote: post #19

And still supporting HTTP. I don't know about this, anyone can suggest a reason to use HTTP nowadays?

* To serve content that can be accessed on networks using captive portals * To serve content on localhost while developing * To serve content on devices where setting up letsencrypt or other SSL is either too much of a hassle or not important * To stand up a quick HTTP server on hacked servers Maybe others can come up with more examples

To allow access by devices (embedded, vintage) where SSL cannot run.

Re: Web Origami, for making websites where you can understand how they’re made

#22

Post by em-bee »

robrtsql wrote: post #13
inanutshellus wrote: post #10

Earlier quoted context omitted.

From your description I expected a pile of legalese, but in reading it... I don't see "passive-aggressive" I see simple etiquette guidelines that shouldn't have to be said, but... clearly do. Often users screaming "I won't use [your project] if you don't fix [my whim]!"** actually does get some traction. So saying explicitly in the readme that that is rude and won't be allowed seems ... healthy. Notably, because it's…

It's totally reasonable, and is also the exact sort of guidelines I would want to establish if I were the maintainer of an open-source project. However, I think it's amusing that the website lists all of these cool reasons why someone should use Web Origami, and then the repo more-or-less says "here's all of these rules you should abide by if you want to even CONSIDER using this project". One page is meant to draw us…

i can only find two rules: treat the developer and his time with respect, and say hello before filing a bug[*]. the rest are statements to tell everyone what they can expect, nothing that they actively need to do.

[*] i disagree with "Bugs are a lousy way to say hello". though i think i know where the developer comes from, but if i am going to make a contribution, i'll just do that, and maybe start the contribution with a short introduction, but i am not going to say hello until i actually have something to contribute. i agree with everything else though, and expecially with all the things i should expect if i contribute something.

One page is meant to draw users in, the other to fend them off

i'd say it's meant to draw in friendly users and fend off the unfriendly ones. if you have participated in other projects you should understand why some developers feel that this is necessary.

Re: Web Origami, for making websites where you can understand how they’re made

#25

Post by quectophoton »

optymizer wrote: post #20
soco wrote: post #19

And still supporting HTTP. I don't know about this, anyone can suggest a reason to use HTTP nowadays?

* To serve content that can be accessed on networks using captive portals * To serve content on localhost while developing * To serve content on devices where setting up letsencrypt or other SSL is either too much of a hassle or not important * To stand up a quick HTTP server on hacked servers Maybe others can come up with more examples

> * To serve content on devices where setting up letsencrypt or other SSL is either too much of a hassle or not important

This is my use case, serving homeserver stuff from a ".internal" domain, only accessible through WireGuard. I ain't gonna mess with a custom CA just for this.

If one of my devices gets compromised enough to be able to sniff network packets that pass through the WireGuard interface, I have bigger problems to worry about.

Re: Web Origami, for making websites where you can understand how they’re made

#27

Post by hn_throwaway_99 »

soco wrote: post #19

And still supporting HTTP. I don't know about this, anyone can suggest a reason to use HTTP nowadays?

Why do you say "still supporting HTTP"? AFAICT this is just a site builder, but doesn't enforce how the site is deployed.

It includes "builtins" for accessing other resources (i.e., as a client) using HTTP, but I hope it should be obvious why that is a necessity.

Re: Web Origami, for making websites where you can understand how they’re made

#29

Post by gspencley »

soco wrote: post #19

And still supporting HTTP. I don't know about this, anyone can suggest a reason to use HTTP nowadays?

Others have offered good reasons but I'm going to offer another one, and I mean this seriously:

- Because I want to

Not everything is security sensitive. Some information is entirely public and has no need for encryption. While SSL is also provides protection against man in the middle attacks, which helps you to trust that the information you are reading has not been compromised and altered, this is also a security requirement that just doesn't exist in a lot of use cases.

So yeah, private internal networks where information security just isn't a requirement because the information is not at all sensitive and nothing bad will happen in a worst case scenario ... don't force things on people that don't require those things.

I can sort of understand the rationale for web browsers pushing encryption for public websites, with the amount of ecommerce that happens in current year. But if your use case doesn't fall into that bucket, and if you've done your own risk analysis and came to the conclusion that you don't need encryption for what you're doing because nothing bad can possibly happen then there's no need to jump through the hassle of setting up certificates.

Post reply on HN