Why you think that Bluetooth is more secure than USB-C? To me Bluetooth seems to be pretty vulnerable legacy.
I didn't, it is just a thought experiment
3% fee for handling a credit card is not as bad as 3% fee for handling cash
Change my mind
I wouldn't call Teams an example of efficient software either
What was hogging the performance btw?
I didn't meant that exactly, however I often encounter issues with applications that expect GMS to be present. When they are fed something non-standard (like sandboxed version or MicroG), such applications behave poorly.
I have configured 16 discover relays in total but I still observe this issue. Furthermore - when I open their profiles, gossip loads their metadata just fine, but not when viewing my followers list.
See this video: https://skhron.com.ua/dl/2024-12-22T21-41-01.mp4
Isn't it pointless to server google play version from zapstore? If you need google play version, you have google services and thus google play store itself.
There is no "forbidden" topics but individuals might not like some specific topic and mute you themselves
As long as your content is not CSAM, no one will ban you from using nostr unlike in X/Twitter
I mean, efficient resource usage is possible even with JS enabled but used really carefully, however having a JS-less website is something frequently demanded by Tor users for security reasons
It is not a bug, it is intended by a design, however I do agree that now it looks strange.
Just deployed our new website at https://skhron.eu/
Please check it out and share your feedback in comments - we will zap anyone with 21 sats for taking your time
Oops I forgot to mention that this website has 100% of functionality working even without JS enabled!
Not of much practical sense currently due to billing website relying on JavaScript, however having a no-JS friendly web user interface is on our roadmap.
Just deployed our new website at https://skhron.eu/
Please check it out and share your feedback in comments - we will zap anyone with 21 sats for taking your time
Gossip Release 0.13.0
=====================
Gossip is a nostr client for desktop.
Gossip is open sourced at https://github.com/mikedilger/gossip
This is a major release with the following changes:
* File Metadata support (NIP-92 / NIP-94)
* imeta data in incoming events is utilized, including testing the hash,
and displaying a placeholder blurhash (until the event loads)
* Attached files get imeta attachments when posting including url,
metadata (m), hash (x), size, dim, and blurhash
* Failed media loading now shows why
* Blossom support (BUD-01, BUD-02)
* Can attach local images and/or videos to your notes, which get uploaded
to your blossom server.
* Synchronizes with your nostr-saved blossom configuration, and you can
edit that
* NIP-89 Support - Recommended Application Handlers
* Gossip collects recommendations published by your contacts
* These become menu options for opening events
* You can disable any of them you don't want
* You can recommend these to your friends
* You can import a new handler (published by an application developer)
* Support is only for 'web' handlers
* Search on relays (NIP-50)
* You must choose your search relays first.
* Followers and Followed
* On the Person page, you can view who someone follows, and who follows
them (including for yourself)
* Computing who follows them is expensive and inaccurate
* Undo Send - for 10 seconds (or whatever you configure) you can undo sending
* Thread replies now sorted by date, except author replies come first
* Cancelling a draft asks if you are sure, so misclicks don't erase your
carefully crafted manifesto.
* Inbox indicator showing how many messages are waiting
* Feeds no longer inject new events and scroll while you are trying to read.
Instead, you will get a "Show New Updates" link to press when you are ready.
* Every feed has it's own separate "include replies" switch now
* Relays can now be tested to see whether they are fit for purpose
* Zap amount can now be typed in (or slid with a slider)
* Support for pubkey hints in 'e' and 'q' tags
* Support for 'E' and 'A' tags and kind 1111 Comments (NIP-22)
* Font update to support more unicode codepoints
* NIP-46 replies with NIP-44 encryption if the client used it.
* NIP-44 encryption now used for private contacts and private lists.
* FFMpeg 7.1 support
* Relay URLs now rendered as links to the relay config page
* build.sh script to help users choose features when compiling
* New command line commands: delete_by_kind, disable_relay
* Subscription batching for naddr searches
* Database compacting reduced to once per week, and handles out of space error
* Some theme color changes
* Relay scoring adjusted
* Likes and zaps data updated more frequently than before
* Default relays for new users have been tested and updated
* Many fixes
05048531f68164055516624327f8154d9bf3256b3ba52097de554b4c4fc9be99 changelog-0.13.0.txt
cfc8722786fdb59d208ebebb7a2dda8fd0e7373822731cdbae8b1ea6be206d07 filter.example.rhai
e56a0164a951f9269de6c24f9d00613faebf7d2edb140217909e62fdaea7cfbb gossip_0.13.0-1_amd64.deb
e08c29f02d38064121bb76abd2cdfb6357f869254997dd864e7b092423636b87 gossip-0.13.0-Darwin-arm64.dmg
3f9d3bd5e7e48cc83e437f53b9605a16b81c0df8b80d3124971c0290405add84 gossip-0.13.0-Darwin-x86_64.dmg
c6b1537aa0a94fc01f6972c3085fba92ce00d6bd78383b99a637f1ec0d67c933 gossip.0.13.0.flatpak
4baa638738860ab5b32d9a6ceaa516f381f6a411a2cabbe1614823f29ca4f719 gossip.0.13.0.msi
e3bc4161d4f659e1d3d5553fec216378109d06ba0c5da8e165dcda5bc1b917f1 gossip-0.13.0.x86_64.AppImage.tar.gz
25155c43f1b12dce73d4da04dff263995976cfc02a9251e415e2f1c7cdf0da5b LICENSE.txt
51d1df41814165378d1d7c305fcb6ca29f4a9fba02b84bc11b895eada8c40716 README.flatpak.txt
702bd583d106ed3d142f7cf92eb86a681fa93a7e46c3a1643773374694242bf2 README.macos.txt
32edc1a7ad1dccbabc174e4959358a779bf4cce2e938481c7574d1b99ece54aa README.txt
5e3da4edc740244d454a36f7d77f38d100ba68eafab4ce9c529eda3b40a59121 README.upgrading.txt
Sorry if this is not appropriate place to ask as I don't think it is justified enough to post in issues, however I would like to ask what I might be doing wrong - some of my followers show as "npub..." without profile picture and display name, despite I have setting "Network > Automatically Fetch Metadata" enabled.
nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c, do you have any idea what might go wrong?
GDPR is wild
What do you think exactly is better? Just curious.
How did lost bitcoin was measured?