github
utterances
github | utterances | |
---|---|---|
30 | 75 | |
2,146 | 8,621 | |
- | 0.6% | |
3.0 | 0.0 | |
almost 3 years ago | 11 months ago | |
TypeScript | ||
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
github
-
How I Fixed GitHub's Repo Traffic Insights 🛠️ 📊
While looking for solutions, I realized that many developers face similar challenges. This issue is widely discussed, particularly in a GitHub thread: Track traffic to GitHub repo longer than 14 days #399.
-
Organizing Multiple Git Identities
Probably the older email address is still the primary one for the GitHub account.
GitHub took it upon themselves to change email addresses and author names when merging via the UI buttons like "Squash and Merge" in 2018 and then again in 2019. See <https://github.com/isaacs/github/issues/1368> for the tedious details.
Essentially the post-2019 behaviour seems to be that where possible with "Squash and Merge" they will set noreply@github as the committer so that they can sign the merged commit themselves, and set author name & email to what they have recorded for the GH account involved (and the signature is then a record that GH have verified that account's involvement).
Personally I think it is shocking that they ignore the name and email address that the actual author of the commit has selected. This is both a violation of the author's intentions -- for example, you may set work and personal email addresses in different repositories as discussed here, but GitHub will rewrite them all to the same thing when other people press "Squash and Merge" on your pull requests -- and potentially a doxxing security risk.
I have considered re-reporting this to GitHub via the newer community discussions or via support again, but given the extent to which they've ignored all such reports over the last five years it is hard to find the motivation to do so.
- GitHub prevents crawling of repository's Wiki pages – no Google search
-
How do Commercial Open Source Startups manage GitHub insights > 14 days? Is everyone using a workaround? How are "unique" cloners and viewers kept track off?
However, there is a massive issue. Github by default truncates insights to t-14 days (where t = today). This is super annoying as there is a discontinuity in data. There is also an archived issue on Github regarding this. The issue has a whopping 119 comments and has been around for over 8 years now. Basically, from the discussions there - Data you don't persist today will be gone 14 days from now. And looks like Github hasn't done anything about it.
-
Reimplementing the Coreutils in a modern language (Rust)
> Hi, people have made money using my code and I also don’t care
looks like everyone's missing the point.
> I understand this is upsetting to you
Again, maybe I am on another level of comprehension, so I don't understanda why it is so hard for someone to get it, but I am not upset by that, at all.
I simply know that those who think "it will be fine" are delusional and don't know what they are talking about!
So I just will paste some link to relevant news here, maybe it will make things clearer.
It includes the opinion of Antirez, father of one of the most successful OSS ever: Redis. Maybe his words will open your eyes and tear the veil of Maya.
(spoiler ahead alert!)
Basically you work for free and people don't even thank you and the maintainer ends up being doxed or blamed or pushed aside and in the long term the only solution to keep sanity is to resign
https://www.jeffgeerling.com/blog/2022/burden-open-source-ma...
https://www.theregister.com/2022/01/13/opensource_apacheplc4...
https://nolanlawson.com/2017/03/05/what-it-feels-like-to-be-...
https://old.reddit.com/r/linux/comments/z14tt2/reason_why_op...
https://github.com/isaacs/github/issues/167
http://web.archive.org/web/20221217180915/http://antirez.com...
-
Git archive checksums may change
I don't know what the fuss is all about. It was publicly known that Github was breaking automatic git archives consistency for many years. Here is a bug on a project to stop relying on fake github archives (as opposed to stable git-archive(1)):
https://bugzilla.tianocore.org/show_bug.cgi?id=3099
At some point it was impossible to go a few weeks (or even days) without a github archive change (depending on which part of the "CDN" you hit), I guess they must have stabilized it at some point. Here is an old issue before GitHub had a community issue tracker:
https://github.com/isaacs/github/issues/1483
-
Keeping a Project Bisectable
Hello, I see you stepped on my favourite personal soapbox! :)
https://github.com/isaacs/github/issues/1017
I really, really like semi-linear branching/merging. I.e. always rebase-merging, but with a merge commit.
Reasons, in comparison to Github's "rebase merge" which doesn't produce a merge commit:
1. It makes it clear which commits were part of one PR
2. It makes it clear who did the merge
3. It's okay to not have every commit build. but the one being merged will.
4. Still pretty bisectable. You'll narrow things down at least to the PR that caused an issue, and from there it's usually quite simple.
5. Looks very tidy in gitk & Co
-
Documenting My Work Again: hypothes.is
Not to say that the feature isn't coming to FOSS git services.. Just that even proprietary organizations have had issues with taking a while to implement them.
-
Keyless Git signing with Sigstore!
Oh this is cool actually! Nice! One of the grievances I have with github commit signing is this issue https://github.com/isaacs/github/issues/1099
-
Attempting to transfer a repository upon resigning from a company (warning I'm a noob)
In addition, you probably want to read this discussion. https://github.com/isaacs/github/issues/1138
utterances
-
Converting BlogCFC blog to Eleventy
Handling New Comments: There are excellent lightweight comment utilities available for managing comments on your eleventy blog. I personally use Utterances, but Giscus is also a great alternative.
-
Unleash Your Dev Blog: Write More with GitHub Issues as Your CMS
We can use utteranc.es, a lightweight comment widget built on GitHub Issues to integrate authed comments in our blog.
-
Must-Have Features to Look for in a Blogging Platform
utterances (open-source)
-
Blog Comments
Typically, a comment requires server side code and a lot of messy management. It’s a pain. These comments rely on a tool called utterances. Utterances uses GitHub’s issue tracker which was designed to track bugs, as part of that it includes extensive comment and discussion capabilities. If an issue doesn’t exist, utterances will automatically create that issue for you. It created this issue for the comments in this page...
-
How do I use utterances on a static GitHub pages site with no custom theme?
I've installed utterances on my GitHub repo. I've configured it and given it the appropriate permissions. At the end of setup, it provided me with an HTML script and the following instructions:
-
Add comments to blog website in minutes
Fortunatly we have free, lightweight and efficient options to add comments in blog website or any website. I am talking about utteranc.es. A lightweight comments widget built on GitHub issues. Use GitHub issues for blog comments, wiki pages and more!
-
🚀 Creating a Personalized Blog Website in minutes with Gatsby - A Step-by-Step Guide
Go to https://utteranc.es and follow the instructions to set up the commenting system.
- Free, non-self-hosted website comment system powered by GitHub Issues
-
Add reactivity to your Next.js blog using giscus
Giscus drew significant inspiration from utterances, which utilize an issue-based comment system instead of discussions. I experimented with utterances initially, but I found it less convenient due to its reliance on an issue tracker for conversational purposes.
-
Website engine or static content + dynamic functions implementations
If you're building a blog for developers, you can use a third-party commenting service that requires login with github, for example https://utteranc.es/
What are some alternatives?
Custom-Scenes - Please go to https://github.com/Notexe/h3-custom-scenes instead. Hitman 3 custom scene experimentation using ResourceTool + QuickEntity + simple-mod-framework + RPKG Tool
giscus - A comment system powered by GitHub Discussions. :octocat: :speech_balloon: :gem:
Signal-Server - Server supporting the Signal Private Messenger applications on Android, Desktop, and iOS
gitalk - Gitalk is a modern comment component based on Github Issue and Preact.
git2html - github clone of http://hssl.cs.jhu.edu/~neal/git2html/
staticman - đź’Ş User-generated content for Git-powered websites
Monocypher - An easy to use, easy to deploy crypto library
remark42 - comment engine
create-branch-from-issue - Creating branch from issue on Github, tampermonkey script
commento
mollyim-android - Enhanced and security-focused fork of Signal.
boring-avatars - Boring avatars is a tiny JavaScript React library that generates custom, SVG-based avatars from any username and color palette.