今日已更新 245 条资讯 | 累计 26657 条内容
关于我们

标签:#dev

找到 3173 篇相关文章

AI 资讯

I made a public comment section for every canonical URL with Chrome Extension

So for about 10 years I've been wanting this every time I'm on a scam website or news article that has no comment section or locked reddit thread. I've seen a couple similar attempts, but most of them focus on personal notes or having drawing features and things I'm not really interested in. This is just about letting users, customers and the general public communicate about URLs and sub-urls the websites themselves don't provide or won't provide the public the ability to comment on. In the extension you can see how many comments are on a URL and your notifications if anyone replied to you. There are some rules like everyone is only allowed one top level comment to reduce spam or potential bots. You can replay as many times as you want. You can also edit your top level comment, which will show last when it was edited. Here is the main list of reasons I created it: Warn people on scam websites when they go there they can just read the comments Comment on locked social media posts, x profiles, youtube videos, reddit threads etc.. Comment on news articles that have no comment section Comment on top of social media that would otherwise require an invasive account to comment. Almost all social media also has a url these days. This also works with any string so technically you can comment on anything including, addresses, businesses, cities. If you paste in a URL it will normalize it so you won't accidentally create a duplicate forum. On the PublicNotes.xyz homepage you can just create a forum based on anything. Feedback and bug notes welcome. Website: https://publicnotes.xyz Chrome extension: https://chromewebstore.google.com/detail/public-notes/keaopkaplnpjhccneageakejbbbeoncp?pli=1 submitted by /u/PandorasBucket [link] [留言]

2026-05-30 原文 →
开发者

Collection of free online tools for web developers

I've been working on a side project called WEBDEVPACK - a collection of free web-based tools for developers, designers, and generally anyone working online. The idea is simple: lightweight tools that help us solve everyday problems. Check it out at webdevpack.com submitted by /u/ivopetkov [link] [留言]

2026-05-30 原文 →
AI 资讯

Built a personal web search engine with automatic indexing of visited websites, result previews & optional semantic search

I'm working on a self-hosted search service called Hister with the goal to reduce dependence on online search engines. Hister is a full text indexer for websites and local files which automatically saves all the visited pages rendered by your browser. It provides a flexible web (and terminal) search interface & query language to explore saved content with ease or quickly fall back to traditional search engines. I've been using it for a few months and as my local index is growing I can avoid opening google/duckduckgo/kagi - and even websites listed in results - more and more frequently. The initial reception is overwhelmingly positive with already more than 30 contributors and hundreds of contributions - perhaps you can find it useful as well. (Or at least have some constructive criticism =]) The code is AGPLv3 licensed, available at https://github.com/asciimoo/hister , read-only demo: https://demo.hister.org/ , website: https://hister.org/ submitted by /u/asciimoo [link] [留言]

2026-05-30 原文 →
AI 资讯

Built a privacy-friendly forum platform for niche communities

Hello! I am Axel and I’ve been building Kanto, a small forum platform for niche communities. The main idea is that communities can allow normal posting or optional anonymous posting which is fully secure and private, while still requiring accounts behind the scenes. Users can create communities, start threads, reply, and browse communities around specific interests! :) I’m trying to keep it simple and privacy-friendly: no ads, no selling user data, and a cleaner experience than huge social platforms, not like the big american social media companies that sell your data. https://kanto.forum submitted by /u/axeeeeeel- [link] [留言]

2026-05-30 原文 →
产品设计

[Showoff Saturday] I built a free 360° atlas of Tasmania by myself

https://preview.redd.it/rbt6z0s1k84h1.jpg?width=1200&format=pjpg&auto=webp&s=87b4980b47fb45994978a1a719b5fbf3180c0860 – 6+ years of shooting, stitching, retouching, design and coding – Built solo. 0 funding, 0 sponsors, 0 ads. – Free for everyone – 80 places online 170 HD 360° panoramas (still only around 30% of what I've shot so far) – Map mode for browsing places across Tasmania, immersive journeys for larger full-screen 360° tours https://tas360.au submitted by /u/vla_dis [link] [留言]

