HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
yltsrc
geocalc
Elixir2023–2023
yltsrc / geocalc

geocalc

Geographic calculations for Elixir

2Distinct people
2Mentions
0Explicit recommenders
156GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Geographic calculations for Elixir

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2023-03-06 08:12:55 UTC to 2023-03-06 13:20:45 UTC.

012023-03-06 08:00:00 UTC to 2023-03-06 09:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 6, 08:002023-03-06 09:00:00 UTC to 2023-03-06 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-06 10:00:00 UTC to 2023-03-06 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 6, 10:002023-03-06 11:00:00 UTC to 2023-03-06 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-06 12:00:00 UTC to 2023-03-06 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-03-06 13:00:00 UTC to 2023-03-06 14:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 6, 13:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 6, 08:002023-03-06 08:00:00 UTC2023-03-06 09:00:00 UTC101
Mar 6, 09:002023-03-06 09:00:00 UTC2023-03-06 10:00:00 UTC000
Mar 6, 10:002023-03-06 10:00:00 UTC2023-03-06 11:00:00 UTC000
Mar 6, 11:002023-03-06 11:00:00 UTC2023-03-06 12:00:00 UTC000
Mar 6, 12:002023-03-06 12:00:00 UTC2023-03-06 13:00:00 UTC000
Mar 6, 13:002023-03-06 13:00:00 UTC2023-03-06 14:00:00 UTC101

What Hacker News says

2 sources
(not sure where the "phoenix sockets" fit into it) 1/ So I guess you're saying one process/GenServer per device, communicating with it. 2/ Use a Registry[0] to store the process names (based on the device id or whatever) to abstract them from their PID. 3/ Have another GenServer (let's call it CoordStore) storing a map of "process_name -> lat/long" (with the related processes sending updates of the coordinates to it) 4/ Use Presence[1] to keep track of the devices and remove them from the CoordStore when needed. 5/ When you have an anomaly on one device ask CoordStore for the nearby devices/processes (using maybe [2]) and ask each one (thanks to the Registry) to run the check. 6/ Done? (sure you can do a barebone version without the Registry or Presence but where's the fun in that?) [0] https://hexdocs.pm/elixir/1.14.3/Registry.html [1]
Read the rest
In Phoenix 1.7.0

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.