undualies

joined 1 year ago
[–] [email protected] 4 points 2 weeks ago (1 children)

Try humming it in the Google or Sound Hound app. They work pretty well.

[–] [email protected] 19 points 3 months ago

It's CentOS 7.x

[–] [email protected] 6 points 5 months ago (1 children)

Nice work!

Out of curiosity, what repairs did the CRT need?

Obligatory safety disclaimer for people who want to repair old TVs: Messing with some of those electronics can be very dangerous.

[–] [email protected] 2 points 11 months ago (1 children)

Open source or proprietary drivers?

[–] [email protected] 2 points 11 months ago (3 children)
[–] [email protected] 9 points 1 year ago (3 children)
 

Dear Support,

I have a question about viewing communities across federated instances.

I had a lemmy.world login, but while it was less available last week, I created this lemm.ee account.

I used the very cool https://github.com/wescode/lemmy_migrate project to copy my subscriptions over, and in the end, got just a few of these:

Failed to resolve community 400 Client Error: Bad Request for url: https://lemm.ee/api/v3/resolve_object?q=https%3A%2F%2 Flemmy.world%2Fc%2F&auth=

Sure enough trying to browse to those lemmy.world communities from lemm.ee, they would show no posts.

However, if I switched back to lemmy.world and tried to view those same few communities, I would see posts.

In case there was any doubt about the instances being federated, I was able to see many other lemmy.world communities from lemm.ee, just not these few.

With just one exception, those communities posts are all visible now.

This occurred on July 3rd, before issues like this were reported: https://github.com/LemmyNet/lemmy/issues/3515

These communities were not particularly active, so assumed it was a feature and not a bug.

So is there some other perquisite to view posts from federated instances' communities? Subscriber count, post count, etc ...?

Thanks for reading.

view more: next ›