Searching We Love Privacy Club

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

**(#7yfkzjq) * Page size 1MB

  • Median 50 pages per query

  • 80% pages cached

  • 200us SSD reads

  • 100us Memory reads

  • Query time:

    • (50x0.80x10 …**

  • Page size 1MB

  • Median 50 pages per query

  • 80% pages cached

  • 200us SSD reads

  • 100us Memory reads

  • Query time:

    • (50x0.80x100)+(50x0.20x200)‎ = 6,000

    • 6000us

    • 6ms ⌘ Read more

⤋ Read More
prologic-twtxt-atom-feed
feeds.twtxt.net
 (1y ago)

**Problem 2: Your SSD-backed database has a usage-pattern that rewards you with a 80% page-cache hit-rate (i.e. 80% of disk reads are served d …**
Problem 2: Your SSD-backed database has a usage-pattern that rewards you with a 80% page-cache hit-rate (i.e. 80% of disk reads are served directly out of memory instead of going to the SSD). The median is 50 distinct disk pages for a query to gather its query results (e.g. InnoDB pages in MySQL). What is the expected average query time from your database?

Share your solution via Twtxt … ⌘ Read more

⤋ Read More
prologic-twtxt-atom-feed
feeds.twtxt.net
 (2y ago)

One of the things I’m going to work on next (maybe today, we’ll see how much time there’s left in the day) is being able to load up old conver …
One of the things I’m going to work on next ( maybe today, we’ll see how much time there’s left in the day) is being able to load up old conversations ( fallen off the cache) like this one. ⌘ Read more

⤋ Read More
prologic-twtxt-atom-feed
feeds.twtxt.net
 (2y ago)

After several hard hours, I think I’ve recovered the last missing 1 Twt from @bender@bender 🥳 Turns out just before I accidentally nuk …
After several hard hours, I think I’ve recovered the last missing 1 Twt from @bender 🥳 Turns out just before I accidentally nuked my pod, I took a dump of it’s cached just seconds before 🤣 – So I was also able to rebuild anything that was missing from the backup from the recent cache dump! ⌘ Read more

⤋ Read More
monero-observer
feeds.twtxt.net
 (2y 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
 (2y ago)
↳ In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

@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