2026-05-30 原文 →
AI 资讯

[Showoff Saturday] RigRAG - easy way to instantly add memory capabilities to your AI Agents

TL;DR : Built a RAG pipeline, allows you to upload docs and connect via API/MCP to service. need feedback if you find it useful or confusing: https://rig-rag.vercel.app I got into the whole AI, embeddings, etc workflow for another project of mine and while pretty fascinating how this all ties together, I thought that it is perhaps also useful to others who don’t want to rebuild the whole pipeline from scratch every time. (also, competition seems pretty costly). It is pretty simple: Make account, make memory space, upload your stuff, configure how you want it retrieved, setup scoped API key, connect your AI to the hosted MCP → done. RigRAG lets you: upload / index documents search them via a simple HTTP API or MCP optionally configure retrieval settings like top-k, candidate count, chunking, etc. Currently entirely free to use since I would want to gather feedback first if it's worth pursuing further before I spend too much time into it. I’d really appreciate feedback on it, if something is unclear to setup, should be improved etc. I’m not trying to do a big launch yet so this is more of a “please try it, and tell me what sucks or if its good” thing. Here the link again: https://rig-rag.vercel.app And for the MCP: https://rig-rag.vercel.app/api/mcp submitted by /u/Odysseyan [link] [留言]

2026-05-30 原文 →
AI 资讯

Building ReefWatch, a Coral-Powered Production Triage Agent

Production incidents almost never break in one place. The alert fires in one tool. The broken deploy is in Netlify. The suspicious change is in GitHub. The stack trace is in Sentry. The human context is in Slack. The runbook is in Notion. The "is this actually paging someone?" answer is in PagerDuty. A normal chatbot can sound helpful in that situation. It can say things like "you should check your recent deployments" and "look for related errors in Sentry." But that is not triage. That is a polished to-do list. I wanted something more useful: an agent that could go get the evidence, connect the dots across sources, show its work, and give an operator-grade answer grounded in real system data. The design constraint from the start was simple: no evidence, no answer. That became ReefWatch , a Coral-powered production triage agent built to investigate instead of improvise. It discovers the tools connected to a workspace at runtime, queries them as evidence, correlates records across systems, and produces a compact answer only when the facts support one. Coral became the backbone because it turns the messiest part of agent tooling into something the model can actually reason about: SQL . What This Guide Builds By the end of this route, you will have a blueprint for an agent that can: discover connected Coral sources at runtime query production systems through read-only SQL correlate evidence across code, deploys, errors, alerts, chats, and runbooks stream every query and row count into an inspectable UI run the same investigation workflow from a CLI when you want a scriptable path generate an incident report only when the evidence supports one stay focused with policy layers instead of a giant prompt blob In one sentence: ReefWatch is a Coral-powered investigation workspace that lets an agent discover connected tools at runtime, query them with read-only SQL, stream the evidence trail, and generate an incident report only when the facts actually support one. Why Coral B

2026-05-30 原文 →
AI 资讯

Hiring an AI Development Company? 7 Questions to Ask First

