HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
community
community
Ruby2020–2026
community / community

community

Public feedback discussions for: GitHub Mobile, GitHub Discussions, GitHub Codespaces, GitHub Sponsors, GitHub Issues and more!

65Distinct people
78Mentions
0Explicit recommenders
8.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Public feedback discussions for: GitHub Mobile, GitHub Discussions, GitHub Codespaces, GitHub Sponsors, GitHub Issues and more!

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year78 dated mentions

Observed mentions: 2020-12-07 18:40:22 UTC to 2026-01-26 17:15:12 UTC.

0102030402020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 22 mentions; 10 submissions, 12 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 40 mentions; 19 submissions, 21 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC110
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC221012
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC401921
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC11011
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

78 sources
Unfortunately, I think this is another indication of a lack of understanding by GitHub of how their OAuth/GitHub App systems are expected to function by end users. I'm reminded of this incident [1] from a few months ago. Allegedly, a malicious actor abused GitHub's poorly designed OAuth permissions to obtain up to 500 stars from developers without their consent, all thanks to a "sign in with GitHub" button and a flawed consent screen that did not communicate what the victims were consenting to. Even worse, GitHub allegedly decided to suspend at least one victim's account. We're left with a number of questions: 1. Why does GitHub give third-party apps permission to star repos when it is apparently against the terms of service to automate such an action? 2. Why does GitHub lump this permission in with public_repo, a scope that grants read a
Read the rest
nd write access to all public repositories? [2] 3. Why does the consent UI for this scope display simply as Repositories Public repositories and not even mention that this grants write access unless the user clicks on it? [3] (it also doesn't mention that it gives permission to star repos) 4. Why does GitHub punish victims with account suspension for being tricked into giving consent to malicious apps? It is good that GitHub is taking some steps to improve account security, such as fine-grained personal access tokens and mandatory 2FA. But these improvements do not seem to be extending to the OAuth system. The GitHub App system, while better in that it has granular permissions, is also flawed with its mysterious "act on your behalf" consent UI. [4] [5] [1]: https://news.ycombinator.com/item?id=33917962 [2]: https://docs.github.com/en/developers/apps/building-oauth-ap... [3]: https://news.ycombinator.com/item?id=33919481 [4]: https://github.com/community/community/discussions/37117 [5]: https://github.com/cirruslabs/cirrus-ci-docs/issues/751
In GitHub Copilot X – Sign up for technical preview
Yeah, Vundle's (presumably temporary) removal caught me off guard today on a fresh install. This, in turn, has caused me to take a hard look at the Vim plugins I was using. Turns out I only needed one...which I wrote. So I'm now just storing that one in the horrible "vanilla" Vim plugin scheme and putting that in my dotfile management. Just a good reminder that dependencies will always let you down. It's just a matter of time. Oh, and never turn your back on a big company. Here's the tracking on this issue: https://github.com/community/community/discussions/48173 GitHub: "The VundleVim organization has been flagged. Because of that, your organization is hidden from the public."
In VundleVim
The way it handled branches and merging was an absolute nightmare. IIRC it did this super weird thing that when you put up a diff from the CLI, it made its own little temporary branch for you. And god forbid if you pushed up your branch remotely, it would get all confused and start diffing against that remote branch. Literally couldn't merge via the UI, the CLI was the only way. To be fair, the review system was better than GitHub. It's insane that even today, there's no way to tag your team and have them stay tagged. If anybody comments or reviews, they're dismissed. This is an issue that's been open for nearly five years. [1] [1] https://github.com/community/community/discussions/5289
In Blender moves from Phabricator to Gitea

Showing the 15 most recent of 78 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.