I think you still have to specify the URL up to the greader.php page, maybe in your case it would be

https://freshrss.example.com/api/greader.php

Turning it on by default would be a massive disservice to the work that domain registries and registrars have been doing to allow Unicode to be used in domain names. In Spanish speaking countries the ñ character is pretty ubiquitous for example, and the workaround of replacing it with an n creates many problems like misdirected web traffic and typos in email addresses. Unicode in URLs and domain names is a feature, abuse should be attacked by means other than disabling it.

Is VR really so ubiquitous to warrant these concerns? In my opinion most of the warnings about how this technology encourages “escaping reality” apply more to things that have had an established place in society for decades, namely phones, social media and online gaming. I have two kids and a VR headset is the least of my concerns, but they could be sucked in to the non-reality of a personal phone in two seconds if I allow it.

I set this up on my instance about a week ago and it works perfectly, thank you!

I recommend NSD or Knot for strictly authoritative servers. BIND is great too, but it is built to do both authoritative and caching DNS which makes it a bit too “big” for the task of serving only authoritative DNS data. You can definitely configure BIND to only serve authoritative data though.

I can’t comment on running from a container, I’ve always worked with NSD/Knot/BIND building directly from source.

Well, you can fact check later right? If nothing else kids will learn to be bored again, which is good.

LastPass Authenticator can use SHA256, it works for logging in to my Lemmy instance. And you can use the app independently of LastPass, keeping everything on your device.

I believe the issue is that Lemmy expects the codes to be generated using the SHA256 algorithm, while most generator apps use SHA1.

No problem! FreshRSS really is amazing so I’m happy to help and spread the love.

Using .site-content container clearfix didn’t work because those are actually three separate CSS classes, so you’d have to use only one - for example .site-content. However, it looks like .site-content is too big, as it includes the website’s sidebar as well. You may already know this but in Firefox and Chrome you can right click anywhere on the website and use the Inspect option to look at the source, and clicking on a section of the source highlights the corresponding section of the website and this will help you find exactly the CSS class you’re looking for. I did this on a couple articles from Humble Bundle and found a couple of options:

• .post: This includes only the content of the post, excluding the title and the image.
• .site-main: This includes the title, author, image and the content.

Another useful tool in FreshRSS I forgot to mention is “CSS selector of the elements to remove”. You can use it to remove certain section from the full article, I’d recommend removing .sharedaddy and .entry-footer (the sharing links at the end of the article), and also .entry-header if you use .site-main as the CSS selector for the full article (.entry-header is the title of the article, but FreshRSS already fetches it from the RSS feed so you don’t need it in the body of the article as well). You can remove multiple sections by using a comma-separated list of CSS classes to remove:

.entry-header, .sharedaddy, .entry-footer

I’ve always known Drop for their audio sales and products, I hope they continue to collaborate with audio brands in the future. The Sennheiser/Drop HD58x is one of my favorites, it was hard to beat for the price when I bought them.

Before you go reading all that, out of curiosity I looked around the RuneScape site and found the News RSS feed here:

https://secure.runescape.com/m=news/latest_news.rss

That feed contains only titles, thumbnails and a very small preview of each article. However, with FreshRSS you don’t need to do scraping/crawling at all to get full articles from limited RSS feeds like this one. Here’s what you do:

1. Subscribe to the RSS feed in FreshRSS as you normally would.
2. Go to Subscription Management and find the settings for the RuneScape feed.
3. In the Advanced section of the feed settings, find the item called “Article CSS selector on original website”, and write .c-news-article__content in that text box. You can click on the button next to the text box to preview the full article that FreshRSS will retrieve.
4. Click Submit to save the changes, and then go to the bottom of the feed settings and click Reload articles so that FreshRSS populates the feed with a few full articles.

That should do it. The CSS selector essentially tells FreshRSS which section of the full article’s HTML/CSS is the body of the article, which FreshRSS then uses to populate the body of the RSS feed.

It can be done directly in FreshRSS and I’ve done it successfully with a few websites, though the process is fairly involved. Here’s a starting point, from the FreshRSS documentation:

https://freshrss.github.io/FreshRSS/en/users/11_website_scraping.html

This blog post (also linked in the FreshRSS docs above) proved extremely useful as an example on how to get started:

https://danq.me/2022/09/27/freshrss-xpath/

Good luck!

I think the apps currently in development will only get better with time, but currently the web app is my favorite way to browse Lemmy.

I see, thank you for the insight. According to this comment, after an instance on 0.18.0 is running one can still set it to private with federation enabled, so it seems this check is only preventing the instance from starting in that state.

I guess this comment was originally a response to a different problem, but in my case it wasn’t a “hack” - there was no problem with enabling federation on a private instance, and it worked as expected. I thought of a “private instance” as “can’t see it unless you log in, but federates exactly like a public instance would”, and that’s exactly how it worked in 0.17.4, but I understand if, in principle, it wasn’t supposed to work like that. Again, there was no need to hack anything on my end, it just worked.

At least on 0.17.4, with Private Instance and Federation enabled, the comments and posts I made to remote communities were federated correctly to other instances. The change seems very intentional, as shown by the error message I got after I upgraded:

lemmy_1 | Error: LemmyError { message: Some("Cannot have both private instance and federation enabled."), inner: Cannot have both private instance and federation enabled., context: SpanTrace [] }

ncgnzlcl_lemmy_1 exited with code 1

Thankfully the error was very explicit:

lemmy_1 | Error: LemmyError { message: Some("Cannot have both private instance and federation enabled."), inner: Cannot have both private instance and federation enabled., context: SpanTrace [] }

ncgnzlcl_lemmy_1 exited with code 1

With both options enabled, my instance operated as expected on 0.17.4: there was no anonymous access to anything, but once logged in you could subscribe to communities from any public instances. They don’t seem incompatible at all, and my posts and comments were federated correctly outside of my instance.

As if these two needed their egos stroked even more. I’ll never understand why billionaires need so much attention, and why on earth we give it to them.