Searching We Love Privacy Club

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

Neat! 👌 I have been hacking on sshbox and refactored it a fair bit to have much more flexible auth methods. In addition I also toyed around w …
Neat! 👌 I have been hacking on sshbox and refactored it a fair bit to have much more flexible auth methods. In addition I also toyed around with the idea of having a shared (free) unix environment like some of the ones around ( whose name eludes me right now 🤦‍♂️), with a couple of key differences and differentiators:

  • The environment you get is actua … ⌘ Read more

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

Over the holiday break I was looking at one of my old projects, µLinux. Turns out I did a fine job realy and have decided to revive the projec …
Over the holiday break I was looking at one of my old projects, µLinux. Turns out I did a fine job realy and have decided to revive the project 🥳 – Just getting the build/tests woring on my Mac Studio ( Apple Silicon). Check it out! 👌 #µLinux ⌘ Read more

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

[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
prologic-twtxt-atom-feed
feeds.twtxt.net
 (1y ago)

**(#rjapt4a) I think it uses the first # url too. See here and here – @xuu@xuu Can you confirm this to be the case? 🙏 GetN("url", ...** I _think_ it uses the first# urltoo. See [here](https://git.mills.io/yarnsocial/go-lextwt/src/branch/main/ast.go#L1062-L1074) and [here](https://git.mills.io/yarnsocial/go-lextwt/src/branch/main/lextwt.go#L88-L95) – [@xuu _@txt.sour.is_](https://twtxt.net/external?uri=https://txt.sour.is/user/xuu/twtxt.txt&nick=xuu) Can you confirm this to be the case? 🙏GetN(“url”, 0)will return the fir ... ⌘ [Read more](https://twtxt.net/twt/5ieybsq)

⤋ Read More
cncf
feeds.twtxt.net
 (1y ago)

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
doesnm
doesnm.p.psf.lt
 (1y ago)
↳ In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

Web interface is deleted in https://git.mills.io/saltyim/saltyim/commit/376de2702319686c902ec03b8ca1e17b020fc639 but seems incorrectly (in source i see git lfs metadata). Can be builded if you grab https://git.mills.io/saltyim/saltyim/src/commit/15a64de82829/internal/web/app.wasm and place it in source (go directory has cached source) and rebuild

⤋ Read More
xuu
txt.sour.is
 (1y ago)
↳ In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

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
falsifian
www.falsifian.org
 (1y ago)

Diving into mblaze, I think I’ve nearly* reached peek email geek.

Just a bunch of shell commands I can pipe together to search, list, view and reply to email (after syncing it to a local Maildir).

EXAMPLES at https://git.vuxu.org/mblaze/tree/README

So far I’m using most of the tools directly from the command line, but I might take inspiration from https://sr.ht/~rakoo/omail/ to make my workflow a bit more efficient.

*To get any closer, I think I’d have to hand-craft my own SMTP client or something.

⤋ Read More
xuu
txt.sour.is
 (1y ago)
↳ In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

the stem matching is the same as how GIT does its branch hashes. i think you can stem it down to 2 or 3 sha bytes.

if a client sees someone in a yarn using a byte longer hash it can lengthen to match since it can assume that maybe the other client has a collision that it doesnt know about.

⤋ Read More
falsifian
www.falsifian.org
 (1y ago)
↳ In-reply-to » The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.

@prologic@twtxt.net Wikipedia claims sha1 is vulnerable to a “chosen-prefix attack”, which I gather means I can write any two twts I like, and then cause them to have the exact same sha1 hash by appending something. I guess a twt ending in random junk might look suspcious, but perhaps the junk could be worked into an image URL like

Image

. If that’s not possible now maybe it will be later.

git only uses sha1 because they’re stuck with it: migrating is very hard. There was an effort to move git to sha256 but I don’t know its status. I think there is progress being made with Game Of Trees, a git clone that uses the same on-disk format.

I can’t imagine any benefit to using sha1, except that maybe some very old software might support sha1 but not sha256.

⤋ Read More
abucci
anthony.buc.ci
 (1y ago)
↳ In-reply-to » There is a bug in yarnd that's been around for awhile and is still present in the current version I'm running that lets a person hit a constructed URL like

@prologic@twtxt.net This does not seem to fix the problem for me, or I’ve done something wrong. I did the following:

  1. Pull the latest version from git (I have commit 7ad848, same as on twtxt.net I believe).
  2. make build and make install
  3. Restart yarnd
  4. Refresh cache in Poderator Settings

Yet I still see these bogus /external things on my pod when I hit URLs like the one I sent you recently. When I hit such a URL with curl I think it’s giving an error? But in a web browser, the (buggy) response is the same as it was before I updated.

So, this problem is not fixed for me.

⤋ Read More
abucci
anthony.buc.ci
 (1y ago)
↳ In-reply-to » @mckinley He's signed up three times now even though I keep deleting the account, which is enough for me to permaban this person. I don't technically want open registrations on my pod but up till now I've been too lazy to figure out how to turn them off and actually do that, and there hasn't been a pressing need. I may have to now.

@lyse@lyse.isobeef.org Interesting. The yarnd --help currently says (for me):

  -R, --open-registrations            whether or not to have open user registgration

meaning it doesn’t give the default setting or warn you that you need to use -R=false and not -R false. It also leaves unclear whether --open-registrations false would work or if you need to do --open-registrations=false. It’s also unclear whether the setting change in the user interface is overridden by the command line arguments, overrides the command line arguments, is persisted across restarts.

Maybe all this is worth posting an issue for additional documentation on the git repo if there isn’t one already.

“registgration” is misspelled that way in the help by the way.

⤋ Read More