Searching We.Love.Privacy.Club

Twts matching #cache
Sort by: Newest, Oldest, Most Relevant
monero-observer
feeds.twtxt.net
 (1y ago)

Haveno adds support for USDT
woodser1 has released Haveno2 version 1.0.133 with support for Tether (USDT)4, various improvements, updates, and bug fixes.

Changes overview

”`
Support USDT (ERC20 & TRC20)
Refactor tabs for simplicity
Update Tails script to retry download using wget
Improve backup recovery if wallet cache is corrupt
Fix sorting Buy or Sell XMR > Amount column
Update price nodes to support USDT
Other stability improvements and bug fixes [..]

... ⌘ [Read more](https://monero.observer/haveno-v1.0.13-released-support-tether-usdt/)“

⤋ Read More
sorenpeter
darch.dk
 (1y ago)

@eapl.me@eapl.me here are my replies (somewhat similar to Lyse’s and James’)

  1. Metadata in twts: Key=value is too complicated for non-hackers and hard to write by hand. So if there is a need then we should just use #NSFS or the alt-text file in markdown image syntax ![NSFW](url.to/image.jpg) if something is NSFW

  2. IDs besides datetime. When you edit a twt then you should preserve the datetime if location-based addressing should have any advantages over content-based addressing. If you change the timestamp the its a new post. Just like any other blog cms.

  3. Caching, Yes all good ideas, but that is more a task for the clients not the serving of the twtxt.txt files.

  4. Discovery: User-agent for discovery can become better. I’m working on a wrapper script in PHP, so you don’t need to go to Apaches log-files to see who fetches your feed. But for other Gemini and gopher you need to relay on something else. That could be using my webmentions for twtxt suggestion, or simply defining an email metadata field for letting a person know you follow their feed. Interesting read about why WebMetions might be a bad idea. Twtxt being much simple that a full featured IndieWeb sites, then a lot of the concerns does not apply here. But that’s the issue with any open inbox. This is hard to solve without some form of (centralized or community) spam moderation.

  5. Support more protocols besides http/s. Yes why not, if we can make clients that merge or diffident between the same feed server by multiples URLs

  6. Languages: If the need is big then make a separate feed. I don’t mind seeing stuff in other langues as it is low. You got translating tool if you need to know whats going on. And again when there is a need for easier switching between posting to several feeds, then it’s about building clients with a UI that makes it easy. No something that should takes up space in the format/protocol.

  7. Emojis: I’m not sure what this is about. Do you want to use emojis as avatar in CLI clients or it just about rendering emojis?

⤋ Read More
monero-observer
feeds.twtxt.net
 (1y ago)

Monero Dev Activity Report - Week 41 2024: 23 PRs, 8 Issues
This weekly report aims to provide a big picture view of Monero development activity, increase community support for existing devs and, hopefully, encourage new contributions.

1 - PRs (23, 17:5:1)

Opened (17)

monero-project/monero:

  • #95071 tests: include where using std::setfill (jeffro256)
  • #95062 wallet2: fix error throw if unable to load cache RELEASE
  • #95053 crypto: remove unus … ⌘ Read more

⤋ Read More