allows it to make its tokamaks at only two percent of the volume of conventional tokamaks

Strap that into a tank, with - hear me out - legs, and we’re golden.

With a small amount of effort and the use of https://github.com/nanos/FediFetcher and https://github.com/g3rv4/GetMoarFediverse you can mitigate basically all those issues. It’s still not perfect by any means but it results in a perfectly usable single user instance.

The first populates the replies of the home timeline posts you see (as well as profiles of people it finds in those replies) and the second pulls down all the content from instances you select for your followed hashtags (choose mastodon.social and you can guarantee you’ll see most all posts with those tags)

Yes. On older generation/cheaper ANC this is perceived as increased “pressure”. It doesn’t seem louder but the physical sensation of loudness is there.

The sound produced by ANC is the exact 180 degree inverse (or as near as possible) of the incoming bad noise.

It’s produced in realtime by dedicated signal processors and requires mic arrays feeding in the sound. The quicker your processing pipeline the better the match is and the more powerful the effect is.

There’s no prerecorded sound that would work.

Let’s be honest, this is only their outlook until the courts make their decision. They’ll sell if that doesn’t go in their favour.

IIRC your data would live on your chosen pod server - which does not have to be a fediverse instance.

Apple has pretty robust parental controls on their devices.

Source: am technical enough to have set them up.

If buying isn’t owning then piracy isn’t stealing.

Is Yorkshire tea similarly fiddled with? Beats the pants off PG Tips as a general rule.

Yeah, sadly not working on communities that exhibit this issue. This one (!lemmy_admin) is one. I have two posts showing on my instance, this one and another that seems to have been updated recently.

If I search for https://lemmy.ml/post/6417868 using my instances search I get no results found. The error in the logs is

2023-11-10T10:20:48.585813Z  WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: couldnt_find_object: data did not match any variant of untagged enum SearchableKinds
   0: lemmy_apub::fetcher::search::search_query_to_object_id
             at crates/apub/src/fetcher/search.rs:19
   1: lemmy_apub::api::resolve_object::resolve_object
           with data=Query(ResolveObject { q: "https://lemmy.ml/post/6417868", auth: Some(Sensitive) })
             at crates/apub/src/api/resolve_object.rs:19
   2: lemmy_server::root_span_builder::HTTP request
           with http.method=GET http.scheme="http" http.host=doomscroll.n8e.dev http.target=/api/v3/resolve_object otel.kind="server" request_id=4ef4bf5c-228f-4268-b798-3561a79d9a2f http.status_code=400 otel.status_code="OK"
             at src/root_span_builder.rs:16

LemmyError { message: Some("couldnt_find_object"), inner: data did not match any variant of untagged enum SearchableKinds, context: SpanTrace [{ target: "lemmy_apub::fetcher::search", name: "search_query_to_object_id", file: "crates/apub/src/fetcher/search.rs", line: 19 }, { target: "lemmy_apub::api::resolve_object", name: "resolve_object", fields: "\u{1b}[3mdata\u{1b}[0m\u{1b}[2m=\u{1b}[0mQuery(ResolveObject { q: \"https://lemmy.ml/post/6417868\", auth: Some(Sensitive) })", file: "crates/apub/src/api/resolve_object.rs", line: 19 }, { target: "lemmy_server::root_span_builder", name: "HTTP request", fields: "\u{1b}[3mhttp.method\u{1b}[0m\u{1b}[2m=\u{1b}[0mGET \u{1b}[3mhttp.scheme\u{1b}[0m\u{1b}[2m=\u{1b}[0m\"http\" \u{1b}[3mhttp.host\u{1b}[0m\u{1b}[2m=\u{1b}[0mdoomscroll.n8e.dev \u{1b}[3mhttp.target\u{1b}[0m\u{1b}[2m=\u{1b}[0m/api/v3/resolve_object \u{1b}[3motel.kind\u{1b}[0m\u{1b}[2m=\u{1b}[0m\"server\" \u{1b}[3mrequest_id\u{1b}[0m\u{1b}[2m=\u{1b}[0m4ef4bf5c-228f-4268-b798-3561a79d9a2f \u{1b}[3mhttp.status_code\u{1b}[0m\u{1b}[2m=\u{1b}[0m400 \u{1b}[3motel.status_code\u{1b}[0m\u{1b}[2m=\u{1b}[0m\"OK\"", file: "src/root_span_builder.rs", line: 16 }] }

but I don’t know if that’s helpful.

If you search for a community first time, 20 posts are fetched initially. Only if a least one user on your instance subscribes to the remote community, will the community send updates to your instance.

The point is I’m not getting 20 posts. I get nothing. I can subscribe and then get posts from that point forward as I’d expect.

I don’t think that’s true. Searching for a community typically brings back a fully populated page. None of the posts have comments or up/down votes, but they’re all there.

I’d say in maybe 20% of cases though it comes back empty.

Yeah. I looks like the beehaw thing has resolved itself. I don’t know why it was just them but I have been able to subscibe since yesterday. I’m guessing that this is an issue with the source instance rather than the requesting instance - maybe it’s not sending out an accept activity like it should.

I’m still seeing the lack of content in newly searched communities though. https://sh.itjust.works/c/plugins for instance just refuses to come back with anything.