phoenix10.1
endoflife.date
phoenix10.1 | endoflife.date | |
---|---|---|
11 | 43 | |
113 | 2,192 | |
- | 2.8% | |
6.6 | 9.9 | |
12 months ago | 3 days ago | |
Python | Ruby | |
MIT License | 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.
phoenix10.1
- I built a personalized FM-style radio station generator with AI-powered RJ
-
Ask HN: Those making $0/month or less on side projects – Show and tell
I love this! I did something similar recently with Phoenix10.1 (https://github.com/pncnmnp/phoenix10.1).
-
Phoenix10.1, Synthesizes a personalized radio station
Hi a quick update: https://github.com/pncnmnp/phoenix10.1/issues I have created issues for all these stuff. I will be working on it tonight! Should be done by tomorrow morning. Cheers!
- Show HN: Phoenix10.1, a Personalized Radio Station
- Phoenix10.1, a Personalized Radio Station
- Generate a radio station with a personalized radio jockey
-
Phoenix10.1: Generates a personalized radio station with your own radio jockey
Let me make a couple of Github Issues based on the discussion we've had today. That way, we can organize our thoughts and plan accordingly.
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?
wttr.in - :partly_sunny: The right way to check the weather
WordOps - Install and manage a high performance WordPress stack with a few keystrokes
Simplest-File-Renamer - Simplest file renamer - rename your files quickly and easily
django-DefectDojo - DevSecOps, ASPM, Vulnerability Management. All on one platform.
git-bug - Distributed, offline-first bug tracker embedded in git, with bridges
xeol - A scanner for end-of-life (EOL) software and dependencies in container images, filesystems, and SBOMs
tql - A GraphQL query builder for TypeScript. Avoid the pain of codegen.
radiofeed-app - Simple podcast aggregator
Vrmac - Vrmac Graphics, a cross-platform graphics library for .NET. Supports 3D, 2D, and accelerated video playback. Works on Windows 10 and Raspberry Pi4.
public-iperf3-servers - A list of public iPerf3 servers...
codebase-visualizer-action - Visualize your codebase during CI.
digraph - Organize the world