Just try it out. I make no guarantees for odd setups like that though. :-)

That … actually looks and feels pretty slick. Very neat UI.

Great writeup thank you. May I just say that tmyour original plan was both ambitious and a little insane. And even the current cost and infrastructure is bonkers IMHO.

I do hope you’re getting donations to help with the cost. Good luck.

My instance is on the other end of the spectrum: I pay $6/month for it on digitalocean. It has 1G of RAM. It crashes every now and then, likely because of the RAM and OOM killer. But it’s only for me and a few ntfy fans, so it’s quite different.

You can type reset to fix your terminal if it gets messed up like that.

Excuse my ignorance, but where can I find details to this issueand does it affect only 0.18.1, or also 0.18.0?

That looks pretty neat. Thanks!

You really should. It’s pretty darn amazing.

I have noticed that I use it less myself. I think honestly though, at least for me, that it is 90% related to the clunky and awkward UI of ChatGPT. If it was easy to natively type the prompt in the browser bar I’d use it much more.

Plus, the annoying text scrolling thingy … Just show me the answer already, hehe.

Thank you for contributing to the magic if the old school internet.

My question: How does one get to write an RFC? Do you have to become part of a certain group, or just be known in certain circles, or do you just start writing and then submit it somewhere? If I had a great idea that I think should become an RFC, what is the process to make this a reality?

Install Debian Stable on a SSD, most likely via debootstrap from the Ubuntu system

What an interesting way to install a new system. I’ve only ever done that for image building purposes. Why would you do that instead of just installing it from a flash drive?

Also: it sounds like you’re manually installing things. I would suggest Ansible or something similar, so that reinstalling isn’t so brittle and manual.

There is no way to exclude individual communities. The post URLs are generic, like /post/1234. From nginx or other proxies, I cannot tell what community they belong to. I would love to have my own be searchable, but not at the price of tainting my project’s reputation.

I asked the same question on r/selfhosted a few weeks ago, and I was downvoted just for asking the question.

https://www.reddit.com/r/selfhosted/comments/13elu4p/why_downvote_so_much/

I concur.

It’s already integrated into a bunch of things, especially the *arrs, but if you have suggestions, please let me or the maintainers of the other software know.

Here’s a list: https://docs.ntfy.sh/integrations/

It only works with 16.4 afaik.

Related to another Reddit app, but not RIF:

The Relay for Reddit dev (u/dbrady) is bravely working on Relay. I got an update yesterday. The changelog said “further reduce API calls”. I think he actually wants to make it a paid app, which I’d gladly pay for.

I hate the Reddit change as much as the next guy, but if the Relay dev can actually make a profit from it that’d be awesome. The app cost a one-time $4 or something, which I’m sure he never made bank with. Having like $3-5/month for it would probably be sustainable.

Awesome. Thanks for sharing 🙏

Cool thanks

This is neat, but it should really be part of Lemmy to be able to link between instances in a way that rewrites the link to your own instance, and makes subscribing easier.

I just read this article and what Meta is doing then triggered all the alarm bells!

This tactic even has a Wikipedia page: Embrace, extend, and extinguish

From the Wiki (quite enlightening):

The strategy’s three phases are:

• Embrace: Development of software substantially compatible with a competing product, or implementing a public standard.
• Extend: Addition and promotion of features not supported by the competing product or part of the standard, creating interoperability problems for customers who try to use the “simple” standard.
• Extinguish: When extensions become a de facto standard because of their dominant market share, they marginalize competitors that do not or cannot support the new extensions.