2 ms·
My own approach is tending more toward a locally-hosted homepage. - Can be accessed from any local browser.[1] - Can be edited with any local text editor. -
by dredmorbius 2y ago
My own approach is tending more toward a locally-hosted homepage.
- Can be accessed from any local browser.[1]
- Can be edited with any local text editor.
- Can be liberally annotated.
- Can be readily searched (Ctrl-F, grep, etc.).
- Can be version controlled.
- Can be rsynced to other systems, or served over a local LAN, or privately-managed VPN, should that be necessary.
Within the homepage I can set up various categories, projects, date-oriented classifications (which can be annotations themselves), and of course a healthy and growing "misc" category.
________________________________
Notes:
1. This is occasionally not the case, as file:/// URIs are deprecated. In which case one can serve the file locally e.g., with Python (python3 -m http.server), netcat, etc.
- shepherdjerred 2y agoI do something like this, but I make it public. It’s just a file in a git repo. https://github.com/shepherdjerred/sjer.red/blob/main/src/links/links.ts https://github.com/shepherdjerred/sjer.red/blob/main/src/lin... https://sjer.red/links/ https://sjer.red/links/
- dredmorbius 2y agoI'd consider a public page, though the implications of that on today's Web have shifted considerably. That said, you'll still find old-school public homepages with lists of links on them, and they really are goldmines.