October 23, 2023 at 3:43:45 PM UTC — Nexodus Archive

Nexodus Archive

A versioned archive of posts from Bluesky, Mastodon, GitHub, npm, YouTube, Letterboxd, Hacker News, and blogs. Browse the most popular posts.

Last built Nov 7, 2026, 1:18 PM UTC.

	Since	posts	replies	likes	reposts and quotes	views
Bluesky	May 2023	1,039	8,236	23,127	2,380
Mastodon	Nov 2022	2,399	29,156	55,396	16,820
GitHub	Jul 2010	179	5,777 3,520	33,866	3,317
npm	Jul 2014	139	1,546			75,991,720
YouTube	Dec 2015	30		1,203		32,713
Letterboxd	Mar 2026	55
Blog	Nov 2025	20
Hacker News	Jan 2011	59	575	802
All	Jul 2010	4,807	37,967	114,394	22,517	76,024,433

8 2010
4 2011
3 2012
6 2013
9 2014
55 2015
78 2016
110 2017
101 2018
66 2019
134 2020
201 2021
327 2022
998 2023
879 2024
1,035 2025
793 2026

4,807 posts by year

The reign of web components continues with a <ppp-price> to show Parity Purchasing Power prices as a demo of @cloudcannon’s Geolocation feature:

https://www.zachleat.com/web/ppp-price/

2 replies

Joe Workman 1 day later

@zachleat how would you implement the payment processing for a system like that? I love this idea and have wanted to do this in the past.
1. Zach Leatherman 1 day later
  
  @joe If you wanted to implement similar logic on the backend, you could use the `ppp-data.json` file for country code ratios: https://github.com/zachleat/parity-purchasing-power-price/blob/49c27c59039839a295b63ae8834c101c4615025b/ppp-data.json
  and the logic for price conversion here: https://github.com/zachleat/parity-purchasing-power-price/blob/49c27c59039839a295b63ae8834c101c4615025b/ppp.js#L76