v1.7.2 - Bitwatch - Privacy Update (#3776)
This commit is contained in:
parent
22d372cd12
commit
d0b0243709
@ -7,7 +7,7 @@ services:
|
||||
APP_PORT: 3117
|
||||
|
||||
web:
|
||||
image: ghcr.io/zapomatic/bitwatch:v1.7.1@sha256:360d6bbefcd78bda68c5520b7d5c7ed4bcc5145b165bbe1d7a1a05f960604c44
|
||||
image: ghcr.io/zapomatic/bitwatch:v1.7.2@sha256:bfc7522e0953c212010e189fdf6bd060168fb9ed283f59512600b0da0c98bd3b
|
||||
user: "1000:1000"
|
||||
restart: on-failure
|
||||
stop_grace_period: 1m
|
||||
|
||||
@ -2,7 +2,7 @@ manifestVersion: 1
|
||||
id: bitwatch
|
||||
category: bitcoin
|
||||
name: Bitwatch
|
||||
version: "1.7.1"
|
||||
version: "1.7.2"
|
||||
tagline: Monitor Bitcoin addresses in real-time
|
||||
description: >-
|
||||
Monitor Bitcoin addresses in the mempool and on-chain using the mempool.space API and websocket.
|
||||
@ -29,10 +29,9 @@ gallery:
|
||||
- 2.jpg
|
||||
- 3.jpg
|
||||
releaseNotes: >-
|
||||
Telegram healthcheck, Performance improvements, and remembers configs:
|
||||
- saves bitcoin/satoshi viewing preference to local storage
|
||||
- adds a healthcheck for telegram connection to prevent loss of telegram notifications
|
||||
- removes excess UI console logs that were causing UI performance issues
|
||||
This release addresses privacy concerns:
|
||||
|
||||
- when a local mempool instance is configured, address links open to that service url
|
||||
|
||||
website: https://github.com/zapomatic/bitwatch
|
||||
repo: https://github.com/zapomatic/bitwatch
|
||||
|
||||
Loading…
Reference in New Issue
Block a user