56!

and all future commits

Not entirely true. As long as you hold the copyright to all of the code (there are no contributions from other people), you can change the license however you like. The important thing is that this only affects commits after the licence is changed. All earlier versions are permanently available under the license they were released with.

https://crates.io/search?q=neofetch brings up 21 versions to choose from (21 are actual neofetch clones). There is also a library to help you write even more of them.

What I feel is missing from the practical suggestions section: why cache images at all? They should be stored on the server they were uploaded to, and nowhere else. The image URL would be attached to the post, and could then be used by clients to fetch the image from the original server.

I thought lemmy did this, but it seems not (any more?).

Is there anything missing from Best-Before? It may just be finished. There is no mention of anything obvious (such as a dependency on an API) that would cause it to stop working.

It seems it doesn’t propagate to other servers immediately though.

You’re not going to have much luck finding a search engine with good results that doesn’t depend on google or bing. Kagi is no different. Using a searx instance is probably best if you’re looking for something without official agreements with bing or google. Edit: Here is a list of independent search indexes I just discovered in another thread https://seirdy.one/posts/2021/03/10/search-engines-with-own-indexes/

The article is pure fluff. (even includes “synergy”). Most sentences don’t mean anything. Was this maybe just AI generated?

Regarding the topic: if people wanted this feature, it would already have been implemented. It’s not like the topic is obscure, or that it’s difficult to implement.

I’ve seen it in private browsing for a while now, but it has also just started happening in a normal window. My solution was to switch to ddg for now. Disabling js breaks image browsing for me.

I think the important part is that the syntax will become standardised, rather than being defined by microsoft/typescript, potentially allowing for alternative implementations. It could also make the build step optional in some cases, which is something people dislike about typescript currently.

I used waydroid for whatsapp, though any android emulator will probably work. To create the account, there was an option to verify a phone number by sending a text message (to a dumb phone with a burner sim card in my case). I use whatsapp web to read and send messages, and only have to open waydroid every few months to sign-in again.

It should be held back. Although I dislike the company, I believe safari’s market share and use of an alternative browser engine is important in keeping google from closing the web.

The term “master” is often used with the term “slave” in computing: https://en.wikipedia.org/wiki/Master-slave_(technology)
So it wouldn’t be odd to assume that git’s use of the term “master” also refers to slavery.

A comment on a post about a different instance suggested clearing browser cache/cookies. It’s not something I’ve run into though.

Hmm. I had it pop up for the first time in ages today, but updating filters and clearing cookies did the trick.

Unlike many comments here, I enjoyed reading the article, especially the parts in the “I don’t want to use gibibyte!” chapter, where you explain that this (the pedantry) is important in technical and formal situations (such as documentation). Seeing some of the comments here, I think it would have helped to focus on this aspect a bit more.

I also liked the extra part explaining the reasoning for using the Nokia E60.

I don’t quite agree with the recommendation to use base 10 SI units where neither KiB or kB would result in nice numbers. I don’t see why base 10 should have an influence on computers, and I think it makes more sense to stick to a single unit, such as KiB.

The reasons I have this opinion are probably to do with:

• My computer has shown me values using KiB, Gib, etc for years - I think it’s a KDE default - so I’m already used to the concept of KiB being different from kB.
• I dislike the concept of base 10 in general. I like the idea of using base 16 universally (because computers. Base 12 is also valid in a less computer-dominant society). I therefore also think 1024 is a silly number to use, and we should measure memory in multiples of 2^8 or 2^16…

p.s, I agree with other commenters that your comments starting with “Pretty obvious that you didn’t read the article.” or similar are probably not helping your case… I understand that some comments here have been quite frustrating though.

I think it’s just normal Lua code.

Here’s a quick json converter (based on https://stackoverflow.com/a/55575074), assuming you have lua installed:

local function to_json(obj)
    local result = {}
    for key, value in pairs(obj) do
        if type(value) == "string" then
            value = string.format("\"%s\"", value)
        elseif type(value) == "table" then
            value = to_json(value)
        end
        table.insert(result, string.format("\"%s\":%s", key, value))
    end
    return "{" .. table.concat(result, ",") .. "}"
end

function item(obj)
    print(to_json(obj))
end

dofile(arg[1])

It just defines the item function to print json, and executes the data file.

arg[1], the first command line argument, is the path to the data file:

$  lua to_json.lua path/to/datafile.list

and pipe the output to something.json or whatever else you want to do.

I think the second part of the comment is what’s important:

If you are in a more comfortable environment you will be better at working

Maybe that is windows for you. I have barely ever used windows, so the concept of searching for installers online and running them just seems clunky and time consuming to me. It’s just not what I’m used to.

However if you are willing to learn multiple systems, you might find that one is better than the others.