This is default featured slide 1 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 2 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 3 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 4 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

This is default featured slide 5 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.

Wednesday, September 6, 2023

New best story on Hacker News: Show HN: Puck – Open-source visual editor for React

Show HN: Puck – Open-source visual editor for React
397 by chrisvxd | 88 comments on Hacker News.
Hey hackers, OP here! I've been dipping in and out of this problem space for the last few years with many of my clients. Puck sits somewhere between an old-school WYSIWYG-powered CMS and headless one, allowing content teams to author content using real React components. Traditional CMS solutions were flexible but often resulted in page that completely broke the brand guidelines. Headless CMS solutions are a fantastic way of controlling brand by restricting UI changes to developers, but makes layout changes restrictive and slow as developers often need to get involved. Puck provides a visual editor for React that can sit on top of your existing headless CMS (or act as standalone). We've been dog-fooding it on a few pages at https://measured.co and on https://wellpaid.io . So far, so good The API is built for React, which allows FE devs to quickly integrate their existing component and add some form fields for author input, or connect it to a headless CMS of choice. It's open-source under MIT, and pairs nicely with Next.js (check out the demo application). Next in the pipeline: support for multi-column layouts, richer demos, new plugins. Looking forward to hearing your comments!

Tuesday, September 5, 2023

New best story on Hacker News: ZFS for Dummies

ZFS for Dummies
394 by giis | 150 comments on Hacker News.


New best story on Hacker News: Rockstar is selling cracked game copies on Steam

New best story on Hacker News: OpenTF repository is now public

OpenTF repository is now public
426 by cube2222 | 145 comments on Hacker News.


New best story on Hacker News: Ask HN: I’m an FCC Commissioner proposing regulation of IoT security updates

Ask HN: I’m an FCC Commissioner proposing regulation of IoT security updates
543 by SimingtonFCC | 173 comments on Hacker News.
Hi everyone, I’m FCC Commissioner Nathan Simington, and I’m here to discuss security updates for IoT devices and how you can make a difference by filing comments with the FCC. As you know, serious vulnerabilities are common in IoT, and it often takes too long for these to be patched on end-user devices—if the manufacturer even bothers to release an update, and if the device was even designed to receive them. Companies may cease supporting a device well before consumers have stopped using it. The support period is often not communicated at the time of sale. And sometimes the end of support is not even announced, leaving even informed users unsure whether their devices are still safe. I’ve advocated for the FCC to require device manufacturers to support their devices with security updates for a reasonable amount of time [1]. I can't bring such a proposal to a vote since I’m not the chairman of the agency. But I was able to convince my colleagues to tentatively support something a little more moderate addressing this problem. The FCC recently issued a Notice of Proposed Rulemaking [2] for a cybersecurity labeling program for connected devices. If they meet certain criteria for the security of their product, manufacturers can put an FCC cybersecurity label on it. I fought hard for one of these criteria to be the disclosure of how long the product will receive security updates. I hope that, besides arming consumers with better information, the commitments on this label (including the support period) will be legally enforceable in contract and tort lawsuits and under other laws. You can see my full statement here [3]. But it’s too early to declare victory. Many manufacturers oppose making any commitments about security updates, even voluntary ones. These manufacturers are heavily engaged at the FCC and represented by sophisticated regulatory lawyers. The FCC and White House are not likely to take a strong stand if they only hear the device manufacturer's side of the story. In short, they need to hear from you. You have experienced insecure protocols, exposed private keys, and other atrocious security. You have seen these problems persist despite ample warning. People ask, ‘why aren’t there rules about these things?’ This is your chance to get on the record and tell us what you think the rules should be. If infosec doesn’t make this an issue, the general public will continue falsely assuming that everything is fine. But if you get on the record and the government fails to act, the evidence of this failure will be all over the Internet forever. If you want to influence the process, you have until September 25th, 2023 (midnight ET) to file comments in the rulemaking proceeding.[4] Filing is easy: go to https://ift.tt/XscLi5Q and click to file either an ‘express’ comment (type into a textbox) or a ‘standard’ comment (upload a PDF). Either way, the FCC is required to consider your arguments. All options are on the table, so don’t hold back, but do make your arguments as clear as possible, so even lawyers can understand them. I’m here to listen and learn. AMA. Feel free to ask any questions about this or related issues, and I’ll answer as many as I can. I just ask that we try to stay on the topic of security. My legal advisor, Marco Peraza, a security-focused software engineer turned cybersecurity lawyer, will be answering questions too. I’m open to incorporating your ideas (and even being convinced I’m wrong), and I hope that my colleagues at the FCC are as well. Thank you! [1] https://ift.tt/dH5tWBF... [2] https://ift.tt/4m9D3tQ... [3] https://ift.tt/4m9D3tQ... [4] If your comments are purely in response to arguments made in other comments, you have an extra 15 days, until October 10, 2023.

New best story on Hacker News: Get a cable modem, go to jail (1999)

Get a cable modem, go to jail (1999)
420 by resolutebat | 324 comments on Hacker News.


New best story on Hacker News: Writing a C compiler in 500 lines of Python

Monday, September 4, 2023

New best story on Hacker News: VSCodium – Open-source binaries of VSCode

VSCodium – Open-source binaries of VSCode
397 by Brajeshwar | 197 comments on Hacker News.


New best story on Hacker News: Ask HN: Who is hiring? (September 2023)

Ask HN: Who is hiring? (September 2023)
375 by whoishiring | 362 comments on Hacker News.
Please state the location and include REMOTE, INTERNS and/or VISA when that sort of candidate is welcome. When remote work is not an option, include ONSITE. Please only post if you personally are part of the hiring company—no recruiting firms or job boards. One post per company. If it isn't a household name, explain what your company does. Commenters: please don't reply to job posts to complain about something. It's off topic here. Readers: please only email if you are personally interested in the job. Searchers: try https://ift.tt/r09YKiN , https://ift.tt/hs4Tmbq , https://hnhired.fly.dev , https://ift.tt/3LarH6s , https://ift.tt/lutgYnT . Don't miss these other fine threads: Who wants to be hired? https://ift.tt/rJj1VIB Freelancer? Seeking freelancer? https://ift.tt/sO82P1p

Sunday, September 3, 2023

Saturday, September 2, 2023

New best story on Hacker News: The Mystery of the Bloomfield Bridge

The Mystery of the Bloomfield Bridge
544 by graypegg | 144 comments on Hacker News.


New best story on Hacker News: The worst programmer I know

The worst programmer I know
545 by zdw | 274 comments on Hacker News.


Friday, September 1, 2023

New best story on Hacker News: Wavacity – a FOSS port of Audacity to the web

New best story on Hacker News: Doug Lenat has died

Doug Lenat has died
442 by snewman | 123 comments on Hacker News.


New best story on Hacker News: RFC 3339 vs. ISO 8601

RFC 3339 vs. ISO 8601
431 by iamwil | 252 comments on Hacker News.


New best story on Hacker News: Organic Maps

Organic Maps
437 by LeoPanthera | 215 comments on Hacker News.


New best story on Hacker News: Animated Knots

Animated Knots
430 by zingerlio | 61 comments on Hacker News.