Tachi
endoflife.date
Our great sponsors
Tachi | endoflife.date | |
---|---|---|
2 | 43 | |
91 | 2,180 | |
- | 4.5% | |
9.7 | 9.9 | |
7 days ago | 5 days ago | |
TypeScript | Ruby | |
- | 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.
Tachi
-
Ask HN: Those making $0/month or less on side projects – Show and tell
I've spent the past two years or so working on Tachi (https://bokutachi.xyz/) (https://github.com/TNG-Dev/Tachi), which is a modular tool for tracking rhythm game scores.
Generally, everyone was using their own personal spreadsheets or ancient "just render everything" tables to analyse their scores and progress before this and I'm pretty happy with how it's turned out.
What I'm probably most proud of is that adding support for a new game is adding a new module for it - all of the other features automatically work with it. This turns a "each game needs to have its own full-site tracker" into a "each game needs a configuration for this one tracker", not unlike how LSP simplifies adding language support for editors!
Taught me almost everything I know about scaling a codebase, and despite being a niche tool it's picked up a lot of momentum (2k users, ~3m scores).
- Ask HN: Who wants to be hired? (January 2023)
endoflife.date
-
End of Life of Technologies and Devices
> where you can see overlapped timelines when support ended
I tried to generate a visual timeline for a given page (https://github.com/endoflife-date/endoflife.date/pull/2859, has some screenshots), but it was limited to a single page (so you'd only see nokia devices at once for eg).
It turned out that it is too hard to generate clear charts with vague data. We often only know whether is device is supported or not (true/false, see comments about samsung below in this thread), and don't have clear release dates.
I'll get to it someday (PRs welcome), but it might not work for the usecase we want (picking phones) because data on mobiles is very vague.
repairability score -> sounds interesting, will file an issue and see. The hard part is that there's no clear identifiers for devices (SWID/CPE are just not good enough) for us to track this kind of data from elsewhere easily.
-
understanding Rails version maintenance policy?
Here's the PR where it was added by a user, "Based on a Rails core team member's comment"...
-
Pragmatic Versioning – An Alternative to Semver
A lot of the communications regarding End of Life for Support is done very effectively here: https://endoflife.date/
-
Maybe helpful: https://endoflife.date
https://endoflife.date (not mine)
-
Central Hardware Firmware versions?
a little similar to endoflife.date if anyone has ever come across it for Software versions?
-
You can serve static data over HTTP
We do this at https://endoflife.date API, and it works quite well.
-
python-eol: A package to check whether the python version you're using is beyond/close to end of life
I've created the `db.json` with the [end of life](https://endoflife.date/) api.
-
Ask HN: Most interesting tech you built for just yourself?
Something I've recently worked on is building an SQLite database of all the dependencies my organisation uses, which makes it possible to write our own queries and reports. The tool is all Open Source (https://dmd.tanna.dev) and has a CLI as well as the SQLite data.
Ive used it to look for software that's out of date (via https://endoflife.date), to find vulnerablilities (via https://osv.dev) and get license information (via https://deps.dev)
It's been hugely useful for us understanding use of internal and external dependencies, and I wish I'd built it earlier in my career so I could've had it for other companies I've worked at!
-
Keeping up with EOS and EOL hardware and software
This is neat: https://endoflife.date/
-
Looking for a 3rd party library of EOL/EOS software support dates
I'm looking for a 3rd party vendor that can do the mindlessly tedious work of maintaining a library of software support dates. Think hundreds of thousands/millions of versions of software in an enterprise with ridiculous tech debt. Something like endoflife.date but much more far encompassing.
What are some alternatives?
longshot - API and CLI for ECAM-based Delonghi machines
WordOps - Install and manage a high performance WordPress stack with a few keystrokes
cv
django-DefectDojo - DevSecOps, ASPM, Vulnerability Management. All on one platform.
resume
xeol - A scanner for end-of-life (EOL) software and dependencies in container images, filesystems, and SBOMs
resume
radiofeed-app - Simple podcast aggregator
beaker - An experimental peer-to-peer Web browser
public-iperf3-servers - A list of public iPerf3 servers...
ArchiSteamFarm - C# application with primary purpose of farming Steam cards from multiple accounts simultaneously.
digraph - Organize the world