#Amethyst v0.88.0: Performance Mode and Performance improvements

This version adds several performance improvements and includes a new UI mode in Settings that is designed for older phones. On that mode, all CPU-based animations are disabled, the use of transparency is minimized and the individually-generated robots are replaced by a static image. We also recommend disabling the Immersive Scrolling when using older phones.

Features:

- Adds performance mode on Settings

- Adds login with NIP-05 address

- Adds outbox relays to zap request: sender, receiver and author relays.

- Adds the NIP-65 relay to zap split tag instead of kind3 relays.

- Adds support for AVIF images

- Adds flare.pub videos to the media tab

- Replaces the post view count for a Share icon in the main feed.

Performance Improvements:

- Centralizes stringResource calls to cache them and avoid disk use

- Removes several unecessary UI states created during rendering

- Moves uncited hashtag parsing to a thread

- Replaces InputButton for ClickableBox to avoid loading colors during rendering

- Switches Social Icons mip-mapped PNGs to faster SVG versions

- Faster calculation of uncited hashtags in content

- Improves the speed of Robohash rendering

- Moves chatroom user group away from immutable sets

- Speeds up long-press Quick Action menus

- Optimizes NIP-11 fetch and avoids requesting twice in the same minute

- Redesigns the UI Components of the relay icons better performance

- Creates a relay flow cache to speed up the relay layout

- Combines hidden and reporting flows in a new cache

- Removes post reports Live data

- Refactors Full Bleed design of the master note

- Unifies Hidden and Report checks between the Video Feed, the Full Bleed Design and the Card layout.

- Adds a hashcode cache to speed up O(1) requests of spam and blocked user public keys

- Minimizes memory alloc by adding a native forEach and Map functions in the event's tag array

- Reduces double launch of co-routines

- Improves memory use of updates to the subscription after EOSE events

- Simplifies intrinsic size calculations for Image Previews and Videos

- Improves rendering time of chat messages

BugFixes:

- Fixes the inconsistency of button animation size in the reaction row

- Fixes the inconsistency of the Zap button graphics

- Fixes the Giftwraps query by EOSE date mismatch

- Fixes the keyboard's Go Button action on new user screen

Michael Saylor to Pay a District Record $40M Settlement in D.C. Income Tax Case

"Florida remains my home today, and I continue to dispute the allegation that I was ever a resident of the District of Columbia. I have agreed to settle this matter to avoid the continued burdens of the litigation on friends, family, and myself," Saylor told The New York Times.

a Relay Test Suite is in the works...

I've already got ideas for 94 tests and as I write these tests they expand out into even more tests.

I hoping that exposing relay behavior will drive relay software towards consistently supporting the same way of doing certain things, and that this will help nostr compatibility.

Tests include things like:

* Can the public write events?

* Can an authenticated person write somebody else's events?

* Does the relay respond to minimally constrained filters?

* Does limit 0 give an EOSE?

* When you write an event and get OK-true, can you read it directly back?

* Does limit behave properly when a filter has multiple pubkeys and multiple kinds?

* Does it require AUTH to read DMs and giftwraps?

* When submitting a replaceable event, are the prior events replaced?

* When submitting a replaceable event with newer ones already present, is it rejected or ignored?

* Does deletion of a replaceable event preserve the events that are newer than the deletion event?

* Does it prompt for auth initially?

* How large of an event can it handle?

* Does it verify signatures?

* How does it react to invalid UTF8?

* Does it handle all JSON escape codes? What about surrogate pairs?

* Does it preserve field order in events?

* Does it preserve fields in events not defined by the nostr spec?

* How many subscriptions does it allow simultaneously?

* Do events with negative created_at values work? What about exponential notation? What about numbers that won't fit in a u64?

... that kind of thing.

Announcing: Harbor, an ecash desktop wallet for better bitcoin privacy.