hypothesize
endoflife.date
hypothesize | endoflife.date | |
---|---|---|
2 | 43 | |
3 | 2,192 | |
- | 2.8% | |
0.0 | 9.9 | |
over 6 years 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.
hypothesize
-
Ask HN: Those making $0/month or less on side projects – Show and tell
I haven't touched it in years, but during grad school I created a fully operational browser-based app for integrated note-taking and reference management for academic projects, based on locally stored markdown files, and designed to minimize attentional breaks: https://github.com/rkp8000/hypothesize .
I ended up using it for the remainder of my PhD; however, it was unfortunately a bit too easy to accidentally delete an entire note document, and I never got around to fixing it (although at least one other person ended up using it as the primary tool for their grad studies also :) ).
It definitely earned me no more than $0/month.
-
Ask HN: Show me your Half Baked project
https://github.com/rkp8000/hypothesize
In grad school I made a browser-based app in django to try to integrate note-taking and reference management as seamlessly as possible, having been fairly disappointed with existing software. Basically, it's kind of wiki-like, except links open in place by default so you don't lose your place jumping between pages.
I got it working well enough to use for the entirety of my PhD but don't really use it anymore just because it's still fairly clunky in certain ways.
I have zero time to continue working on it, but I do still kind of like the idea and would be thrilled if someone else picked it up!
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?
agstoolbox - 🧰Utility Adventure Game Studio software to help manage, install, and uninstall different AGS Editor versions.
WordOps - Install and manage a high performance WordPress stack with a few keystrokes
getstreamline - Streamline is a stream-of-consciousness writer for Obsidian
django-DefectDojo - DevSecOps, ASPM, Vulnerability Management. All on one platform.
notemapp-web - A notepad for maps - take notes on a world map and sync them across any device
xeol - A scanner for end-of-life (EOL) software and dependencies in container images, filesystems, and SBOMs
hist-prototype - A prototype of a history-keeping database
radiofeed-app - Simple podcast aggregator
Scrabble Solver by Kamil Mielnik - Free, open-source, and cross-platform analysis tool for Scrabble, Super Scrabble & Literaki. Quickly find top scoring words using given letters and board state. Available in English, French, German, Persian, Polish, Romanian & Spanish.
public-iperf3-servers - A list of public iPerf3 servers...
Nobody.live - View twitch streamers with zero viewers at nobody.live
digraph - Organize the world