where_is_waldo 0.1.12 → 0.1.13
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +24 -0
- data/README.md +31 -0
- data/VERSION +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: d06a950b27e51d7506062dc38518912b7b631a91be886eb29801f01e0ac438ac
|
|
4
|
+
data.tar.gz: fb1f82a4742a5099eee4d7a70f9d5445010dc52bd17408cfe2451363c04051a2
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 5bfd8270b07bed9227be801b90b1f354a30a1eeaf748a3b7b7ff0d1a551bb0f3d6685792862f7c8e5676d411ea263b14fe64c67a76be422b0e55055a01672900
|
|
7
|
+
data.tar.gz: '053823564618b09793ded991cf679d9017eb3be14c8069bf1d33ee0fbe50d8872b0e004a7d0ab8ac0969a08e3eb4c7b427c562800e2c002fa9ec8c1cc9bd3e22'
|
data/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,30 @@ Notable changes to where_is_waldo. Format loosely follows
|
|
|
5
5
|
|
|
6
6
|
## Unreleased
|
|
7
7
|
|
|
8
|
+
## 0.1.13 - 2026-11-04
|
|
9
|
+
|
|
10
|
+
### Documentation
|
|
11
|
+
|
|
12
|
+
No code changes. This release exists to get the README onto the npm page, which
|
|
13
|
+
only refreshes its rendered README on a new version.
|
|
14
|
+
|
|
15
|
+
- **The README now says where this came from.** It previously mentioned
|
|
16
|
+
byscott.io zero times in 543 lines, so the one public, indexed page the
|
|
17
|
+
project owns pointed back at nothing. Adds a line under the tagline and an
|
|
18
|
+
About section naming the suite and three sibling tools.
|
|
19
|
+
- **States plainly what the gem requires, and what it does not.** No account, no
|
|
20
|
+
API key, and no outbound calls of any kind — verified against the shipped
|
|
21
|
+
code, which contains no HTTP client and no hostnames. The sibling tools linked
|
|
22
|
+
in that section are hosted services and do require accounts; this does not,
|
|
23
|
+
and the distinction is now explicit rather than left to the reader.
|
|
24
|
+
- **States that presence data is transient and lives in the consumer's own
|
|
25
|
+
store.** One table, or Redis keys with a TTL; a session's row is removed once
|
|
26
|
+
it stops heartbeating. This answers the question a developer actually asks of
|
|
27
|
+
a presence library — whether it quietly accumulates rows they then have to
|
|
28
|
+
manage.
|
|
29
|
+
- `homepage` now points at byscott.io. `repository` and `bugs` still point at
|
|
30
|
+
this public repo, so source and issues stay one click away from the npm page.
|
|
31
|
+
|
|
8
32
|
## 0.1.12 - 2026-10-27
|
|
9
33
|
|
|
10
34
|
### Fixed
|
data/README.md
CHANGED
|
@@ -2,6 +2,9 @@
|
|
|
2
2
|
|
|
3
3
|
Real-time presence tracking for Rails + React using ActionCable.
|
|
4
4
|
|
|
5
|
+
Open source, and built for and used in production by the [byscott.io](https://byscott.io)
|
|
6
|
+
suite of tools for churches, educators, small businesses and families.
|
|
7
|
+
|
|
5
8
|
[](https://github.com/byscott-io/where_is_waldo/actions/workflows/ci.yml)
|
|
6
9
|
[](https://rubygems.org/gems/where_is_waldo)
|
|
7
10
|
[](https://www.npmjs.com/package/@byscott-io/where-is-waldo)
|
|
@@ -538,6 +541,34 @@ gem guarantees, and what your app must do:
|
|
|
538
541
|
are gated to transitions. For large or hostile deployments use the Redis
|
|
539
542
|
adapter and consider rate-limiting.
|
|
540
543
|
|
|
544
|
+
## About
|
|
545
|
+
|
|
546
|
+
WhereIsWaldo is maintained by Scott Gibson and came out of a real need across
|
|
547
|
+
[byscott.io](https://byscott.io) — a suite of software tools for churches,
|
|
548
|
+
educators, small businesses and families, where several Rails and React apps
|
|
549
|
+
each wanted "who is online right now" without paying for a hosted websocket
|
|
550
|
+
service.
|
|
551
|
+
|
|
552
|
+
**No account or API key is required, and nothing phones home.** This gem keeps
|
|
553
|
+
no store of its own. Presence lives in one table in your own database, or as
|
|
554
|
+
expiring keys in your own Redis, and it is transient either way — a session's
|
|
555
|
+
row is removed once it stops heartbeating, and Redis keys carry a TTL. The only
|
|
556
|
+
infrastructure it needs is the ActionCable you already run.
|
|
557
|
+
|
|
558
|
+
The sibling tools below are hosted services and do require an account; this gem
|
|
559
|
+
is a library and does not.
|
|
560
|
+
|
|
561
|
+
Other tools from the same suite, if a shared backend is what you actually want
|
|
562
|
+
rather than a library:
|
|
563
|
+
|
|
564
|
+
- **[IssuesByScott](https://issues.byscott.io)** — error reporting, an issue
|
|
565
|
+
portal your users can file into, and deploy tracking
|
|
566
|
+
- **[BillingByScott](https://billing.byscott.io)** — subscriptions, invoicing
|
|
567
|
+
and entitlement checks across several apps
|
|
568
|
+
- **[MetricsByScott](https://metrics.byscott.io)** — events, page views and
|
|
569
|
+
time-varied metrics, with a data warehouse rather than a dashboard you cannot
|
|
570
|
+
query
|
|
571
|
+
|
|
541
572
|
## License
|
|
542
573
|
|
|
543
574
|
MIT
|
data/VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
0.1.
|
|
1
|
+
0.1.13
|