lyse @lyse.isobeef.org

Follow

Block / Report User

If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!

You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.

@lyse does not follow you (they may not see your replies!)

Recent Twts

Recent twts from lyse

lyse @lyse.isobeef.org
 (8h ago)

I just fixed another bug in tt where the language hint in multiline markdown code blocks had not been stripped before rendering. It just looked like it was part of the actual code, which was ugly. I now throw it away. Actually, itā€™s already extracted into the data model for possible future syntax highlighting.

#f5crctq
lyse @lyse.isobeef.org
 (9h ago)

(#ys4znqq) @shinyoukai@neko.laidback.moe Because you might not want to commit all changed files in a single commit. I very often make use of this and create several commits. In fact, I like to git add --patch to interactively select which parts of a file go in the next commit. This happens most likely when refactoring during a feature implementation or bug fix. I couldnā€™t live without that anymore. :-)

If you have a much more organized way of working where this does not come up, you can just git commit --all to include all changed files in the next commit without git adding them first. But new files still have to be git added manually once.

#u5appra
lyse @lyse.isobeef.org
 (11h ago)

(#3hge2sq) Ok, the standard library implementation is wonky at best, at least in regards to XDG, because it really doesnā€™t implement it properly. https://github.com/golang/go/issues/62382 I stick to my own code then. It doesnā€™t properly support anything else than Linux or Unixes that use XDG, but personally, I donā€™t care about them anyway. And the cross-platform situation is a giant mess. Unsurprisingly.

#5dudhyq
lyse @lyse.isobeef.org
 (12h ago)

(#iudi6qq) Hmm, mine also resolves a leading tilde in these variables. And if $HOME is not specified it tries to resolve the userā€™s home directory by user.Current().HomeDir. Maybe thatā€™s overkill, I have to check the XDG spec.

But Iā€™m definitely missing os.UserDataDir(). Thatā€™s a bummer.

#3hge2sq
lyse @lyse.isobeef.org
 (13h ago)

(#f2cdpva) @movq@www.uninformativ.de Thanks! Iā€™ll have a look at SnipMate. Currently, Iā€™m (mis)using the abbreviation mechanism to expand a code snippet inplace, e.g.

autocmd FileType go inoreab <buffer> testfunc func Test(t *testing.T) {<CR>}<ESC>k0wwi

or this monstrosity:

autocmd FileType go inoreab <buffer> tabletest for _, tt := range []struct {<CR>    name string<CR><CR><BS>}{<CR>   {<CR>   name: "",<CR><BS>},<CR><BS>} {<CR>  t.Run(tt.name, func(t *testing.T) {<CR><CR>})<CR><BS>}<ESC>9ki<TAB>

But this of course has the disadvantage that I still have to remove the last space or tab to trigger the expansion by hand again. Itā€™s a bit annoying, but better than typing it out by hand.

#fjhkxza
lyse @lyse.isobeef.org
 (1d ago)

(#j5s5khq) @movq@www.uninformativ.de How about ā€œQuongsiā€? I generated the first five letters with pwgen --no-capitalize --no-numerals 5 and since that already showed up in DDG search results, I simply appended the last two, which yielded nothing on DDG and Google).

What kind of project is it? Maybe we can help you find a name or nudge you in the right direction.

#7tsxwnq
lyse @lyse.isobeef.org
 (1d ago)

The tt URLs View now automatically selects the first URL that I probably are going to open. In decreasing order, the URL types are:

  1. markdown media URLs (images, videos, etc.)
  2. markdown or plaintext URLs
  3. subjects
  4. mentions

I might differentiate between mentions of subscribed and unsubscribed feeds in the future. The odds of opening a new feed over an already existing one are higher.

#sd722yq
lyse @lyse.isobeef.org
 (1d ago)

(#pact6sq) @prologic@twtxt.net In my opinion, the integrity isnā€™t lost. The same input data always result in the same output hash, no matter when you calculate the hashes. Itā€™s true that a corrupt database contents yields to corrupt hashes, but then you have a whole bigger problem than just receiving different hashes. :-D

#uugltha
lyse @lyse.isobeef.org
 (1d ago)

(#73l4niq) @zvava@twtxt.net By hashing definition, if you edit your message, it simply becomes a new message. Itā€™s just not the same message anymore. At least from a technical point of view. As a human, personally I disagree, but thatā€™s what Iā€™m stuck with. Thereā€™s no reliable way to detect and ā€œcorrectā€ for that.

Storing the hash in your database doesnā€™t prevent you from switching to another hashing implementation later on. As of now, message creation timestamps earlier than some magical point in time use twt hash v1, messages on or after that magical timestamp use twt hash v2. So, a message either has a v1 or a v2 hash, but not both. At least one of them is never meaningful.

Once you ā€œupgradeā€ your database schema, you can check for stored messages from the future which should have been hashed using v2, but were actually v1-hashed and simply fix them.

If there will ever be another addressing scheme, you could reuse the existing hash column if it supersedes the v1/v2 hashes. Otherwise, a new column might be useful, or perhaps no column at all (looking at location-based addressing or how it was called). The old v1/v2 hashes are still needed for all past conversation trees.

In my opinion, always recalculating the hashes is a big waste of time and energy. But if it serves you well, then go for it.

#qatkviq
lyse @lyse.isobeef.org
 (1w ago)

(#o3hv4aq) @zvava@twtxt.net I might misunderstand what you wrote, but only hashing the message once and storing the hash together with the message in the database seems a way better approch to me. Itā€™s fixed and doesnā€™t change, so thereā€™s no need to recompute it during runtime over and over and over again. You just have it. And can easily look up other messages by hash.

#pmmlyta
lyse @lyse.isobeef.org
 (1w ago)

Oh great, I received an e-mail that my SMTP credentials have been exposed. Once again, just another shitty scanner that generates garbage reports from tests it doesnā€™t understand. Thank you for nothing!

conf := &Config{
    SMTPHost: "smtp.example.com",
    SMTPPort: 587,
    SMTPUser: "user",
    SMTPPass: "hunter2",
    SMTPFrom: "from@example.com",
}
#eljhddq
lyse @lyse.isobeef.org
 (1w ago)

(#c6rrdzq) @prologic@twtxt.net @movq@www.uninformativ.de A crocodile had bitten the big submarine internet cable that connects Australia to Europe. The investigations revealed that some construction work last week accidentally tore up the protective layer around it. That went unnoticed, unfortunately, so marine life had an easy job today. For just 40 minutes, they were quite fast in repairing the damage if you ask me! These communication cables are fricking large.

Just kidding, I completely made that up. :-D I didnā€™t notice any outage either. But I didnā€™t try to connect to Down Under at the time span in question.

#hsmdvqq
lyse @lyse.isobeef.org
 (1w ago)

(#2hgjg3q) @movq@www.uninformativ.de Very nice! I often wish other languages had something similar. Sometimes, I use lambdas, but that also looks ugly and feels a bit like a misuse. Other times, just the normal blocks are enough, but itā€™s not the same. Especially with the mutability aspects as the article explains. Typically, I just put it in a function or ignore it if itā€™s just a few lines.

#xqyb4ya