Searching We.Love.Privacy.Club

Twts matching #git
Sort by: Newest, Oldest, Most Relevant

[LFF] [1.2 XMR] Fundraiser for hosting the Monero archive for one more year

I have now been hosting the monero archive for more than a year now (started sometime in September 2023), I would like to keep on hosting it for one more year (at least). This fundraiser is for one more year of hosting. The price is the same at 0.1 XMR/month for hosting + maintenance.

Links:

⤋ Read More

How to ace the Certified Argo Project Associate (CAPA) exam
Community post originally published on Medium/IT Next by Giorgi Keratishvili Introduction Over the last five years, GitOps has emerged as one of the most interesting implementations of using GIT in the Kubernetes ecosystem and when people hear about… ⌘ Read more

⤋ Read More

I share I did write up an algorithm for it at some point I think it is lost in a git comment someplace. I’ll put together a pseudo/go code this week.

Super simple:

Making a reply:

  1. If yarn has one use that. (Maybe do collision check?)
  2. Make hash of twt raw no truncation.
  3. Check local cache for shortest without collision
    • in SQL: select len(subject) where head_full_hash like subject || '%'

Threading:

  1. Get full hash of head twt
  2. Search for twts
    • in SQL: head_full_hash like subject || '%' and created_on > head_timestamp

The assumption being replies will be for the most recent head. If replying to an older one it will use a longer hash.

⤋ Read More