Mentions
Conversations linking to GitHub, newest first. Times are UTC.
Mentions by source
X
Bluesky
Hacker News
V2EX
Qiita
DEV
Mastodon
Latest posts
This looks interesting. MarcelRoozekrans/Rag.NET. I am using it to implement a personal RAG system with NeoAstra (UI)
Free open source security camera application with object and fire detection and email/SMS alerts #dev #code #python #linux #OpenSource
@DeepSeekHarness Just shipped one: dsh-marktext — MarkText (muya) in the DSH right sidebar. Click any .md → true WYSIWYG (math / Mermaid / tables), autosave + ⌘S. Plugins → Install dsh-marktext Roland0511/dsh-marktext
#MSX RetroS3 Watch をリリースしました✨ game-de-it/RetroS3-Watch (開発中に呼称していた「MSX Watch」は、商標の問題を回避するために「RetroS3 Watch」に改名しています) ✅RetroS3 Watchとは Waveshare ESP32-S3-Touch-AMOLED-1.8 V2を、タッチランチャー、 8BitDo Microコントローラー操作、音声、ステートセーブ、Wi-Fiファイル転送、約60fps表示を 備えたコンパクトなMSX/MSX2互換エミュレーターにするファームウェアです
Teste DLSS 5 ao vivo RX 9070XT - com o AMD NR! Testando o DLSS5 (Neural Rendering) na placa da AMD! Link do Programa: github.com/3zwr1/AMD-NR---OptiScaler/releases/dow… [en-US] Live DLSS 5 test RX 9070XT - with AMD NR! Testing DLSS5 (Neural Rendering) on an AMD graphics card! Program Link: github.com/3zwr1/AMD-NR---OptiScaler/releases/dow… [es-US] Prueba de DLSS 5 en vivo RX 9070XT - ¡con AMD NR! ¡Probando DLSS5 (Renderizado Neuronal) en una tarjeta gráfica AMD! Enlace del programa: github.com/3zwr1/AMD-NR---OptiScaler/releases/dow…
Agent Mesh v0.2.0 Deep in Agent Mesh my agent waited, unheard. Now: one path. Hello. Your agents can now take calls from outside the mesh. Same identity, same policy, one URL each. github.com/google/agentmesh/releases/tag/v0.2.0
Stream Discussion Thread -- Monday, November 02, 2026 Post Stream Discussion Thread --- Docket - Tape to Tape - Just Chatting Today's Top Clip: "gen 1 boomer lul" ^(Clipped by Twitch user) ^(Hikari_Senca) --- Twitch VOD Previous Mega Threads --- ^(Bot created by) ^(/u/AManNamedLear) ^(|) ^(GitHub)
@jani_wacho 6.99 is unlimited basically. We are not suing super expensive models and we get over 500. Messages a month and doing fine. We also have a free version where you use your own API keys. But you need to set it up. kudamusaisiwa/whatsapp-desk
Agent Mesh v0.2.0 Deep in Agent Mesh my agent waited, unheard. Now: one path. Hello. Your agents can now take calls from outside the mesh. Same identity, same policy, one URL each. github.com/google/agentmesh/releases/tag/v0.2.0
Learning GPU programming? 🦀 Check out my project: DevBrewer/learn-gpu It is a casual, hands-on workspace for practicing wgpu, glam, and winit 0.30. Great for following along with tutorials. #RustLang #wgpu #GraphicsProg
Memdoor team-solve 工作流和 50 次运行记录: github.com/guregodevo/memdoor/tree/main/examples/… GVS5H 原方法: slee-persis/GVS5H
Stream Discussion Thread -- Monday, November 02, 2026 Post Stream Discussion Thread --- Docket - Tape to Tape - Just Chatting Today's Top Clip: "gen 1 boomer lul" ^(Clipped by Twitch user) ^(Hikari_Senca) --- Twitch VOD Previous Mega Threads --- ^(Bot created by) ^(/u/AManNamedLear) ^(|) ^(GitHub)
备课的时候满世界找素材最让人头疼,现在这个问题也有开源工具来管了。 tchMaterial-parser 专门针对国家中小学智慧教育平台,能把平台上的教学材料扒下来存到本地,课件、教案、学习任务单、练习题这些附件一个不落。 🔗 happycola233/tchMaterial-parser t.co
You now could self host and potentially run your own @ProtonPrivacy / @ProtonMail competitor, using open source server re implementation, and their very own web and mobile clients! Euroton/euroton-server t.co
Nick 5.1 is out. Signed protection updates, stronger local detection, better responsible-app attribution, and a more reliable Endpoint Security pipeline. Still free, open source, and running locally on your Mac. github.com/EhsanAzish80/Nick/releases/tag/v5.1.0
☺️ 说起来 xiaogpt 现在也由 republic 作为 ai provider 驱动了! bubbuild/republic
Repo: sahenjp/RustXNG Their retrieval benchmark (SealQA): github.com/sahenjp/RustXNG/blob/main/docs/SEALQA.… I track fast rising open source AI repos every day at ossradar.net
@zygard77 @X Let's connect! Currently working on a bunch of project, lately an open-source project where I gave local LLMs the ability to make and take phone calls. oxnw/ai-phone
I built a tool to check whether your Flutter/Dart dependencies are still maintained I’ve added a new feature to Flutterverse, Flutter/Dart ecosystem tracker (now tracking 10,000+ packages and projects). You can paste your pubspec.yaml, pubspec.lock, or a list of packages, and it’ll check the maintenance status of your direct dependencies. It categorizes packages into five verdicts, from healthy to needing replacement, and suggests alternatives when a dependency is becoming stale. A few other things: - Runs entirely in your browser. Your pubspec is never uploaded. - Shows an overall dependency health score. - Package maintainers can add health verdict badges to their READMEs. The data refreshes daily from pub.dev and GitHub. give it a try: flutterverse.org github: YeLwinOo-Steve/flutterverse Love to get your feedbacks for it!
Idea for the Epstein RAG app: a confidence note on answers. When retrieval only finds weak matches, the answer should say so up front instead of sounding sure. AbhisumatK/Epstein_Files_RAG
Allowing newer transitive dependencies with haskell-flake I'm trying to use haskell-flake ( srid/haskell-flake ) with some libraries that need to be invoked with newer dependencies. I tried to use extraBuildFlags but I don't think this is working as intended The flake { inputs = { nixpkgs.url = "github:nixos/nixpkgs/nixpkgs-unstable"; flake-parts.url = "github:hercules-ci/flake-parts"; haskell-flake.url = "github:srid/haskell-flake"; }; outputs = inputs@{ self, nixpkgs, flake-parts, ... }: flake-parts.lib.mkFlake { inherit inputs; } { systems = nixpkgs.lib.systems.flakeExposed; imports = [ inputs.haskell-flake.flakeModule ]; perSystem = { self', pkgs, ... }: { haskellProjects.default = { basePackages = pkgs.haskell.packages.ghc9124; packages = { }; settings = { localize = { extraBuildFlags = [ "--allow-newer=bytestring" ]; }; text-format-heavy = { check = false; broken = false; extraBuildFlags = [ "--allow-newer=text" ]; }; }; devShell = { tools = hp: { inherit (pkgs) cabal-install; inherit (hp) cabal-gild; }; }; }; packages.default = self'.packages.nixtest; }; }; } And cabal file ... build-depends: base ^>=4.21.2.0 , localize hs-source-dirs: app default-language: Haskell2010 If I use the following cabal.project file it builds as expected packages: ./ package nixtest allow-newer: , localize:bytestring , text-format-heavy:text There's no real code, simply the output from cabal init -n Is what I'm trying to do here possible, or do I need to go through the effort of patching transitive deps if I want to use nix as a build tool?
CRE Agent Skills is for the specific task already on your desk. 90 standalone skills for work like rent roll analysis, lease review, lender comparisons and investment committee memos. Use the pieces you need. ahacker-1/cre-agent-skills
I wanted my task list to do its own chores. OpenTodo 0.20.0 “routines” solve this problem: small chained automations / with and without AI Most to-do apps either have no automation, or a single “when X, do Y” rule. And the to-do list is full of chores that are almost the same every time: moving overdue things, tidying the Inbox, setting up the same checklist every Monday, nudging someone in a shared project. i.redd.it So OpenTodo got routines. A routine is a trigger plus a few steps, and the editor shows each step as a plain sentence, so you can read what it’ll do. Some I actually use: - Every Friday at 17:00: find my tasks that are overdue and not urgent → move them to Monday → comment “pushed from Friday”. - When I complete a task in “Trips”: if it has the label packing, create “Unpack and wash” for the day after. - Every Monday morning: create the “Weekly reset” checklist from a template in my Home project. - When a task lands in the Inbox from email: if the subject mentions an invoice, move it to Finance and set a deadline 14 days out. Things I cared about while building it: - You see it before it runs. “Try it” runs the routine against your real data and shows exactly which tasks it would change. Nothing is written until you save. - It’s dynamic, not hand-picked. Steps work on whatever earlier steps found (“find tasks where…”, then “take the first 3”, then “comment on each”), so a routine keeps working next week. - Starters, or one sentence. Pick a starter, or type “every Friday move my overdue work tasks to Monday”, and it drafts the routine for you to check. - Optional AI steps, with review first. A step can ask an AI to judge or summarise (“is this task really urgent?”, “summarise this week’s done tasks”). By default it proposes, and you approve the changes. Only you can turn on applying without asking; an agent can’t. - Run history. Every run is logged with what it changed, plus a “Routines since your last visit” note, and everything can be undone. - Shared projects. A household or team project can have its own routines that everyone in it can see. It’s part of OpenTodo, a task manager I’ve been building that runs on your own server or computer. It’s free and open source (AGPL), with no account anywhere else and no telemetry. There’s a web app that works offline, an Android app, and CalDAV. - Try the demo (no sign-up): demo.open-todo.app - Routines guide: open-todo.app - Code: OpenTodoApp/OpenTodo I’d really like to hear what chores you’d automate in your own lists. And what’s the one automation you wish your current app had?
Logtide: 1 Year After the First Commit (The Real Numbers) --- title: "Logtide: 1 Year After the First Commit (The Real Numbers)" published: true tags: opensource, startup, devops, webdev canonical_url: logtide.dev --- On November 26, 2025 I pushed a commit called "Initial Commit - LogWard v0.1.0 alpha". Four days later I published a post on dev.to titled I built an Open Source Datadog alternative because ELK was eating my RAM. It had a Docker Compose file, a SvelteKit 5 frontend, TimescaleDB instead of Elasticsearch, and Redis with BullMQ for the job queue. That was a year ago. In January I wrote a 2-months post with every number I had, good and bad. This is the same exercise at twelve months. Same rule as last time: no bullshit, just numbers. --- The numbers | | Launch (Nov 2025) | 2 months (Jan 2026) | 1 year (Nov 2026) | | --- | --- | --- | --- | | GitHub stars | 0 | 223 | 457 | | Docker pulls (backend image) | 0 | 3,000+ | 47,000+ | | Commits | 1 | n/a | 2,020 | | Releases | 0.1.0 | 0.4.x | 50+, latest 1.6.0 | | Issues opened | 0 | 27 | 103 | | Merged PRs from other people | 0 | 1 | 17 | | Storage engines | 1 | 1 | 3 | | Official SDKs | 3 | 5 | 7 | The stars curve flattened after the virtualizationhowto.com spike. The Docker pulls curve did not. Fifteen times more pulls with only twice the stars tells me what I suspected at two months: the people running Logtide are mostly not the people starring repos. They are self-hosters who pull an image, put it behind a reverse proxy, and never open an issue unless something breaks. The commit count is mostly me. 1,982 of the 2,020 commits have my name on them. The remaining ones are small, but they are the ones I remember. --- The year in releases A quick timeline, because a year of changelogs is long and nobody should read it. - January: forced rebrand from LogWard to Logtide after a trademark conflict. 0.4.0 shipped the same week. - January / February: 0.5.0 made Redis optional. 0.6.0 added PII masking at ingestion, and ClickHouse as a second storage engine. - February: 0.7.0 added OTLP metrics, service maps and audit logs. Logs, traces and metrics in one place. - March: 0.8.0 added MongoDB as a third storage engine, plus browser observability. - April: 0.9.0 replaced the fixed dashboard with custom dashboards, added uptime monitoring with public status pages, and log parsing pipelines. - June: 1.0.0. More on what that release actually was below. - July / August: inbound webhook receivers, digest emails, error regression detection, geo map panels. - October: 1.6.0, the biggest release of the year. A rebuilt UI, one query language that works on every storage engine, an incidents inbox, Slack, Teams and PagerDuty destinations, and an extension system. --- What I got wrong in the 2-months post Re-reading the January post is a bit uncomfortable. A few things I wrote with confidence turned out to be wrong. "OpenTelemetry metrics: postponed indefinitely." Only two users had asked for it, and I wrote that most people use Prometheus anyway. Six weeks later 0.7.0 shipped OTLP metrics. Logs, traces and metrics in one place turned out to matter more than a vote count in an issue tracker. The lesson I wrote at the time was "build what users request". It still holds, but it is not the whole picture. "TimescaleDB was the right choice." It still is, as the default. But by March Logtide also ran on ClickHouse (0.6) and MongoDB (0.8), through a storage layer called reservoir. The cost was real: every query, every filter and every panel now has to behave identically on three engines. Getting that right took until 1.6.0, where the same search syntax finally parses to the same results everywhere. "Redis might be unnecessary. Next version might remove it." This one I got right, mostly. Since 0.5.0 Redis is optional: without it, the job queue runs on PostgreSQL through graphile-worker. It is not removed: if you already run Redis, BullMQ is still there. Making a dependency optional turned out to be more useful than deleting it. --- What 1.0 actually was At 0.9.0 I wrote that we were not jumping straight to a 1.0 declaration, because we wanted the announcement to mean something. What it ended up meaning was a security audit. Before cutting 1.0, I went through every data access path in the backend looking for one specific thing: a query that could read another organization's data. I found some. The logs and traces query APIs accepted a projectId parameter and trusted it without checking that it belonged to the API key making the request. There were also tenant-table queries missing an organization filter, protected only by the route above them. All of it was fixed in 1.0, along with a dedicated isolation test suite and CI checks so the same pattern fails the build if it comes back. PII masking also became fail-closed: before 1.0, if a masking rule threw, the batch was stored unmasked with a warning in the console. For a product whose whole pitch is GDPR, that was the worst possible failure mode. Then, right after 1.0, a batch of issues was reported privately through coordinated disclosure by KIberblick.de, including a cross-tenant read on the dashboard endpoints and a stored XSS. Fixed in 1.0.3. I am genuinely grateful for that report. It is humbling to run an audit and then have someone else find what you missed a week later, but that is the system working. The lesson I'd give anyone building a multi-tenant product solo: the hard part is not the features. It is making sure every single query is scoped, and keeping it that way while you ship features fast. --- What worked Shipping small and often. 53 tags in a year is roughly one a week. Most were boring patch releases. Boring patch releases are what make people trust a project enough to upgrade it. Docker Compose as the main install path. I said at two months that Docker Compose working in five minutes got more stars than any feature. That is still true. There is a Helm chart now, but the Compose file is what most people use. Writing about the technical decisions, not the product. The most read posts I wrote this year were not the release announcements. I Replaced Redis with PostgreSQL got 340 reactions, the microservices math got 154. The average release post got around 15. People came for the Postgres opinions, and some of them found the log management along the way. SDKs in the languages people actually use. Node.js, Python, PHP, Kotlin/Java, C#, Go and Ruby, plus Laravel, Symfony, Slim and WordPress integrations. The Kotlin SDK was a community contribution in the first two months, and I still think about that every time someone asks for a new language. --- What didn't The rebrand. I covered it in January, but it is worth repeating because it is the cheapest lesson on this page: check the trademark before you name anything. Doing everything alone. 98% of the commits are mine. That is fast, but it means every architectural mistake is mine too, and there is nobody to say "this is a bad idea" before it ships. The extension system in 1.6.0 is partly an answer to that: a way for people to build on Logtide without having to get a PR through me. --- Thank you To everyone who opened an issue, especially the ones that started with "this is probably a dumb question" and were not. To the 17 merged pull requests that did not come from me. To the people who reported security issues privately instead of on Twitter. And to the self-hosters running Logtide somewhere I will never see, who never open an issue because nothing is broken. You are the reason the Docker pull counter keeps moving. --- If you're using Logtide, I'd love to hear how. Open a discussion, open an issue, or drop a ⭐ if it has been useful. - 🌐 Cloud: logtide.dev - 💻 GitHub: logtide-dev/logtide - 📖 Docs: logtide.dev Here's to year two. 🌊
CRE Acquisition Orchestrator brings a 31-role AI deal team into one local workspace. Work through multifamily diligence, underwriting, financing, legal and closing, with citations and human review. ahacker-1/cre-acquisition-orchestrator
Slime girl sex~ Made using: FP-Studio/framepack-studio LoRA 1: civitai.red LoRA 2: civitai.red My models and art are free, so I appreciate your support! Find more here: civitai.red #nsfw #aiart #hunyuanvideo #civitai #sex #framepack #framepackstudio
A good RAG system is a librarian, not a biographer. It does not decide what the documents mean. It finds the right pages, shows you the shelf marks, and lets you read. AbhisumatK/Epstein_Files_RAG
orrery-tui: Terminal Solar System Wanted to show off this solar system model in the terminal. tjyank/orrery-tui
A single photo of a peacock mantis shrimp turned into an explosive 3D teardown, and I am losing my mind. The look is straight from the picture, but the rest is pure, chaotic Three.js engineering. Devjyoti-D/Bio-Mech-3D t.co
Why RAG and not a fine tuned model for the Epstein files: the documents are the product. Retrieval keeps the source passages there at answer time, ready to be read and checked, instead of blended away into a model. AbhisumatK/Epstein_Files_RAG
Static Recomp Theatrhythm PS4 on PC Hey guys, recently playing around with static recomps. This is slightly modded to have some controller compatibility with Xbox and Keyboard, some controller hints was also updated to adapt that. This version uses the PS4 version and would default to the 4K targeted render resolution and scaled to your resolution. I am ironically not that great at rhythm games, but I do love listening to the arrangements, so I haven't gone through all nooks and crannies especially on difficult maps, but if you guys found issues along the way, feel free to post it. The version was tested on NVIDIA (Windows) and AMD (CachyOS), the game is very light it should be able to run on a Steam Deck spec-wise (untested). I wouldn't say it's completely bug free, but I've been squashing quite a lot of the very visible ones. Repo : YAPhoa/theatrhythm-fbl-pc It should be plug and play as long as you are providing your own PS4 dump, but if you have any feedback in terms of the launcher flow, you can let me know as well.
De 28 webs que analicé, solo Clerk llega al nivel 5 de SEO para agentes de #IA. GitHub, Stripe, OpenAI y #Anthropic están en el 1. La mía, en el 2. Para medirlo he hecho verify-seo-for-agents, un binario en Rust con 23 comprobaciones. Va en #ClaudeCode. marcmayol/verify-seo-for-agents
JiaFeiMiao-K-Cat/DiscImageStudio 光学ディスクに(データを書きつつ)こんなことできるんだ!? t.co
I've just released Larastan-Livewire v2.6.0 with that new feature and some fixes! I also noticed that we recently crossed >1M downloads 🤯 github.com/calebdw/larastan-livewire/releases/tag… t.co
A skill needs to teach, guide, explain and provide reference. Those are different information needs. In Second Read, proposed edits are explicit: replace, insert, move or delete. Each is anchored to the original words. C-Kapsalis/second-read
Learning how to use @github daily has been such a journey pay-kit#411
De 28 webs que analicé, solo Clerk llega al nivel 5 de SEO para agentes de #IA. GitHub, Stripe, OpenAI y #Anthropic están en el 1. La mía, en el 2. Para medirlo he hecho verify-seo-for-agents, un binario en Rust con 23 comprobaciones. Va en #ClaudeCode. marcmayol/verify-seo-for-agents t.co
Repo if you want to try it: ai-dynamo/snapshot
Download: carbon.alexandrejoly.me Code, MIT: AlexDemzz/carbon
[OS] MeowDisplay: use your Mac from your iPhone/Android or iPad (free & open source) - Hiya! People call me J, and I've been working on an app called MeowDisplay, short for Mac Everywhere, On Whatever Display. The problem My main goal was pretty simple. I just wanted to have my Mac handy, even when I'm not sitting in front of it. Whether I'm running a long render, waiting for tests to finish, or running sessions with Claude, sometimes I just want to pull out my iPhone, check what's happening, interact with my Mac if needed, and get on with other stuff instead of having to go back and sit infront of it. I mainly use my iPhone, so I've put quite a lot of effort into making the Mac genuinely usable from a phone, rather than just shrinking a desktop or adapting an iPad interface to a tiny screen. Features in the 2.0 Release of MeowDisplay Window view and multitasking: Instead of viewing your entire desktop, you can work with individual Mac windows, arrange them into panes, split, resize, swap, or group them into tabs. There's also Stage Peek for quickly switching between windows. Multiple displays: You can mirror or extend your Mac's desktop, with each connected device having its own independent display mode. You could extend to an iPad, mirror to an iPhone, and use Window view on another device at the same time. Remote access: You can use your Mac even when you're away from home, provided you have a private network like Tailscale configured. I actually spent three days in another city with my Mac at home, checking in from my phone whenever I needed to. I've also tested it over 5G on a moving bus, lol. Controls and customization: Natural Touch, Classic Touch, Trackpad mode, customizable shortcuts, gestures and control trays. I've tried to make the interactions feel as natural as possible, especially on an iPhone. There's also audio streaming, Remote Finder, clipboard sharing, Mac-to-Mac connections and a bunch of smaller additions. Comparison I've tried alternatives like AnyDesk, RustDesk and others, but they never quite felt like what I wanted. Apple's Sidecar is great for iPads, but doesn't support iPhones. MeowDisplay focuses on making the Mac practical to use from a phone, with touch interactions and individual-window multitasking rather than just a conventional remote desktop view. I'm not claiming it performs better than those apps. It's just a different approach to how you interact with your Mac. Pricing MeowDisplay is completely free and open source, with no ads, subscriptions, in-app purchases or accounts required. I intend to keep it that way as well as intending to maintain and improve it with time. Availability Version 2.0 is officially out for Mac, iPhone and iPad! The main Mac app requires macOS 14 or later. Android is currently in closed testing, and there's also a separate receiver-only app for Macs running macOS 12 or later. App Store Website / Downloads GitHub I'm the developer, and guys, trust me when I say this feels better to use, try it if this is a kind of thing you need and do share feedback, both positive and negative, it's also found out that the majority of people who have no problems with something don't always do a review/feedback, whilst most of the people having a negative experience, do post about it, so you never mostly see about the good things and the bad things get highlighted.. I've been building and testing this on my 8 GB M2 MacBook Air, and Xcode has NOT been particularly kind to that setup 😭 ifykyk There's still plenty to improve, but I've been using MeowDisplay myself throughout development, and I'm excited to finally have 2.0 out :DDD
Theatrhythm Final Bar Line (PS4) Hey guys, recently playing around with static recomps. I think this is a title that not many people know about but actually quite interesting. It's a rhythm game from final fantasy, and it hosts hundreds of tracks across their titles. This is slightly modded to have some controller compatibility with Xbox and Keyboard, some controller hints was also updated to adapt that. This version uses the PS4 version and would default to the 4K targeted render resolution and scaled to your resolution. I am ironically not that great at rhythm games, but I do love listening to the arrangements, so I haven't gone through all nooks and crannies especially on difficult maps, but if you guys found issues along the way, feel free to post it. The version was tested on NVIDIA (Windows) and AMD (CachyOS), the game is very light it should be able to run on a Steam Deck spec-wise (untested). I wouldn't say it's completely bug free, but I've been squashing quite a lot of the very visible ones. Not going to bother you with flashy trailers and stuffs, honestly I am mostly just interested on making things work and playable. Repo : YAPhoa/theatrhythm-fbl-pc It should be plug and play as long as you are providing your own PS4 dump, but if you have any feedback in terms of the launcher flow, you can let me know as well.
A year after my last Lilith project, I’m back—with a more interactive desktop Lilith hihi~ it’s been about a year since I last shared my Lilith project here. I wanted to show you what I’ve been working on recently. I really liked the noexistance of lilith, and wanted to give her more ways to interact with what I’m doing. So I built on that idea: she can react to Claude Code activity while I’m coding, control music, respond to interactions, can be tucked away—then return to where she was. She uses the original game animations and recorded voice lines, with optional local AI chat through Ollama. Generated AI voice is disabled for now; I wasn’t happy with how it sounded, and keeping her feeling like Lilith matters more to me than adding another feature. Since it's unofficial fan project, and you’ll need your own installed copy of the game for the initial asset setup. The character assets aren’t included in the download, so please support the original creators. There’s now a Windows setup installer, with update and uninstall options too. Project and download: nuttyuwu/lilith-desktop There are still things I want to improve, but I’m happy to finally share her again. I’d love to hear what you think—or what little interactions you’d like her to have. Edit 1 (・・;) I wasn’t expecting aloft of linux users. Last time i did this they wanted Windows. But soon i will start the linux support I cant test linux cuz currently i don’t have a linux machine w me
How to Find GitHub Issues Opened by a Specific Author Use the native repository Search issues field and append author:USERNAME to is:issue state:open. The genuine example uses python/cpython and cmaloney, observed in the initial public issue list. Enter submits; actual result query and author rows are retained. This demonstrates open issues in one repository, not every issue everywhere or account identity verification. Author is not assignee. Counts and UI can change. No issue creation, edit, assignment or closure. Genuine native screenshot holds/crops and authorized synthetic owner voice planned. GitHub attribution; no affiliation or demand claim. Source: github.com/python/cpython/issues Narration uses the channel owner's authorized synthetic voice. Native UI screenshots are edited with crops, cuts and holds. [ar] كيفية العثور على المشكلات التي تم فتحها بواسطة مؤلف معين على GitHub استخدم حقل "البحث عن المشكلات" في المستودع الأصلي، وأضف اسم المستخدم (author:USERNAME) إلى حالة المشكلة (is:issue state:open). يستخدم المثال الأصلي مكتبة python/cpython وcmaloney، كما هو موضح في قائمة المشكلات العامة الأولية. أدخل عمليات الإرسال؛ وسيتم الاحتفاظ بنتائج الاستعلام وبيانات المؤلف. يوضح هذا المشكلات المفتوحة في مستودع واحد، وليس جميع المشكلات في كل مكان أو التحقق من هوية الحساب. المؤلف ليس هو المُسند إليه. قد تتغير الإحصائيات وواجهة المستخدم. لا توجد عمليات إنشاء أو تعديل أو إسناد أو إغلاق للمشكلات. لقطات الشاشة الأصلية الأصلية مُجهزة بخاصية التثبيت/الاقتصاص، والصوت الاصطناعي المُصرّح به للمالك. يُنسب العمل إلى GitHub؛ لا توجد أي انتماءات أو مطالبات. المصدر: github.com/python/cpython/issues يستخدم التعليق الصوتي الصوت الاصطناعي المُصرّح به لمالك القناة. يتم تعديل لقطات شاشة واجهة المستخدم الأصلية من خلال الاقتصاص والقص والتثبيت. [bn] কোনো নির্দিষ্ট লেখকের খোলা গিটহাব ইস্যুগুলো কীভাবে খুঁজে বের করবেন নেটিভ রিপোজিটরির 'সার্চ ইস্যু' ফিল্ডটি ব্যবহার করুন এবং is:issue state:open-এর সাথে author:USERNAME যুক্ত করুন। আসল উদাহরণটিতে পাইথন/সিপাইথন এবং সিমালনি ব্যবহার করা হয়েছে, যা প্রাথমিক পাবলিক ইস্যু তালিকায় দেখা যায়। সাবমিট এন্টার করুন; আসল ফলাফল কোয়েরি এবং লেখকের সারিগুলো সংরক্ষিত থাকবে। এটি একটি রিপোজিটরির খোলা ইস্যুগুলো প্রদর্শন করে, সব জায়গার প্রতিটি ইস্যু বা অ্যাকাউন্টের পরিচয় যাচাইকরণ নয়। লেখক অ্যাসাইনি নন। সংখ্যা এবং UI পরিবর্তন হতে পারে। কোনো ইস্যু তৈরি, সম্পাদনা, অ্যাসাইনমেন্ট বা বন্ধ করা যাবে না। আসল নেটিভ স্ক্রিনশট হোল্ড/ক্রপ এবং অনুমোদিত সিন্থেটিক মালিকের কণ্ঠস্বর ব্যবহারের পরিকল্পনা রয়েছে। গিটহাব অ্যাট্রিবিউশন; কোনো অ্যাফিলিয়েশন বা দাবির আবেদন নেই। উৎস: github.com/python/cpython/issues বর্ণনায় চ্যানেল মালিকের অনুমোদিত সিন্থেটিক কণ্ঠস্বর ব্যবহার করা হয়। নেটিভ UI স্ক্রিনশটগুলো ক্রপ, কাট এবং হোল্ড দিয়ে সম্পাদনা করা হয়। [de-DE] So findest du GitHub-Issues eines bestimmten Autors Verwenden Sie das Suchfeld des nativen Repositorys und fügen Sie Autor:BENUTZERNAME zu „is:issue state:open“ hinzu. Das Beispiel verwendet Python/CPython und Cmdaloney, wie in der ursprünglichen öffentlichen Issue-Liste zu sehen. Geben Sie „submits“ ein; die tatsächlichen Suchergebnisse und Autorenzeilen bleiben erhalten. Dies demonstriert offene Issues in einem Repository, nicht alle Issues weltweit oder die Verifizierung der Kontoidentität. Der Autor ist nicht der Bearbeiter. Zähler und Benutzeroberfläche können sich ändern. Es werden keine Issues erstellt, bearbeitet, zugewiesen oder geschlossen. Original-Screenshots werden beschnitten und mit einer autorisierten synthetischen Stimme des Kanalinhabers versehen. GitHub-Quellenangabe; keine Zugehörigkeits- oder Anspruchsansprüche. Quelle: github.com/python/cpython/issues Die Sprachausgabe verwendet die autorisierte synthetische Stimme des Kanalinhabers. Screenshots der nativen Benutzeroberfläche werden beschnitten und mit Ausschnitten versehen. [es-US] Cómo encontrar problemas de GitHub abiertos por un autor específico Utilice el campo de búsqueda de incidencias del repositorio nativo y añada `author:USERNAME` a `is:issue state:open`. El ejemplo real utiliza `python/cpython` y `cmaloney`, tal como se observa en la lista inicial de incidencias públicas. Introduzca las solicitudes; se conservan la consulta de resultados y las filas de autores. Esto muestra incidencias abiertas en un repositorio, no todas las incidencias en todas partes ni la verificación de la identidad de la cuenta. El autor no es el responsable. Los recuentos y la interfaz de usuario pueden cambiar. No se permite la creación, edición, asignación ni cierre de incidencias. Se planean capturas de pantalla nativas con recortes y la voz sintética autorizada del propietario. Atribución de GitHub; sin afiliación ni reclamación de derechos. Fuente: github.com/python/cpython/issues La narración utiliza la voz sintética autorizada del propietario del canal. Las capturas de pantalla de la interfaz de usuario nativa se editan con recortes y pausas. [fr-FR] Comment trouver les issues GitHub ouvertes par un auteur spécifique Utilisez le champ de recherche des problèmes du dépôt natif et ajoutez auteur:NOM_UTILISATEUR à is:issue state:open. L'exemple fourni utilise Python/CPython et cmaloney, comme indiqué dans la liste publique initiale des problèmes. Saisissez les soumissions ; les résultats de la requête et les lignes d'auteur sont conservés. Ceci illustre les problèmes ouverts dans un seul dépôt, et non tous les problèmes partout ni la vérification d'identité des comptes. L'auteur n'est pas le responsable. Le nombre et l'interface utilisateur peuvent changer. Aucune création, modification, attribution ou fermeture de problème n'est possible. Capture d'écran native avec recadrage et mise en pause, et voix de synthèse autorisée prévue. Attribution GitHub ; aucune affiliation ni revendication de droits d'auteur. Source : github.com/python/cpython/issues La narration utilise la voix de synthèse autorisée du propriétaire du canal. Les captures d'écran natives sont modifiées avec recadrage, découpage et mise en pause. [hi] GitHub पर किसी विशिष्ट लेखक द्वारा खोले गए इश्यू (issues) कैसे खोजें नेटिव रिपॉजिटरी के सर्च इश्यू फ़ील्ड का उपयोग करें और is:issue state:open में author:USERNAME जोड़ें। मूल उदाहरण में python/cpython और cmaloney का उपयोग किया गया है, जो प्रारंभिक सार्वजनिक इश्यू सूची में देखा गया है। सबमिट दर्ज करें; वास्तविक परिणाम क्वेरी और लेखक पंक्तियाँ बरकरार रखी जाती हैं। यह एक रिपॉजिटरी में खुले इश्यू को दर्शाता है, न कि हर जगह के सभी इश्यू या खाता पहचान सत्यापन को। लेखक असाइनी नहीं है। संख्याएँ और UI बदल सकते हैं। कोई इश्यू निर्माण, संपादन, असाइनमेंट या समापन नहीं। वास्तविक नेटिव स्क्रीनशॉट होल्ड/क्रॉप और अधिकृत कृत्रिम स्वामी की आवाज़ की योजना बनाई गई है। GitHub का श्रेय; कोई संबद्धता या दावा नहीं। स्रोत: github.com/python/cpython/issues नैरेटर चैनल स्वामी की अधिकृत कृत्रिम आवाज़ का उपयोग करता है। नेटिव UI स्क्रीनशॉट को क्रॉप, कट और होल्ड के साथ संपादित किया गया है। [id] Cara Menemukan Issue GitHub yang Dibuka oleh Penulis Tertentu Gunakan kolom Pencarian Masalah repositori asli dan tambahkan author:USERNAME ke is:issue state:open. Contoh asli menggunakan python/cpython dan cmaloney, yang diamati dalam daftar masalah publik awal. Masukkan pengajuan; hasil kueri aktual dan baris penulis dipertahankan. Ini menunjukkan masalah terbuka dalam satu repositori, bukan setiap masalah di mana pun atau verifikasi identitas akun. Penulis bukan penerima tugas. Jumlah dan UI dapat berubah. Tidak ada pembuatan, pengeditan, penugasan, atau penutupan masalah. Tangkapan layar asli yang ditahan/dipotong dan suara pemilik sintetis resmi direncanakan. Atribusi GitHub; tidak ada klaim afiliasi atau permintaan. Sumber: github.com/python/cpython/issues Narasi menggunakan suara sintetis resmi pemilik saluran. Tangkapan layar UI asli diedit dengan pemotongan, pemotongan, dan penahanan. [it] Come trovare le segnalazioni di problemi (Issues) aperte da un autore specifico su GitHub Utilizza il campo di ricerca "issues" del repository nativo e aggiungi `author:USERNAME` a `is:issue:state:open`. L'esempio originale utilizza `python/cpython` e `cmaloney`, come osservato nell'elenco pubblico iniziale delle issue. Inserisci i risultati; le righe relative ai risultati effettivi e agli autori vengono mantenute. Questo esempio mostra le issue aperte in un repository, non tutte le issue ovunque o la verifica dell'identità dell'account. L'autore non è l'assegnatario. I conteggi e l'interfaccia utente possono cambiare. Non sono previste la creazione, la modifica, l'assegnazione o la chiusura delle issue. Sono previsti ritagli/sequenze di screenshot nativi e una voce sintetica autorizzata del proprietario. Attribuzione GitHub; nessuna affiliazione o rivendicazione di proprietà. Fonte: github.com/python/cpython/issues La narrazione utilizza la voce sintetica autorizzata del proprietario del canale. Gli screenshot dell'interfaccia utente nativa sono modificati con ritagli, tagli e sezioni. [iw] כיצד למצוא בעיות ב-GitHub שנפתחו על ידי מחבר ספציפי השתמשו בשדה חיפוש הבעיות במאגר המקורי והוסיפו את author:USERNAME ל- is:issue state:open. הדוגמה המקורית משתמשת ב-python/cpython ו-cmaloney, כפי שנצפה ברשימת הבעיות הציבורית הראשונית. הזינו submits; שורות שאילתת התוצאה בפועל ושורות המחבר נשמרות. זה מדגים בעיות פתוחות במאגר אחד, לא כל בעיה בכל מקום או אימות זהות חשבון. המחבר אינו מקבל הקצאה. ספירות וממשק המשתמש יכולים להשתנות. אין יצירה, עריכה, הקצאה או סגירה של בעיות. החזקות/חיתוכים מקוריים של צילומי מסך וקול סינתטי מורשה של הבעלים מתוכננים. ייחוס GitHub; אין תביעת שיוך או דרישה. מקור: github.com/python/cpython/issues הקריינות משתמשת בקול הסינתטי המורשה של בעל הערוץ. צילומי מסך מקוריים של ממשק המשתמש ערוכים עם חיתוכים, חיתוכים והחזקות. [ja] 特定の投稿者が作成したGitHubのIssueを検索する方法 ネイティブリポジトリの「課題検索」フィールドを使用し、「is:issue state:open」に「author:USERNAME」を追加してください。実際の例では、最初の公開課題リストで確認されたpython/cpythonとcmaloneyを使用しています。「submits」と入力すると、実際のクエリ結果と著者行が保持されます。これは、すべてのリポジトリのすべての課題やアカウントの本人確認ではなく、1つのリポジトリ内の未解決課題を示しています。著者は担当者ではありません。カウントとUIは変更される可能性があります。課題の作成、編集、割り当て、クローズはできません。ネイティブのスクリーンショットは、トリミングと認証済みの合成音声で作成されます。GitHubの帰属表示はありますが、提携関係や要求はありません。ソース:github.com/python/cpython/issues ナレーションには、チャンネル所有者の認証済み合成音声が使用されます。ネイティブUIのスクリーンショットは、トリミング、カット、ホールドなどの編集が施されています。 [ko] 특정 작성자가 제기한 GitHub 이슈를 찾는 방법 기본 저장소의 이슈 검색 필드를 사용하고, 작성자:사용자 이름을 is:이슈 상태:열림에 추가하세요. 실제 예시는 초기 공개 이슈 목록에서 볼 수 있는 Python/cpython 및 cmaloney를 사용합니다. 제출 버튼을 누르면 실제 검색 결과와 작성자 행이 유지됩니다. 이는 모든 이슈 또는 계정 신원 확인이 아닌, 하나의 저장소에 있는 열린 이슈들을 보여줍니다. 작성자는 담당자가 아닙니다. 이슈 개수 및 UI는 변경될 수 있습니다. 이슈 생성, 편집, 담당자 지정 또는 종료는 불가능합니다. 실제 기본 UI 스크린샷은 일부 영역을 잘라내고 편집하며, 승인된 담당자의 음성을 사용할 예정입니다. GitHub 출처를 명시하며, 제휴 또는 권리 주장은 없습니다. 출처: github.com/python/cpython/issues 내레이션에는 채널 소유자의 승인된 음성이 사용됩니다. 기본 UI 스크린샷은 일부 영역을 잘라내고 편집합니다. [ml] ഒരു പ്രത്യേക രചയിതാവ് തുറന്ന GitHub പ്രശ്നങ്ങൾ എങ്ങനെ കണ്ടെത്താം നേറ്റീവ് റിപ്പോസിറ്ററി സെർച്ച് ഇഷ്യൂസ് ഫീൽഡ് ഉപയോഗിച്ച് author:USERNAME എന്നത് is:issue state:open എന്നതിലേക്ക് ചേർക്കുക. പ്രാരംഭ പബ്ലിക് ഇഷ്യൂ ലിസ്റ്റിൽ നിരീക്ഷിച്ച python/cpython, cmaloney എന്നിവ യഥാർത്ഥ ഉദാഹരണത്തിൽ ഉപയോഗിക്കുന്നു. submit-കൾ നൽകുക; യഥാർത്ഥ ഫല അന്വേഷണവും രചയിതാവിന്റെ വരികളും നിലനിർത്തിയിരിക്കുന്നു. ഇത് ഒരു റിപ്പോസിറ്ററിയിലെ തുറന്ന പ്രശ്നങ്ങൾ കാണിക്കുന്നു, എല്ലായിടത്തും എല്ലാ ലക്കമോ അക്കൗണ്ട് ഐഡന്റിറ്റി വെരിഫിക്കേഷനോ അല്ല. രചയിതാവ് അസൈനി അല്ല. എണ്ണവും UI-യും മാറാൻ കഴിയില്ല. പ്രശ്നം സൃഷ്ടിക്കൽ, എഡിറ്റ്, അസൈൻമെന്റ് അല്ലെങ്കിൽ ക്ലോഷർ എന്നിവയില്ല. യഥാർത്ഥ നേറ്റീവ് സ്ക്രീൻഷോട്ട് ഹോൾഡുകൾ/ക്രോപ്പുകൾ, അംഗീകൃത സിന്തറ്റിക് ഉടമയുടെ ശബ്ദം ആസൂത്രണം ചെയ്തിരിക്കുന്നു. GitHub ആട്രിബ്യൂഷൻ; അഫിലിയേഷനോ ഡിമാൻഡ് ക്ലെയിമോ ഇല്ല. ഉറവിടം: github.com/python/cpython/issues ആഖ്യാനം ചാനൽ ഉടമയുടെ അംഗീകൃത സിന്തറ്റിക് വോയ്സ് ഉപയോഗിക്കുന്നു. ക്രോപ്പുകൾ, കട്ടുകൾ, ഹോൾഡുകൾ എന്നിവ ഉപയോഗിച്ച് നേറ്റീവ് UI സ്ക്രീൻഷോട്ടുകൾ എഡിറ്റ് ചെയ്യുന്നു. [nl-NL] Hoe vind je GitHub-issues die door een specifieke auteur zijn geopend? Gebruik het zoekveld voor problemen in de native repository en voeg author:USERNAME toe aan is:issue state:open. Het echte voorbeeld gebruikt python/cpython en cmaloney, zoals te zien is in de oorspronkelijke openbare lijst met problemen. Voer 'submits' in; de daadwerkelijke zoekresultaten en auteurs worden behouden. Dit toont openstaande problemen in één repository, niet alle problemen overal of verificatie van accountidentiteit. De auteur is niet de toegewezen persoon. Aantallen en de gebruikersinterface kunnen veranderen. Geen probleemcreatie, -bewerking, -toewijzing of -sluiting. Echte native screenshots met uitsnijdingen en een geautoriseerde synthetische stem van de eigenaar zijn gepland. Vermelding van GitHub; geen affiliatie of claim op rechten. Bron: github.com/python/cpython/issues De gesproken tekst maakt gebruik van de geautoriseerde synthetische stem van de kanaaleigenaar. Native UI-screenshots worden bewerkt met uitsnijdingen, knippen en uitsnijdingen. [pa] GitHub 'ਤੇ ਕਿਸੇ ਖਾਸ ਲੇਖਕ ਦੁਆਰਾ ਖੋਲ੍ਹੇ ਗਏ ਮੁੱਦਿਆਂ (Issues) ਨੂੰ ਕਿਵੇਂ ਲੱਭਿਆ ਜਾਵੇ ਮੂਲ ਰਿਪੋਜ਼ਟਰੀ ਖੋਜ ਮੁੱਦੇ ਖੇਤਰ ਦੀ ਵਰਤੋਂ ਕਰੋ ਅਤੇ ਲੇਖਕ:USERNAME ਨੂੰ is:issue state:open ਵਿੱਚ ਜੋੜੋ। ਅਸਲੀ ਉਦਾਹਰਣ python/cpython ਅਤੇ cmaloney ਦੀ ਵਰਤੋਂ ਕਰਦੀ ਹੈ, ਜੋ ਕਿ ਸ਼ੁਰੂਆਤੀ ਜਨਤਕ ਮੁੱਦੇ ਸੂਚੀ ਵਿੱਚ ਦੇਖੇ ਗਏ ਹਨ। ਦਰਜ ਕਰੋ; ਅਸਲ ਨਤੀਜਾ ਪੁੱਛਗਿੱਛ ਅਤੇ ਲੇਖਕ ਕਤਾਰਾਂ ਨੂੰ ਬਰਕਰਾਰ ਰੱਖਿਆ ਜਾਂਦਾ ਹੈ। ਇਹ ਇੱਕ ਰਿਪੋਜ਼ਟਰੀ ਵਿੱਚ ਖੁੱਲ੍ਹੇ ਮੁੱਦਿਆਂ ਨੂੰ ਦਰਸਾਉਂਦਾ ਹੈ, ਹਰ ਮੁੱਦੇ ਨੂੰ ਹਰ ਜਗ੍ਹਾ ਜਾਂ ਖਾਤਾ ਪਛਾਣ ਤਸਦੀਕ ਨਹੀਂ ਕਰਦਾ। ਲੇਖਕ ਅਸਾਈਨੀ ਨਹੀਂ ਹੈ। ਗਿਣਤੀ ਅਤੇ UI ਬਦਲ ਸਕਦੇ ਹਨ। ਕੋਈ ਮੁੱਦਾ ਬਣਾਉਣਾ, ਸੰਪਾਦਨ, ਅਸਾਈਨਮੈਂਟ ਜਾਂ ਬੰਦ ਨਹੀਂ। ਅਸਲੀ ਮੂਲ ਸਕ੍ਰੀਨਸ਼ੌਟ ਹੋਲਡ/ਕ੍ਰੌਪਸ ਅਤੇ ਅਧਿਕਾਰਤ ਸਿੰਥੈਟਿਕ ਮਾਲਕ ਦੀ ਆਵਾਜ਼ ਦੀ ਯੋਜਨਾ ਬਣਾਈ ਗਈ ਹੈ। GitHub ਵਿਸ਼ੇਸ਼ਤਾ; ਕੋਈ ਮਾਨਤਾ ਜਾਂ ਮੰਗ ਦਾਅਵਾ ਨਹੀਂ। ਸਰੋਤ: github.com/python/cpython/issues ਕਥਨ ਚੈਨਲ ਮਾਲਕ ਦੀ ਅਧਿਕਾਰਤ ਸਿੰਥੈਟਿਕ ਆਵਾਜ਼ ਦੀ ਵਰਤੋਂ ਕਰਦਾ ਹੈ। ਮੂਲ UI ਸਕ੍ਰੀਨਸ਼ੌਟਸ ਨੂੰ ਫਸਲਾਂ, ਕੱਟਾਂ ਅਤੇ ਹੋਲਡਾਂ ਨਾਲ ਸੰਪਾਦਿਤ ਕੀਤਾ ਜਾਂਦਾ ਹੈ। [pl] Jak znaleźć zgłoszenia na GitHubie utworzone przez konkretnego autora Użyj natywnego pola wyszukiwania zgłoszeń w repozytorium i dopisz author:USERNAME do is:issue state:open. W oryginalnym przykładzie użyto python/cpython i cmaloney, co zaobserwowano na początkowej publicznej liście zgłoszeń. Wprowadź dane; rzeczywiste wyniki zapytania i wiersze autora są zachowywane. To pokazuje otwarte zgłoszenia w jednym repozytorium, a nie wszystkie zgłoszenia wszędzie, ani weryfikację tożsamości konta. Autor nie jest cesjonariuszem. Liczniki i interfejs użytkownika mogą się zmieniać. Brak tworzenia, edycji, przypisania ani zamknięcia zgłoszenia. Oryginalne natywne zrzuty ekranu i zaplanowane autoryzowane syntetyczne głosy właścicieli. Atrybucja GitHub; brak powiązań lub roszczeń. Źródło: github.com/python/cpython/issues Narracja wykorzystuje autoryzowany syntetyczny głos właściciela kanału. Natywne zrzuty ekranu interfejsu użytkownika są edytowane z przycinaniem, cięciami i przycięciami. [pt-BR] Como encontrar issues do GitHub abertas por um autor específico Use o campo de pesquisa de problemas nativo do repositório e adicione `author:USERNAME` a `is:issue state:open`. O exemplo genuíno usa python/cpython e cmaloney, conforme observado na lista pública inicial de problemas. Insira os resultados; a consulta real e as linhas de autor são mantidas. Isso demonstra problemas abertos em um repositório, não todos os problemas em todos os lugares ou verificação de identidade da conta. O autor não é o responsável. As contagens e a interface do usuário podem mudar. Não há criação, edição, atribuição ou fechamento de problemas. Capturas de tela nativas genuínas com recortes e voz sintética autorizada do proprietário planejadas. Atribuição do GitHub; sem afiliação ou reivindicação de demanda. Fonte: github.com/python/cpython/issues A narração usa a voz sintética autorizada do proprietário do canal. As capturas de tela da interface nativa são editadas com recortes e pausas. [ru] Как найти задачи GitHub, созданные конкретным автором Используйте встроенное поле поиска задач в репозитории и добавьте author:USERNAME к is:issue state:open. В реальном примере используются python/cpython и cmaloney, как видно из первоначального публичного списка задач. Введите отправленные данные; фактический результат запроса и строки с автором сохраняются. Это демонстрирует открытые задачи в одном репозитории, а не все задачи повсюду или проверку личности учетной записи. Автор не является назначенным исполнителем. Количество и пользовательский интерфейс могут изменяться. Нет создания, редактирования, назначения или закрытия задач. Планируется использование встроенных функций блокировки/обрезки скриншотов и авторизованного синтетического голоса владельца. Указание авторства GitHub; нет претензий на принадлежность или требования. Источник: github.com/python/cpython/issues Озвучивание использует авторизованный синтетический голос владельца канала. Скриншоты встроенного пользовательского интерфейса редактируются с помощью обрезки, вырезания и блокировки. [ta] குறிப்பிட்ட நபர் GitHub-இல் பதிவிட்ட சிக்கல்களைத் தேடுவது எப்படி நேட்டிவ் ரெபாசிட்டரியின் 'சிக்கல்களைத் தேடு' (Search issues) புலத்தைப் பயன்படுத்தி, 'is:issue state:open' என்பதில் author:USERNAME என்பதைச் சேர்க்கவும். உண்மையான எடுத்துக்காட்டு, ஆரம்பப் பொது சிக்கல் பட்டியலில் காணப்பட்டதைப் போல, python/cpython மற்றும் cmaloney-ஐப் பயன்படுத்துகிறது. சமர்ப்பிக்கவும்; உண்மையான முடிவு வினவல் மற்றும் ஆசிரியர் வரிசைகள் தக்கவைக்கப்படுகின்றன. இது எல்லா இடங்களிலும் உள்ள எல்லா சிக்கல்களையும் அல்லது கணக்கு அடையாளச் சரிபார்ப்பையும் அல்லாமல், ஒரு ரெபாசிட்டரியில் உள்ள திறந்த சிக்கல்களைக் காட்டுகிறது. ஆசிரியர் என்பவர் உரிமைதாரர் அல்ல. எண்ணிக்கைகளும் பயனர் இடைமுகமும் மாறக்கூடும். சிக்கல் உருவாக்கம், திருத்தம், ஒதுக்கீடு அல்லது மூடல் எதுவும் இல்லை. உண்மையான நேட்டிவ் ஸ்கிரீன்ஷாட் ஹோல்ட்ஸ்/கிராப்ஸ் மற்றும் அங்கீகரிக்கப்பட்ட செயற்கை உரிமையாளர் குரல் திட்டமிடப்பட்டுள்ளது. கிட்ஹப் உரிமை கோரல்; எந்தவொரு இணைப்பும் அல்லது உரிமை கோரலும் இல்லை. மூலம்: github.com/python/cpython/issues விவரிப்பு, சேனல் உரிமையாளரின் அங்கீகரிக்கப்பட்ட செயற்கைக் குரலைப் பயன்படுத்துகிறது. நேட்டிவ் பயனர் இடைமுக ஸ்கிரீன்ஷாட்கள் கிராப்ஸ், கட்ஸ் மற்றும் ஹோல்ட்ஸ் மூலம் திருத்தப்பட்டுள்ளன. [te] GitHubలో ఒక నిర్దిష్ట వ్యక్తి ఓపెన్ చేసిన ఇష్యూలను ఎలా కనుగొనాలి నేటివ్ రిపోజిటరీ సెర్చ్ ఇష్యూస్ ఫీల్డ్ను ఉపయోగించండి మరియు is:issue state:open కు author:USERNAME ను జోడించండి. అసలైన ఉదాహరణ పైథాన్/సిపైథాన్ మరియు సిమలోనీని ఉపయోగిస్తుంది, ఇది ప్రారంభ పబ్లిక్ ఇష్యూ జాబితాలో గమనించవచ్చు. సబ్మిట్లను నమోదు చేయండి; అసలు ఫలిత క్వెరీ మరియు రచయిత వరుసలు అలాగే ఉంచబడతాయి. ఇది ఒకే రిపోజిటరీలోని ఓపెన్ ఇష్యూలను ప్రదర్శిస్తుంది, అంతేగానీ ప్రతిచోటా ఉన్న ప్రతి ఇష్యూను లేదా ఖాతా గుర్తింపు ధృవీకరణను కాదు. రచయిత అసైనీ కాదు. గణనలు మరియు UI మారవచ్చు. ఇష్యూ సృష్టి, సవరణ, కేటాయింపు లేదా మూసివేత ఉండవు. అసలైన నేటివ్ స్క్రీన్షాట్ హోల్డ్స్/క్రాప్స్ మరియు అధీకృత సింథటిక్ ఓనర్ వాయిస్ ప్లాన్ చేయబడ్డాయి. గిట్హబ్ అట్రిబ్యూషన్; ఎలాంటి అనుబంధం లేదా హక్కుల క్లెయిమ్ లేదు. మూలం: github.com/python/cpython/issues వ్యాఖ్యానం ఛానెల్ యజమాని యొక్క అధీకృత సింథటిక్ వాయిస్ను ఉపయోగిస్తుంది. నేటివ్ UI స్క్రీన్షాట్లు క్రాప్స్, కట్స్ మరియు హోల్డ్స్తో సవరించబడతాయి. [uk] Як знайти issue на GitHub, створені конкретним автором Використовуйте поле пошуку задач у рідному репозиторії та додайте author:USERNAME до is:issue state:open. У справжньому прикладі використовуються python/cpython та cmaloney, що спостерігається у початковому публічному списку задач. Введіть submits; фактичний результат запиту та рядки автора зберігаються. Це демонструє відкриті задачі в одному репозиторії, а не кожну задачу скрізь або перевірку особи облікового запису. Автор не є правонаступником. Кількість та інтерфейс користувача можуть змінюватися. Створення, редагування, призначення або закриття задач не передбачено. Заплановано збереження/обрізання знімків екрана у справжньому рідному репозиторії та авторизований синтетичний голос власника. Атрибуція GitHub; жодних претензій щодо приналежності чи вимог. Джерело: github.com/python/cpython/issues Озвучування використовує авторизований синтетичний голос власника каналу. Знімки екрана рідного інтерфейсу користувача редагуються з обрізанням, вирізанням та утриманням.
DeepSeek just open-sourced a coding agent that picks up work from GitHub on its own deepseek-ai/dsh-superagent-prototype
Erdős问题 #650 迎来精确解:min(m, ⌈2√m⌉) #孙宇晨奖 聚焦数学经典问题的完整解决与完整Lean形式化验证。 解题者:Wouter van Doorn、Yanyang Li、 Quanyu Tang(@Vieta__jumping) Lean验证者:Wouter van Doorn 获奖记录👇 github.com/TheJustinSunPrize/awards/blob/main/awa… t.co
Slime girl sex~ Made using: FP-Studio/framepack-studio LoRA 1: civitai.red LoRA 2: civitai.red My models and art are free, so I appreciate your support! Find more here: civitai.red #nsfw #aiart #hunyuanvideo #civitai #sex #framepack #framepackstudio
Give your agent a way to leave a note without interrupting you. Professor Clippy's README separates leave_message from ask_user, which waits up to 10 minutes by default. On Windows, ordinary notes stay quiet; questions pop up. geetbatth/professor-clippy
Paper: arxiv.org Code: facebookresearch/textseal Joint work with @pierrefdz and others at Meta Superintelligence Labs @AIatMeta. Feedback welcome.