nostr:nprofile1qqsdph4ln7cjmmup7s7hc62znwmcfqf2c8jd94f6yqkmd2k8af95vmqpz9mhxue69uhkummnw3ezuamfdejj7qg4waehxw309ahx7um5wghx77r5wghxgetk9uq3zamnwvaz7tmwdaehgu3wd3skuep0yuaawk Well, after about half a day of using the Bengal JS, I gotta say, I think the fossil is just straight up superior. Having multiple buttons is great. Battery life is way better, obviously, on the fossil. The bangle is neat and I'm going to keep playing with it, but I'm probably going to run that fossil into the fucking dirt before I get rid of it and try and keep it alive for as long as possible.
That's the feeling I got when readinh reviews and accounts from other gadgetbridge users. Bangle is more freedom but rougher around the edges (literally and ironically since it has a square shape).
I know you couldn't get the api key again on the fossil but if you factory reset using the proprietary app and do it all over again. Hit me on simplex if you run into issues.
Couldn't do it this weekend, out on vacs with the fam
#Amethyst v0.88.4: New Reactions Panel
This is a small release to gather user feedback on the new reaction panel. Are the icons too big? Too small? Just right?
Download via [Obtainium](http://amethyst.social) or [Zap.Store](https://zap.store/)
Wen zapless polls?
When both nostr-mastodon bridges are working
*close family. I couldn't care less about 3rd degree cousins, don't even know their names
I honestly don't know. This happened by just rebooting...
My theory is that when you reboot, it kills all processes "nicely" with SIGTERM but if they don't stop after some time, it kills them forcefully with SIGKILL. I think Fulcrum can take a while to shutdown if it gets killed while writing to the DB, so when it gets SIGKILLed later, DB gets corrupted.
I have a secret: I always sync on my desktop and then copy it to my node. Not only is it much faster, I also always have a backup on my desktop up to the last time I did this, so I never have to do it from scratch.
Fulcrum DB got corrupted, AGAIN. fml 💀🤬🪦
Zaps, reactions, boosts and follows can all be faked and abused...
Just because something can be abused, does not mean that it will be.
Most polls will not be abused because they are not worth the effort to attack them. There is no value in coming up with a ultra secure polling system that no one will want to use because it's not frictionless.
We desperately need zapless polls.
🇬🇧 Vote on #ChatControl postponed – a triumph in our fight to defend the digital privacy of correspondence and secure encryption. 💪 Thank you!
But the next attempt will come. The critical governments need to get their act together now:
https://www.patrick-breyer.de/en/chat-control-vote-postponed-huge-success/
#ChatControl avoided! Now we can fully focus on what matters: #euro2024 🙃
#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
- Stops redirecting when resolving nip05 addresses by nostr:npub1e2yuky03caw4ke3zy68lg0fz3r4gkt94hx4fjmlelacyljgyk79svn3eef
- Fix hidden notes when hidden words is empty by nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5
- Fixes Url Preview crop when the image is too small or to big for the preview card.
- Better error messages when NIP-11 queries fail
- Fixes use navigateUp instead of popBackStack to avoid closing the app on double clicks on the back button
- Fixes the centered url on videos without active playback
- Fixes the padding of the reaction row on quotes
- Solves notification dots appearing on the navigation bar due to a hidden post
- Increases the download limit for reactions/zaps to events from 100 to 1000
- Fixes zap split rounding precision
- Fixes padding of the zap raiser
- Avoids showing error message if devs have removed their lnadress on the Zap the Devs card.
- Fixes padding and border of the zap split section on the master note
- Removes gray border in image urls that couldn't be loaded.
- Fixes alignment of reactions
- Fixes not centered Blank Notes
- Fixes scrollable drawer for all screen sizes
- Fixes search limits for profiles from 100 to 1000 events
- Re-normalizes all relays urls before connecting to reduce duplications
- Fixes the jittering from resizing Videos and Images during loading.
- Fixes landscape video centralization
- Forces relay URLs to be single line.
Updated translations:
- Czech, German, Swedish and Portuguese by nostr:npub1e2yuky03caw4ke3zy68lg0fz3r4gkt94hx4fjmlelacyljgyk79svn3eef
- Hindi by nostr:npub1ww6huwu3xye6r05n3qkjeq62wds5pq0jswhl7uc59lchc0n0ns4sdtw5e6
- Polish by nostr:npub16gjyljum0ksrrm28zzvejydgxwfm7xse98zwc4hlgq8epxeuggushqwyrm
- French by nostr:npub106efcyntxc5qwl3w8krrhyt626m59ya2nk9f40px5s968u5xdwhsjsr8fz
- Spanish by nostr:npub1luhyzgce7qtcs6r6v00ryjxza8av8u4dzh3avg0zks38tjktnmxspxq903
- Chinese by nostr:npub1raspu6ag9kfcw9jz0rz4z693qwmqe5sx6jdhhuvkwz5zy8rygztqnwfhd7
- Dutch by nostr:npub1w4la29u3zv09r6crx5u8yxax0ffxgekzdm2egzjkjckef7xc83fs0ftxcd
Code Quality Improvements:
- Removes old Robohash bitmap-based generation
- Upgrades Compose, Lifecycle and Fragments
Download via [Obtainium](http://amethyst.social) or [Zap.Store](https://zap.store/)
#amethyst latest release is just 13.9 MB. That's ridiculously small for the amount of features it packs. I still remember the days of >80 MB apks, it has come a long way.
They're already here:
nostr:naddr1qqrhxetww3e82mgzyrgda0ulkyk7lq05847xjs5mk7zgz2kpunfd2w3q9km243l2fdrxcqcyqqq80xgtev24u
You should only login using a nostr browser extension
TIL counting viewers of an HLS live stream is a hard fucking problem and there's no right answer. It's all based on heuristics and approximations.
This stems from the fact that viewers are just constantly making intermittent http calls for the .ts fragments of the stream. That's basically a huge mess to figure out who is connected since it's not long lasting.
There seems to be 3 main ways to count:
* Using an analytics proxy server 🤮🤮🤮
* Using the current number of established tcp inbound connections to port 443 from unique IPs
* Parsing the webserver (nginx) logs to make sense of it.
My question is, with so many good technical alternatives, why did the world settled on HLS as the standard for livestreams? It sucks.
nOsTr eLiTe
Their silo is broken wether they want it or not