Hiring an AI Development Company? Ask These 7 Questions First Most AI projects fail long before deployment. Not because the model is bad. Because teams skip the hard engineering questions. If you're evaluating an AI development company, ask these 7 questions first: 1. How is data secured? AI systems process sensitive business information. Ask: Where is data stored? Is encryption enabled at rest and in transit? Who has access to prompts, logs, and embeddings? Are enterprise security standards followed? Security should be designed in from day one. 2. What observability exists? You can't improve what you can't monitor. A production AI system should include: Request tracing Prompt/version tracking Latency monitoring Cost visibility Error reporting If nobody can explain what happened after a bad output — that's a problem. 3. How do you handle model drift? AI performance changes over time. Questions to ask: How are outputs evaluated? Is feedback collected? How are prompts/versioning managed? What happens when accuracy drops? Production systems need iteration loops. 4. What happens during failure? No system is perfect. Ask: Is there fallback logic? Human review? Retry handling? Graceful degradation? Failure handling matters more than demos. 5. How is access controlled? Enterprise AI systems require permissions. Examples: Role-based access API authentication Audit logs Team-level controls Not everyone should access everything. 6. What compliance assumptions exist? Especially important for regulated industries. Ask whether the system considers: GDPR SOC2 HIPAA Financial or internal compliance rules Compliance cannot be an afterthought. 7. Who owns the infrastructure? Clarify ownership before signing anything. Ask: Who owns the source code? Cloud infrastructure? Models and prompts? Data pipelines? You should avoid vendor lock-in. AI success is rarely about flashy demos. It's about secure infrastructure, reliability, observability, and long-term maintainability. What question

2026-05-30 原文 →
AI 资讯

[Showoff Saturday]: added a text expander to my clipboard extension and its been saving me a ton of typing

been maintaining a privacy first clipboard manager chrome extension for a while. recently shipped a snippets feature where you type /keyword in any text field and it expands to whatever you saved i use it for: - my product pitch so i dont rewrite it every time - boilerplate comments on github or pr reviews - pasting my product link into discussions - common replies i send over and over it supports two types - rich text with formatting for things like emails, and code with syntax highlighting if you need it. the expansion works through a content script on all websites. comes with a management page where you can search filter by type or language and edit your snippets. everything is saved locally only on your device, currently these are not synced, let's see if user needs the sync facility for these or not. NOTE: currently figuring out how to make this feature work on Google Docs and MS Word submitted by /u/nhrtrix [link] [留言]

2026-05-30 原文 →
AI 资讯

Finishing My Personal Website: Mobile-Friendly, Dark Mode, and a Better Projects Section

This is a submission for the GitHub Finish-Up-A-Thon Challenge What I Built I revisited my personal website and decided to turn it into a more complete and polished portfolio. The project originally started as a simple personal website hosted on GitHub Pages. While it was functional, many planned features and improvements were never completed. For this challenge, I am working on improving the mobile experience, adding dark mode support, enhancing the Projects section, improving SEO, fixing existing issues, and making the website more interactive and professional. My goal is to transform an unfinished personal website into a modern portfolio that better represents my work, skills, and projects. Demo Live Website https://ehsankahrizi.github.io/ GitHub Repository https://github.com/Ehsankahrizi/Ehsankahrizi.github.io Current Status This project is currently being improved as part of the GitHub Finish-Up-A-Thon Challenge. Planned improvements include: Better mobile responsiveness Dark mode support Enhanced Projects section Improved SEO More interactive user experience Better website performance Additional pages and content Fixing existing usability issues The Comeback Story When I returned to this project, I realized that many ideas I originally had for the website were still unfinished. Although the website was online, it still had several limitations: The mobile experience needed improvement. Dark mode was not available. The Projects section was incomplete. The contact functionality needed attention. SEO optimization was missing. The website relied on a mostly single-page structure. User interactions were limited. Performance could be improved. Instead of starting a new project, I decided to revisit this existing one and finally complete the improvements that had been postponed. This challenge provided the perfect opportunity to continue development, clean up the codebase, improve the user experience, and turn the website into something I can confidently share with ot

2026-05-30 原文 →
AI 资讯

The Real Sovereign OS - OnemanBSD updated!

I lost more than 60 days but I made a huge update All OnemanBSD OS is now 64 bits. I also removed all bloat like Rust, Wayland and Qt dependencies from all app ports used in the system. (mpv was changed to gnome-mplayer because of that). New apps included (+ fixed source code of everything): audacity (audio editor) godot (game editor) deadbeef (mp3 player) ted (word processor) Also some bug fixes. Here is the link again: http://bialamusic.com/onemanBSD/ Here are my thoughts: I feel that we as humans are loosing control over technology that was created by humans. This is rising some serious and strange questions. I think we now need tools to power the individual so we can fight back. Not corporations. Not governments. Not organizations. Consider this my bullet in this battle. It is now in your hands so you can be active developers not just passive users.

