We had a temporary delay with outgoing federation. Everything should be recovered and back to normal now!
sunaurus
joined 2 years ago
Yes, they indeed blocked us a while ago, AFAIK it was planned as a temporary thing, but no idea where they stand on it now.
Hey! Do I understand correctly that your app is trying to fetch any /post/<id> directly from its source instance API? If so, I have a few ideas:
- If you detect anything that looks like a Lemmy post URL (
<host>/post/<id>), you could first try to make a request to<host>/version, and only treat the post as a Lemmy post if you get a JSON response from that endpoint where.software.name === 'lemmy'. Otherwise, open that URL in the browser.
- The above will already "fix" the issue, but custom frontends on subdomains is actually quite common, so if you want to handle those links without resorting to a browser, then: in cases where
<host>/versionis not a Lemmy response, but<host>includes a subdomain, you could repeat the same logic from step 1 for the parent domain as well. If you detect a Lemmy API at the parent domain, then just use that to fetch the post.
I’m already accustomed to the light theme of Lemmy and can’t find how to switch from dark to light in “Next.”
This is planned after the 3rd milestone is complete!
The red, green, and blue buttons in the footer seem to do nothing.
They should change the primary color in the UI - are you sure it's not doing this for you? Maybe it's just enough of a subtle change that it's not immediately noticable?
The notion on every post that “Your IP is hidden from another Lemmy instance” is kind of annoying and useless. Why is it there?
Most (all) other Lemmy frontends will always leak your IP to external media hosts, I wanted to handle this a bit differently in lemmy-ui-next by proxying by default (to improve user privacy). The message is there to let you know if a specific piece of media is being proxied or not - and the only way for something to not be proxied is for the user to manually approve it first.
I guess not all users will care about this, so maybe I can add a setting to hide the proxy indicator completely... I will think about it!
I dislike a little that it tries to copy the old Reddit interface. Although that interface wasn’t bad, and I’m the one who would first say “don’t fix what isn’t broken,” I’m more prone to seeing something new, some experimentation. Right now it feels more like “next to the old Reddit,” which isn’t exactly bad, but still…
It was an initial goal and guiding principle to heavily take inspiration from the great UIs of existing link aggregators like old reddit and hackernews. At the same time, I realize that this approach is not for everyone, so I am not against adding some different layouts (especially for the post list view) in the future.
Thank you for all the feedback!
This is planned after the 3rd milestone is complete!
Interesting idea, I think that will also require a small change in the Lemmy backend, but I think it's doable. Thanks!
You can check the federated/defederated instances for any instance on the /instances page. For example:
That's true, it will only show content which has been federated to lemm.ee, so indeed if you want to search for more content than is available on your instance, you would need some additional tools for that.
We had a temporary delay with outgoing federation. Everything should be recovered and back to normal now!