you brought up top month and I don’t see how you’d want that to work

The truth is I don’t want “top month”. What I really want is “best result, filtered by this month”. But unfortunately that doesn’t exist, and in the absence of that, I use “top month”.

This doesn’t have anything to do with sort ordering though, which is based on time and votes. Text search is just a filter on top of sorting.

That doesn’t feel like how search should work. It should be ranking results that fit the search query better higher than ones that fit it less. Regardless of how the search is done, that should remain true. So if you’re using trigram matching, instead of a binary “does the comment contain 80% of the trigrams in the search query”, it should be “if it contains 100% of the trigrams from the search query, rank it higher than something with 90% match, which is higher than 80%.” Or maybe not that precisely, but something so that more relevant results appear above less relevant ones.

Without doing something like that, it’s just…not very useful. Which is the observed behaviour of search on Lemmy right now which started this whole conversation.

Eh, I don’t think it’s that surprising. Getting a list of comments on a post vs getting them from a search term are very similar operations, so it doesn’t make too much sense for these to have different queries in the backend

Sure, but one would have thought that the ordering in a search is fundamentally different from the ordering in other places. Because you want something that contains the words you’ve searched for near each other to appear ahead of a post that has those words scattered at random because it’s a 500 word essay. You want exact word matches prioritised ahead of entirely unrelated words that include the same characters. Like “enum” should turn up your comment, but rank a comment that contains the text “renumbers” much more lowly. A particularly smart search page might keep “enumerate” high while rejecting “renumbers”, though.

Of course, it’s true that at least in the current latest release, Lemmy fails at all of this. I hope 1.0 is at least fixing some of it?

At least the search function is still better than Reddit’s

I actually don’t agree. This is one area where Reddit’s centralised nature is a benefit, because it makes it super easy for Google to index and return results. On-site search isn’t great on Reddit, but at least Googling for stuff from Reddit works really well.

https://join-lemmy.org/docs/users/03-votes-and-ranking.html#sorting-comments

That’s a page that really shouldn’t be relevant, and it concerns me if it is, because the search page should not be working on the same ordering logic that comment pages or the front page use.

Anyway, I mainly only use the “top month” option as a proxy for what I really want, which is “filter by posts/comments in the last month”, usually because I’m searching for something I saw recently, and I have a rough idea of when it was posted.

Searching by “posts” on Lemmy is actually superior to searching on PieFed, though searching by “all” or “comments” on Lemmy is absolutely borken

Ah, that makes sense. I’ll try to pay attention to which I’m doing, because my most recent search used only comments, but was absolutely useless.

Here’s a search I did just now. Despite trying to restrict it to the last month (“Top Month”), none of the results on the first page are within the last month.

Here’s a search I did just now. Despite trying to restrict it to the last month (“Top Month”), none of the results on the first page are within the last month.

The human lineage diverged from that of chimps and bonobos before chimps and bonobos diverged from each other.

Out of interest, what is search like on Piefed? Lemmy’s is all but useless. Even filtering by “last week” will show me two year-old posts and comments, regularly that don’t actually include the word I’m looking for.

Discussions are, arguably, their own type of OC. Like this thread as one example. That’s the kind of thing I, and I suspect @fujiwood@lemmy.world, would love to see more of.

In Queensland, Australia, we passed a Voluntary Assisted Dying law a few years ago. But it’s worth noting that it probably would not apply to OP’s condition. One of the eligibility criteria is “expected to cause death within 12 months”, and another is “Have decision-making capacity” which means that long-term progressive diseases which take away mental faculties long before they cause death, as Alzheimer’s does, are unfortunately not eligible.

There’s a ~/.docker/config.json. In that there’re some auths, with keys https://index.docker.io/v1/, https://index.docker.io/v1/access-token, and https://index.docker.io/v1/refresh-token, and then there’s "currentContext": "rootless".

There’s ~/.docker/contexts/meta/[a long hex string]/meta.json, with {"Name":"rootless","Metadata":{"Description":"Rootless mode"},"Endpoints":{"docker":{"Host":"unix:///run/user/1000/docker.sock","SkipTLSVerify":false}}}.

The only file in /etc/docker is key.json.

I never set one up myself, and this 11 year-old thread implies that Raspbian doesn’t have one set up by default. It is a very old thread though, so could be wrong.

edit: this is more recent and also says Raspbian doesn’t have DNS caching by default

$ dig registry-1.docker.io

; <<>> DiG 9.18.33-1~deb12u2-Debian <<>> registry-1.docker.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50801
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;registry-1.docker.io.          IN      A

;; ANSWER SECTION:
registry-1.docker.io.   33      IN      A       54.210.249.78
registry-1.docker.io.   33      IN      A       44.218.153.24
registry-1.docker.io.   33      IN      A       107.20.112.188
registry-1.docker.io.   33      IN      A       34.234.222.10
registry-1.docker.io.   33      IN      A       34.195.83.243
registry-1.docker.io.   33      IN      A       52.21.128.203
registry-1.docker.io.   33      IN      A       52.0.248.137
registry-1.docker.io.   33      IN      A       52.207.69.161

;; Query time: 47 msec
;; SERVER: 192.168.20.1#53(192.168.20.1) (UDP)
;; WHEN: Tue Aug 12 22:27:45 AEST 2025
;; MSG SIZE  rcvd: 177
$ cat /etc/resolv.conf
# Generated by NetworkManager
search Home
nameserver 192.168.20.1

edit: oh, and in my router’s configuration:

• Primary DNS Server:9.9.9.9
• Secondary DNS Server:1.1.1.1

I’m happy to keep it public if only for the off chance that if we find a solution it might some day help someone else with the same issue. The thread’ll fall down in the rankings naturally over time anyway so I wouldn’t worry about polluting anything for people not actively seeking it out.

I’m not 100% sure how to find the OS version, but uname -a outputs [...]6.12.25+rpt-rpi-v8[...]. /etc/os-release contains “Debian GNU/Linux 12 (bookworm)”. It should be whatever was latest as of a month or two ago when I installed the OS fresh.

DHCP server as in on my router?

Still get exactly the same error.

52.207.69.161
52.21.128.203
3.224.238.37
44.218.153.24
54.210.249.78
18.232.25.125
52.72.195.97
54.161.169.181

Do you have no ipv6 address now in ip addr

Just comparing it by eye, there’s no change.

zag@raspberrypi:~ $ man dig
No manual entry for dig
zag@raspberrypi:~ $ which dig
zag@raspberrypi:~ $ sudo apt install dig
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package dig

But if I ping it

$ ping registry-1.docker.io
PING registry-1.docker.io (107.20.112.188) 56(84) bytes of data.

Unfortunately not.

 docker run hello-world
Unable to find image 'hello-world:latest' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/library/hello-world/manifests/sha256:ec153840d1e635ac434fab5e377081f17e0e15afab27beb3f726c3265039cfff": dial tcp [2600:1f18:2148:bc00:eff:d3ae:b836:fa07]:443: connect: network is unreachable

Run 'docker run --help' for more information