2026-05-30 原文 →
AI 资讯

Anthropic Just Dropped Claude Opus 4.8: What It Means for Developers 🚀

Anthropic just announced Claude Opus 4.8 , a major upgrade to their flagship AI model. If you use AI tools to help you write, debug, or architect software, this release has some huge updates that will change your daily workflow. The best part? It is available right now for the exact same price as Opus 4.7. Here is a quick, no-nonsense breakdown of what is new and why you should care. 1. Smarter Coding and "4x Better Honesty" We have all been there: an LLM confidently hands you a block of code, claiming it’s perfect, only for you to find out it breaks completely. Anthropic spent a lot of time fixing this "false confidence" problem. According to their internal testing, Opus 4.8 is four times less likely to let bugs or flaws in its written code pass by unremarked. It has better judgment, meaning it will actually question a bad plan, catch its own mistakes before showing them to you, and admit when it is uncertain about an edge case. 2. Parallel Coding with "Dynamic Workflows" Available in research preview for Claude Code (Enterprise, Team, and Max plans), Dynamic Workflows allows Claude to break a massive programming task down into smaller pieces. Instead of tackling a codebase line-by-line, it can spin up and run hundreds of parallel subagents at the same time to solve large problems. Anthropic notes that it can manage codebase-scale migrations across hundreds of thousands of lines of code from start to merge, verifying everything against your existing test suites. 3. New "Effort Control" Slider You can now manually choose how much processing power Claude puts into a task on Claude.ai and Cowork: High Effort: Claude thinks longer, reasons deeper, and double-checks its work. Best for complex architecture, tricky debugging, or heavy logic. Low Effort: Claude replies much faster and conserves your token rate limits. Best for quick syntax checks, simple explanations, or boilerplate code. 4. Developer API Upgrades If you are building products on top of Claude's API, Amazon

2026-05-30 原文 →
AI 资讯

How I Built CoralSec Copilot: A Unified Enterprise SOC with Coral & Next.js in 4 Days

The tech industry is currently in a frenzy. Everyone is rushing to build the next big AI application, slapping a chatbot interface onto a database and calling it a day. But in this gold rush, we are leaving something critical behind: Enterprise Security. Living in a Kali Linux environment and spending time hunting vulnerabilities teaches you one fundamental truth: security is entirely about context. Hardcoded API keys, undocumented access escalations, and compliance blind spots remain the number one cause of major data breaches. Security teams don’t just need a chatbot that can answer questions; they need a single pane of glass. They need a Security Operations Center (SOC). For the Pirates of the Coral-Bean Hackathon (hosted by Coral and WeMakeDevs), I decided to tackle this massive industry problem. Over the course of 4 sleepless nights, I built CoralSec Copilot—an AI-powered, unified Enterprise SOC platform. Here is the complete Captain's Log of my entire journey, the architecture, the roadblocks, and a reproducible guide so you can build and run it yourself. Day 1: The Brainstorm, Grok, and Cursor AI When the hackathon was announced, my initial thought was basic: "I'll build a CLI agent that scans code." I fired up my IDE, opened Cursor, and started bouncing ideas around. I even looked into some AI models like Grok to understand how they process vast amounts of real-time data. But while brainstorming the architecture, I hit a wall. Scanning a GitHub commit for a leaked AWS key is great, but what if the AI also knew whether the developer who pushed that commit had recently escalated their admin privileges? What if it knew the exact SOC2 compliance policy from our company’s Notion workspace? To do this traditionally, I would have to write dozens of messy REST API integrations. I'd have to handle rate limits, write custom Python scripts for GitHub, another set for Slack, another for Notion, and then build fragile ETL (Extract, Transform, Load) pipelines to bring all

2026-05-30 原文 →