{"payload":{"header_redesign_enabled":false,"results":[{"body":"Anyone up for showing their homepage? Would like to see different ways of organizing apps. I ll start with mine\n\nimage\n","created":"2022-11-01T04:09:54.000Z","hl_text":"Anyone up for showing their homepage? Would like to see different ways of organizing apps. I ll start with mine\n\nimage\n","hl_title":"Share your homepage","id":"4526046","num_comments":298,"number":473,"repo":{"repository":{"id":528313152,"name":"homepage","owner_id":122929872,"owner_login":"gethomepage","updated_at":"2024-06-01T16:58:40.564Z","has_issues":true}},"title":"Share your homepage","url":"/gethomepage/homepage/discussions/473","updated":"2024-06-01T22:14:47.000Z","user_avatar_url":"https://avatars.githubusercontent.com/u/43682030?s=48&v=4","user_id":43682030,"user_login":"javijuji"},{"body":"posts/giscus\n\nIntroducing giscus: a comment system built on GitHub Discussions.\n\nhttps://laymonage.com/posts/giscus\n","created":"2021-05-15T14:57:28.000Z","hl_text":"posts/giscus\n\nIntroducing giscus: a comment system built on GitHub Discussions.\n\nhttps://laymonage.com/posts/giscus\n","hl_title":"posts/giscus","id":"3367022","num_comments":188,"number":14,"repo":{"repository":{"id":341141696,"name":"base","owner_id":6379424,"owner_login":"laymonage","updated_at":"2024-06-01T11:47:14.186Z","has_issues":true}},"title":"posts/giscus","url":"/laymonage/base/discussions/14","updated":"2024-06-01T22:13:02.000Z","user_avatar_url":"https://avatars.githubusercontent.com/in/106117?s=48&v=4","user_id":81026895,"user_login":"giscus[bot]"},{"body":"Hey guys. You might have noticed the somewhat slower and haphazard updates to NewPipe for the last few releases. The\nthing is, NewPipe was started, like so many others in FOSS, as an enthusiast project. It s been over 7 years since then,\nand the age of the codebase is starting to show through spaghetti code, outdated UI, bad design choices and instability.\n\nIt has gotten to the point that we re having difficulties even maintaining the current code and fixing bugs, let alone\nadding new features, due to complex interconnections and lack of proper modularity. Progress has been slow, since\ndevelopers were focused on fixing nasty bugs. Often users requested features that would make sense, but nobody had the\ntime (and, sometimes, knowledge of the codebase) to implement them.\n\nTo mitigate the issues we initially tried to do incremental refactors of various components. Take for example the\nplayer, which has often been deemed a hot pile of garbage : it underwent a couple major Pull Requests that restructured\nit while maintaining all features. Although now the code is a bit better, new crashes and unwanted behaviors have\narisen, because the interaction between the old and the new code is not optimal. We tried again and again to debug the\nproblems, without luck.\n\nAt the moment NewPipe is relying on libraries and components that have become outdated, which might not only drive users\naway from the app, but also push away developers wanting to get some experience on new technologies. We need to migrate\nto Material Design 3, Kotlin and Jetpack Compose, and unfortunately doing so basically requires rewriting everything.\n\nSo, we ve discussed and discussed this ad nauseam. We re very sure the old code needs to go, no matter what, to be\nreplaced by a modern and professional codebase. But we can t decide on the approach to get there.\n\nAnyone who s been in the FOSS community for long has come across at least one or two failed rewrites or refactors, and\nwe don t want to repeat such tragic history. We believe NewPipe really has the potential to be a staple app in people s\ndevices, if only we could get across this massive hurdle and come out the other side relatively intact.\n\nWhat we need from you guys is advice. Preferably, experienced advice. Do we just dump the old code into maintenance mode\nand start afresh? Or replace it piece by piece like the Ship of Theseus? A combination of the two? Or something else\nentirely?\n\nPlease let us know. Also, if you don t have any directly helpful advice, please, please restrict yourself to just\nupvoting or leaving a thumbs up instead of commenting, so that there is less noise and more info in the thread. We all\nknow how fantastic walls of text are at putting us off from reading, and we d like to avoid that.\n\nAlso, if you are experienced in Android mobile development and would like to help us out with the rewrite, be sure to\nreach out to us! We will be using the most modern components whenever possible, as detailed below, so it is sure going\nto be a good learning experience for everyone involved. As a first step, please join the IRC from the ReadMe.\n\nBy the way, don t worry, all currently open PRs that introduce big features will be merged in NewPipe 0.26.0 or future\nreleases of the current app. See the related Project and also take a look at the plans we have for the current app\nbelow.\n\nThanks! The NewPipe team.\n\nWhat approach do we want to use?\n\n  - migrate the existing codebase of the app:\n      - = risks:\n          - strange issues between new and old code;\n          - keeping an architecture which could be bad in some places;\n          - going nowhere;\n          - lack of interest from external contributors.\n      - = benefits:\n          - staying on one repository only;\n          - better handling of issues.\n  - create a new app and reuse good code:\n      - = risks:\n          - a lot of time before reaching feature parity with the current app;\n          - abandonment of devs due to the huge work required.\n      - = benefits:\n          - creating a modularized app in an easier way, and following good architecture and dependency models, hence\n            making migration processes easier too;\n          - potential increase of interest for NewPipe projects, which could lead to more (quality) contributions and to\n            new team members;\n          - embedding more community input in the app.\n\nSimilar or common issues are being raised increasingly in the Extractor repo, so these questions could be considered for\nthe Extractor too.\n\nKey elements we should use and not forget during development\n\n  - Good design thinking: possibility of contacting UI/UX designers and using community feedback to create new app\n    designs:\n    \n      - = use Material 3 design system\n    \n      - = think about accessibility and form factors\n\n  - Asking feedback from the community and taking it into account where that s relevant: results of a subreddit poll\n    returns around 80% in favour;\n\n  - Better organization: good use of Projects, which we would use to plan what should be in the next releases, what is\n    in progress, what s remaining\n    \n      - = we ve started to do this in the recent release, and we should grow our usage of these tools\n\n  - Try to get new and experienced people into the team: most of us are students passionate about technology, but:\n    \n      - we have other things to do in our life, and some or all of us may leave the NewPipe project at some point;\n    \n      - we can t know everything, and we lack knowledge in some domains.\n\n  - Apply more agile principles such as doing smaller but more frequent release cycles.\n\n  - For the development by itself:\n    \n      - Jetpack Compose;\n      - ViewModels;\n      - Hilt for dependency injection;\n      - modules for app components (player, downloader, channel, search, settings, ...) with usage of interfaces for\n        communication between them;\n      - use Kotlin everywhere in the app to reduce code and bugs;\n      - Jetpack Media3 for the player.\n      - use https://penpot.app to create designs (it s an OSS alternative to Figma)\n\nDecide what we want to ship in the current app\n\n  - highly requested features, mostly the ones which are blockers for content accessibility (also see the related\n    Project):\n    \n      - comment replies (almost ready);\n      - channel tabs (almost ready);\n    \n    = work of these features probably needs to be done by the team due to code and/or approaches from external\n    contributions not quite meeting our standards\n    \n      - multiple audio tracks support (already merged, released in 0.25.2);\n      - advanced search filters (could be a blocker for channel tabs due to the reworking of filters in the extractor);\n      - better quality of images, by introducing multiple images support (a pull request was opened).\n\n  - bug fixes and regressions, in particular the most annoying ones (we can t guarantee we will be able to debug\n    everything though, for the aforementioned reasons):\n    \n      - fullscreen issues on some devices since the player UI rewrite;\n      - player App Not Responding and crashes on some devices and in some cases;\n      - ViewHolders not attached crash;\n      - fullscreen button with autorotation enabled.\n","created":"2023-05-26T08:06:39.000Z","hl_text":"Hey guys. You might have noticed the somewhat slower and haphazard updates to NewPipe for the last few releases. The\nthing is, NewPipe was started, like so many others in FOSS, as an enthusiast project. ...","hl_title":"Planning a new, modern and stable NewPipe","id":"5235273","num_comments":171,"number":10118,"repo":{"repository":{"id":41889031,"name":"NewPipe","owner_id":22159318,"owner_login":"TeamNewPipe","updated_at":"2024-05-31T07:23:39.666Z","has_issues":true}},"title":"Planning a new, modern and stable NewPipe","url":"/TeamNewPipe/NewPipe/discussions/10118","updated":"2024-06-01T21:55:42.000Z","user_avatar_url":"https://avatars.githubusercontent.com/u/36421898?s=48&v=4","user_id":36421898,"user_login":"Stypox"},{"body":"Feel free to ask questions about mini.nvim which are not really suitable for an issue. Like How do I setup ...? , etc.\n\nAnother approach is to create a separate discussion in Q A category, if you have trouble working with this particular\ndiscussion (as it is quite populated already). This approach might be even more preferable as it will allow filtering\nquestions by module.\n","created":"2022-01-02T14:29:57.000Z","hl_text":"Feel free to ask questions about mini.nvim which are not really suitable for an issue. Like How do I setup ...? , etc.\n\nAnother approach is to create a separate discussion in Q A category, if you have ...","hl_title":"Ask questions","id":"3775769","num_comments":335,"number":33,"repo":{"repository":{"id":378088544,"name":"mini.nvim","owner_id":24854248,"owner_login":"echasnovski","updated_at":"2024-06-01T11:47:49.120Z","has_issues":true}},"title":"Ask questions","url":"/echasnovski/mini.nvim/discussions/33","updated":"2024-06-01T21:42:00.000Z","user_avatar_url":"https://avatars.githubusercontent.com/u/24854248?s=48&v=4","user_id":24854248,"user_login":"echasnovski"},{"body":"TLDR: We have completely overhauled the UI for Frigate to focus on specific common user goals. It’s a big change and we\nhope you love it. This is just where we started, and the new UI isn’t entirely at feature parity with the current\nrelease yet.\n\nUpdated Documentation\n\nGuided Demo of new UI\n\nWe plan to release the first beta soon.\n\nBackground\n\nFrigate started as a stateless object detection pipeline for live video fees with information relayed over MQTT to be\nused in Home Assistant. Initially, I had no intention of building a UI for it. HomeAssistant was the UI. After a few\nyears of releases in January 2021, a community contribution with a basic web UI was made as a part of version 0.8.0.\nSince then, the UI has always been treated as a basic interface to expose some of the backend information that Frigate\nwas using to detect and track objects. As new features like clips and recordings were added the UI was updated to\nprovide an interface to view them.\n\nA new approach\n\nAs Frigate has become more mature, it has evolved from a real time object detection pipeline into an NVR. While it still\nlacks some of the customization and features from NVR solutions that have existed for longer, many users are migrating\nfrom those platforms and using Frigate as their primary NVR solution. However, Frigate’s UI was never designed around\nspecific user goals, nor was any real thought put into the efficiency of accomplishing common tasks.\n\nFrigate+ was created in part to help fund the future development of Frigate. While still in the early phases, the\ninitial revenue from Frigate+ subscriptions created an opportunity to hire outside resources for revamping Frigate’s UI.\nAfter looking at various options, I decided to hire Jim Designs.\n\nThe Goals\n\nI wanted to design the new UI around specific user goals with the intent to have a UI that allows accomplishing those\ngoals as quickly and efficiently as possible. The following goals are where we started. I expect we will continue to\nfind better ways of accomplishing these goals in the future as well as incorporate additional goals.\n\nWhat is happening right now and/or what just happened?\n\nThe first use case centers around the need to quickly see what is happening or what just happened. Imagine you hear a\nsound outside, your dog barks, or the doorbell rings and you want to quickly be able to see your cameras.\n\nThe new home page for Frigate is intended to be a real time dashboard for your cameras. Recent alerts are represented by\nanimated thumbnails in a filmstrip view above your camera feeds. Your camera images update once per minute when no\ndetectable activity is occurring to conserve bandwidth and resources. As soon as any motion is detected, cameras\nseamlessly switch to a live stream. In addition, camera groups have been added so you can quickly switch between indoor\nand outdoor cameras.\n\nSelecting a camera takes you to a new live view where the scroll wheel can be used to zoom in and out.\n\nWhat happened last night (or the past 24 hours)?\n\nA common use case for security cameras is reviewing last night’s footage for any concerning activity. The first step of\nthat process is checking to see what Frigate detected. In the current UI, this is accomplished by scrolling through your\nevents. Because events are simply low level tracked objects, their time ranges may overlap or still be in progress. This\nmakes it difficult to review a timeline of video without jumping around or watching the same section of video multiple\ntimes. If a person walks by with their dog and a car drives by at the same time, you will end up with 3 separate events\nall with overlapping time ranges. It is difficult to reason about what periods of time you have and haven’t reviewed.\n\nIn order to switch to a more timeline oriented review process, we implemented a new area of the app for reviewing video\nfootage. When reviewing, Frigate intelligently identifies parts of your timeline for review by leveraging the underlying\ndata about motion and tracked objects. These time periods are mutually exclusive, so once you have reviewed a portion of\nthe timeline for a camera, it is marked as reviewed.\n\nThe other primary focus was on efficiency. We wanted users to be able to review these segments as efficiently as\npossible. Rather than scrolling through a timeline and trying to align a single point with an indication of activity, we\nimplemented a scrollable grid of thumbnails alongside a timeline. Hovering (or swiping on mobile) over the thumbnails\nwill start a preview playback for the segment inline. You can also grab the progress bar to scrub through the segment.\n\nAfter watching a segment, it is marked as reviewed.\n\nLastly, not all segments are created equal. Video of people who enter your property are a different priority than those\nwalking by on the sidewalk. By default, all person and car objects are considered alerts. You can refine what ends up in\nthe alert tab by configuring required zones for your events.\n\nWas anything missed last night?\n\nIn the current release, there isn’t a way to see motion activity on a timeline and watch video at that time. The ability\nto scrub video for things Frigate missed has been one of the most common feature requests.\n\nWithin the Motion tab of review, you can now scrub through the timeline for all cameras simultaneously with a timeline\nshowing relative motion activity.\n\nIn order to avoid scrubbing over time periods already included in alerts and detections, you can scrub in motion only\nmode.\n\nOther Notable Improvements\n\n  - Many improvements have been made to improve the usability of the mobile UI\n  - Live view now displays full-resolution camera streams\n  - Cameras with non standard aspect ratios like panoramic and portrait fit into the UI seamlessly\n  - Zone / mask editor has been improved to be easier to use and makes more options fully configurable in the UI\n  - Tune motion detection in real-time directly in the UI\n","created":"2024-04-28T13:46:47.000Z","hl_text":"TLDR: We have completely overhauled the UI for Frigate to focus on specific common user goals. It’s a big change and we\nhope you love it. This is just where we started, and the new UI isn’t entirely at ...","hl_title":"Rebuilding the Frigate UI for 0.14","id":"6573557","num_comments":769,"number":11136,"repo":{"repository":{"id":167694194,"name":"frigate","owner_id":569905,"owner_login":"blakeblackshear","updated_at":"2024-06-01T17:00:36.417Z","has_issues":true}},"title":"Rebuilding the Frigate UI for 0.14","url":"/blakeblackshear/frigate/discussions/11136","updated":"2024-06-01T21:25:44.000Z","user_avatar_url":"https://avatars.githubusercontent.com/u/569905?s=48&v=4","user_id":569905,"user_login":"blakeblackshear"},{"body":"zh\n\n探索Ultralytics YOLOv8 的完整指南，这是一个高速、高精度的对象检测和图像分割模型。安装、预测、培训教程等。\n\nhttps://docs.ultralytics.com/zh\n\n!-- sha1: 68a5d7a179f27b047cf588c7cf817eabe6480c78 --\n","created":"2024-02-05T07:08:20.000Z","hl_text":"zh\n\n探索Ultralytics YOLOv8 的完整指南，这是一个高速、高精度的对象检测和图像分割模型。安装、预测、培训教程等。\n\nhttps://docs.ultralytics.com/zh\n\n!-- sha1: 68a5d7a179f27b047cf588c7cf817eabe6480c78 --\n","hl_title":"zh","id":"6180324","num_comments":253,"number":8026,"repo":{"repository":{"id":535360445,"name":"ultralytics","owner_id":26833451,"owner_login":"ultralytics","updated_at":"2024-06-01T16:19:46.202Z","has_issues":true}},"title":"zh","url":"/ultralytics/ultralytics/discussions/8026","updated":"2024-06-01T21:12:59.000Z","user_avatar_url":"https://avatars.githubusercontent.com/in/106117?s=48&v=4","user_id":81026895,"user_login":"giscus[bot]"},{"body":"guides/object-counting/\n\nObject Counting Using Ultralytics YOLOv8\n\nhttps://docs.ultralytics.com/guides/object-counting/\n\n!-- sha1: da88fee982f75bf17a09a4170133d7a4b7b5ddf1 --\n","created":"2024-02-09T11:36:42.000Z","hl_text":"guides/object-counting/\n\nObject Counting Using Ultralytics YOLOv8\n\nhttps://docs.ultralytics.com/guides/object-counting/\n\n!-- sha1: da88fee982f75bf17a09a4170133d7a4b7b5ddf1 --\n","hl_title":"guides/object-counting/","id":"6199322","num_comments":365,"number":8112,"repo":{"repository":{"id":535360445,"name":"ultralytics","owner_id":26833451,"owner_login":"ultralytics","updated_at":"2024-06-01T16:19:46.202Z","has_issues":true}},"title":"guides/object-counting/","url":"/ultralytics/ultralytics/discussions/8112","updated":"2024-06-01T20:58:49.000Z","user_avatar_url":"https://avatars.githubusercontent.com/in/106117?s=48&v=4","user_id":81026895,"user_login":"giscus[bot]"},{"body":"Track - Ultralytics YOLOv8 Docs\n\nExplore YOLOv8n-based object tracking with Ultralytics BoT-SORT and ByteTrack. Learn configuration, usage, and\ncustomization tips.\n\nhttps://docs.ultralytics.com/modes/track/\n\n!-- sha1: 5a4ecf75307fa090e21cf7ee93788dc248817042 --\n","created":"2023-05-18T04:05:48.000Z","hl_text":"Track - Ultralytics YOLOv8 Docs\n\nExplore YOLOv8n-based object tracking with Ultralytics BoT-SORT and ByteTrack. Learn configuration, usage, and\ncustomization tips.\n\nhttps://docs.ultralytics.com/modes/track/ ...","hl_title":"Track - Ultralytics YOLOv8 Docs","id":"5207930","num_comments":135,"number":2687,"repo":{"repository":{"id":535360445,"name":"ultralytics","owner_id":26833451,"owner_login":"ultralytics","updated_at":"2024-06-01T16:19:46.202Z","has_issues":true}},"title":"Track - Ultralytics YOLOv8 Docs","url":"/ultralytics/ultralytics/discussions/2687","updated":"2024-06-01T20:49:13.000Z","user_avatar_url":"https://avatars.githubusercontent.com/in/106117?s=48&v=4","user_id":81026895,"user_login":"giscus[bot]"},{"body":"Hi,\n\nI m now building a deploy workflow for a monorepo, and trying to set up a CI workflow triggered by a push to a special\nbranch (like production) for deployment. We currently merge regular PRs to the main branch using Squash and merge by\nenabling Require linear history option, and merging deploy PRs to the production branch with Create a merge commit in\norder to avoid unexpected divergent. It works, but not perfect because Squash and merge button is present when merging a\nPR to the production branch. As far as I searched, I couldn t find a good way to enforce developers to use Create a\nmerge commit .\n\nIs there a good way to achieve that? So far, I could find a stackoverflow saying it s not possible.\n\nThanks in advance!\n","created":"2022-01-31T12:04:31.000Z","hl_text":"Hi,\n\nI m now building a deploy workflow for a monorepo, and trying to set up a CI workflow triggered by a push to a special\nbranch (like production) for deployment. We currently merge regular PRs to the ...","hl_title":"Disable "Squash and merge" on some specific branches","id":"3844868","num_comments":477,"number":10809,"repo":{"repository":{"id":301573344,"name":"community","owner_id":93784371,"owner_login":"community","updated_at":"2024-06-01T07:23:41.921Z","has_issues":false}},"title":"Disable \"Squash and merge\" on some specific branches","url":"/community/community/discussions/10809","updated":"2024-06-01T20:47:12.000Z","user_avatar_url":"https://avatars.githubusercontent.com/u/3426676?s=48&v=4","user_id":3426676,"user_login":"makotoshimazu"},{"body":"Mod Compatibility\n\nA maintained list of known mods and compatibility state in regards to Connector.\n\nHelp us test!\n\nWe welcome any help. If you have tested or experienced issues with a mod and would like let us know, just comment on\nthis post and we ll look into listing the mod. Thanks!\n\nCompatibility statuses\n\n  - ✅Compatible - This mods is tested and verified to be compatible with Connector\n  - ⚠️Functional - This mod loads with Connector, but might contain bugs\n  - ❌Incompatible - This mod is not compatible with Connector\n\nStatus list\n\n| 📦 Mod Name | 🔗 Link | ❓ Status | 🗒️ Notes |\n| :-: | :-: | :-: | :-: |\n| LambDynamicLights | Modrinth | ✅ |  |\n| Tech Reborn | CurseForge | ✅ |  |\n| Terrestria | Modrinth | ✅ |  |\n| Traverse | Modrinth | ✅ |  |\n| Immersive Portals | Modrinth | ⚠️Functional | Likely to cause bugs when used with other (Forge) mods. br/ See the\nissue tracker for ongoing issues |\n| amecs api | GitHub | ❌ | Conflicting mixins with Forge s keybind API |\n| Forge Config API Port | CurseForge | ❌ | Provides modified versions of Forge config classes |\n| Reach Entity Attributes | GitHub | ❌ | Conflicts with Forge attribute modifiers |\n| Sodium | Modrinth | ❌ | Conflicts with Forge s Early Loading Screen |\n| FREX | Modrinth | ❌ | Conflicts with Forge s rendering pipeline |\n| Indium | Modrinth | ❌ | Conflicts with Forge s rendering pipeline |\n","created":"2023-08-08T15:01:16.000Z","hl_text":"Mod Compatibility\n\nA maintained list of known mods and compatibility state in regards to Connector.\n\nHelp us test!\n\nWe welcome any help. If you have tested or experienced issues with a mod and would like ...","hl_title":"Mod Compatibility Thread","id":"5499896","num_comments":910,"number":12,"repo":{"repository":{"id":645504703,"name":"Connector","owner_id":135172129,"owner_login":"Sinytra","updated_at":"2024-05-31T17:40:07.887Z","has_issues":true}},"title":"Mod Compatibility Thread","url":"/Sinytra/Connector/discussions/12","updated":"2024-06-01T20:43:16.000Z","user_avatar_url":"https://avatars.githubusercontent.com/u/51261569?s=48&v=4","user_id":51261569,"user_login":"Su5eD"}],"type":"discussions","page":1,"page_count":100,"elapsed_millis":357,"errors":[],"result_count":1818,"facets":[],"protected_org_logins":[],"topics":null,"query_id":"","logged_in":false,"sign_up_path":"/signup?source=code_search_results","sign_in_path":"/login?return_to=https%3A%2F%2Fgithub.com%2Fsearch%3Fq%3Dcomments%253A%253E100%26type%3DDiscussions","metadata":null},"title":"Discussion search results"}