Sheriff: Block JavaScript and Cookies per Domain, in Safari
Sheriff blocks externally-loaded JavaScript, not embedded JavaScript.
Doesn't block embedded JavaScript.
Multiple attempts have failed with clear negative feedback. Continuing down this path would likely waste your time and resources when better opportunities exist elsewhere.
Don't build it.
Your idea for a browser extension to find and delete cookies falls into a crowded space. We found 10 similar products, indicating high competition. Considering the number of similar products, it's going to be tough to stand out. The average comment count on these similar products is 15, suggesting high engagement, but the lack of positive signals for use or purchase means there's no clear user demand. Given the existing solutions and the absence of expressed need, this venture could be challenging and might not be the best use of your time and resources. I know this might sting, but I'd rather be honest with you so you can focus on better ideas.
Your idea for a browser extension to find and delete cookies falls into a crowded space. We found 10 similar products, indicating high competition. Considering the number of similar products, it's going to be tough to stand out. The average comment count on these similar products is 15, suggesting high engagement, but the lack of positive signals for use or purchase means there's no clear user demand. Given the existing solutions and the absence of expressed need, this venture could be challenging and might not be the best use of your time and resources. I know this might sting, but I'd rather be honest with you so you can focus on better ideas.
Sheriff blocks externally-loaded JavaScript, not embedded JavaScript.
Doesn't block embedded JavaScript.
AI-driven cookie management for your site. Auto-scan, categorise, fill missing info, and generate dynamic policies. Streamline user consent effortlessly. šŖ āØ
CookieChimp is praised for simplifying cookie compliance with its automatic categorization and gap-filling features. The launch received positive feedback and congratulations. There is interest in the platform's automation of website aspects, with a question raised about potential legal issues. An offer was made to list the app in AI directories to increase its visibility.
Users expressed concerns about the learning curve associated with integrating CookieChimp. A significant worry also revolved around potential legal issues and lawsuits that might arise from using the platform.
This FireFox / Chrome extension blocks cookies pop-ups and banners on websites.
Users discussed various methods and tools for web scraping and browser automation, with a focus on handling JavaScript content. Selenium was frequently mentioned, alongside alternatives like Puppeteer and Playwright, which some users preferred. The use of Chrome DevTools for inspecting dynamic content and accessing cookies was highlighted. There were debates about the definition of 'works' for websites without JavaScript and the security of storing cookies. Some users shared specific tools and libraries, while others sought advice on technical issues like shebang usage and capturing full raw HTTP requests. Apologies were made for an untested pull request, and there was a mention of a Chrome extension for cookie tracking.
Users criticized the product for reliance on Selenium, suggesting alternatives like Puppeteer or Playwright, and noted the lack of maintenance for Pyppeteer. Concerns were raised about security, particularly with the 'peanut' key and the handling of cookies. The product's inability to work without JavaScript on most websites and to capture full raw POST requests was also highlighted. Users pointed out issues with debugging, the shebang format, and the submission of untested code. Some comments were neutral or misinterpretations.
Get a free cookie audit of your website instantly and determine your siteās compliance with GDPR cookie laws. The audit checks if you have stored cookies on the site, have 3rd party domains on the site and whether you have a cookie banner implemented.
Users are very positive about the Cookie Checker launch on Product Hunt, praising its ease of use, clean layout, and the free cookie audit tool. The dog logo is also a hit, with multiple users finding it cute and endearing. Several comments highlight the app's usefulness for cookie compliance. Some users inquire about specific functionalities like localStorage/sessionStorage usage, private cookie detection, and recognition of CookieConsent v3.
The Product Hunt launch received criticism for not recognizing CookieConsent v3. A user also suggested a feature addition focused on specific compliance improvements to enhance the product's functionality and adherence to regulations.
Automatically capture browser cookies and synchronize them for external crawler sessions to maintain connections.
Creator of Moodistory asks for feedback.
Hi! Author of this proposal here.Iām loving all the feedback and wanted to address some things:* Yes, nonce tracking is expensive. HTTP request signatures could be used instead of noncesātheyāre just not fully fleshed out yet, from what I can tell. And a lot of other crypto systems we rely on in Web traffic today also assume proper nonce tracking. Fortunately you only need to track distinct nonces per established session, so you could wait to allocate storage for them until the client actually tries to set up a WebSession, and use a Bloom filter to save on storage at the risk of some false positives for nonce reuse (could be risky if youāre relying on that as tamper evidence, but you could tune your filters accordingly).* The stuff about the ergonomics of cookies and banners and auto-log-out as they currently are is mostly incidental. Iām just trying to paint a picture of how tighter integration of the notion of a āsessionā into the browser itself could improve the UX we currently have today.* Many people have pointed out that this is not stateless. Indeed! This is supposed to be a more secure way of establishing a stateful connection over a stateless protocol, for which there is already a demand which weāre meeting with the least secure possible method (bearer tokens sent in plaintext over the channel). Issues with scalability need to be addressed on the implementation side, but I believe the protocol is still sound and not inherently unscalable (no more than TLS in its current form).I am going to look for opportunities to fold these points into the document itself, and maybe rearrange some of it so that these points get covered earlier and more clearly.
The Show HN submission has received criticisms regarding lack of features for session management and security, such as no enforcement of cookie clearing on device lock, no session invalidation, and issues with nonce tracking. Users find the documentation unclear and the implementation complex, potentially leading to security vulnerabilities. There are also concerns about GDPR compliance, with criticisms of non-compliant cookie banners, legal misunderstandings, and ineffective enforcement. The product is seen as promoting conformity over innovation, with a lack of novel tracking methods. Additionally, there are usability issues, such as the lack of backward compatibility and the potential for DDoS risks.