One example is FreePBX, which supposedly supports automated SSL renewal via LetsEncrypt, but constantly overwrites the config, thus breaking the “auto.” So I have to manually renew the cert, or I have to upgrade (ie rebuild the whole system from scratch, including installing the OS) to the next major version of FreePBX and hope they fixed the issue.
So I’m really not excited about the time limit dropping from 90 days to 47 days.
This (same link I believe, not just same story) was on the front page a couple of days ago and quickly flagged dead. I’m surprised to see it again so quickly. I would have thought a flagged link wouldn’t be possible to submit again and get to the front page.
Not remotely the same thing. HN's ads are text-only job postings for companies in YC's portfolio. "Online ads" on the other hand are an unregulated wasteland of scams, dropship brands, misinformation, titillation, and culture war ragebait.
True, but how many sites allow users to down-vote or flag the advertisements? A lot of the blatant ad posts wind up flag-killed and only people who have "show dead" enabled ever see them.
You're self aware enough to realize that there's "some undercurrent stuff", but not self aware enough to pick any other username than F0UKYOU-HN, which just maybe might prejudice users and moderators against you. It's like wandering into a bank with a hoodie, face mask, and a gun, and wondering why security is all up in your grill about a "mysterious" something. You're being profiled at the very start by something you set for yourself. If someone comes into your house and the first thing out of their mouth is "f0uk you!", would you really be inclined to sit down and listen to them and have a thoughtful conversation, or are you going to kick them out at the first sign of trouble? At the very least, you're going to keep a close eye on them, yeah?
In meat space, you can do things to change your appearance somewhat, but people gonna people and they're gonna judge you, some times fairly; sometimes not. Online, the only thing people have to go off here is your words, and choosing F0UKYOU-HN belies a certain amount of aggression that is naturally going to start people off on the wrong foot. How do you want people to see you? You could have chosen anything, maybe something bland or generic, like mikelovesbikes32, but in choosing what you chose, you wanted to make a statement, and with your statement, you're "baffled" by why the human being on the other side of the screen might take offense?
>I post a few comments here and there and the site tells me I am commenting too often.
A moderator probably took one look at your username and comment history, decided you were a troll and rate limited your account. You need to learn how to play the game better.
But the "you're posting too fast" filter is applied by the mods. I know because I've had one for a while. The expectation is that you either apologize for your behavior and have it removed or get frustrated and quietly leave. But like many of HN's operant conditioning features it doesn't really work as intended.
And the aggressive and demeaning tone of a lot of your comments seems intended to invite downvotes. Are you surprised that when you call people simps and angry and selfish that you get downvotes?
The validity of your comments matter far less than your tone and demeanor around here. I don't know if this is your first account here but if it isn't you should know this place is aggressively and mercilessly tone policed.
edit: also editing your comments like that is just lame. For someone who constantly calls other people butthurt you really do seem to be the most butthurt and triggered person here. Sorry I tried to engage with you like a person. Bye.
I'm not understanding the difference between Main Editor and Live Preview on the demo page. They look identical to me. And both seem to have a live preview, as far as I can tell.
This is so weird that a random website on a random server (having SSL doesn’t change that in the slightest) is considered less of a risk than a file I have on my own computer.
The random website cannot access arbitrary files on your computer's file system and send it somewhere else. An html file with javascript running locally, if trusted, on a typical personal computer could do that.
There should be some way to mark files as accessible, for example, place them into a folder with a specific name (like "html-accessible-files") on the same level as HTML file.
Internet Explorer in an ancient age used to have .HTA ("HTML Application") files for a double-click a self-contained HTML file that can act as a small local application. It did a lot of what PWAs are still trying to do, somewhat more effectively and simpler. (.HTA was mostly just a ZIP file! Simple to build.) It also had a lot of security holes that gave it a terrible reputation and a lot of reasons it got killed. (It was very early days for "AJAX" and modern browser security tools like CORS and whatnot, after all.)
Such things seem to be cycles.
Today a lot of browsers support .MHT which is a similar format, but also worse in many other ways. (The M stands for MIME and wrapping a website like an email seems somehow sillier and weirder to me than wrapping it in a ZIP file, though I get that MIME wrappers are ancient internet tech with an ancient track record.)
Then we see all the millions of apps in PWAs and Electron downloads.
At some point it feels like we should have better solutions and cut some of the gordian knot cycling between "local apps are too much of a security risk" and "local apps should be complicated collections of Service Workers to get offline support" and "local apps should just embed a full browser and all its security implications/risks rather than allowing browsers to directly open local apps" and back and forth. .HTA and .MHT both showcase possible directions back to "simpler" than PWAs/Electron, they just have such fascinating and weird histories.
The rule was probably intended to block public non-SSL pages, so your clipboard data doesn't ever get sent over the wire unencrypted.
Why does it block local pages? Well what benefit of is to Apple or Google if it were easier to make good localhost webapps?
Try deleting Safari site data(indexed DB etc) for your localhost site. You won't be able to. Hell, even deleting data for a specific public site is hilariously painful. Try adding a certificate authority to your iPhone. Try playing locally cached audio blobs via web APIs on an iPhone. There's probably 1000 more.
Last time I used Gemini CLI it still couldn’t consistently edit a file. That was just a few weeks ago. In fact, it would go into a loop attempting the same edit, burning through many thousands of tokens and calls in the process, re-reading the file, attempting the same edit, rinse, repeat until I stopped it.
It's not perfect - you often have to remind it not to write imperative style code and to lean on Elixir conventions like "with" statements, function head matching, not reassigning vars, etc.
So I’m really not excited about the time limit dropping from 90 days to 47 days.
reply