[-] binwiederhier@discuss.ntfy.sh 8 points 1 year ago

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.

[-] binwiederhier@discuss.ntfy.sh 24 points 1 year ago

Use ntfy.sh. It's open source and has a free server.

Disclaimer: I made it ;-)

[-] binwiederhier@discuss.ntfy.sh 9 points 1 year ago

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.

[-] binwiederhier@discuss.ntfy.sh 38 points 1 year ago* (last edited 1 year ago)

Thank you for contributing to the magic of 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?

[-] binwiederhier@discuss.ntfy.sh 20 points 1 year ago* (last edited 1 year ago)

Related question: is "Hot" super buggy? I am on 0.18.0, but I still often see really really really old posts (1 year old, 2 years old) sprinkled in with new stuff, and I often see clusters of 5-10 posts of a single community grouped together.

I have to pay extra attention to the post age because of this.

1

Due to the nature of the default robots.txt and the meta tags in Lemmy, search engines will index even non-local communities. This leads to results that are undesirable, such as unrelated/undesirable content being associated with your instance.

As of today, lemmy-ui does not allow hiding non-local (or any) communities from Google and other search engines. If you, like me, do not want your instance to be associated with other content, you can add a custom robots.txt and response headers to avoid indexing.

In nginx, simply add this:

# Disallow all search engines
location / {
  ...
  add_header X-Robots-Tag noindex;
}

location = /robots.txt {
    add_header Content-Type text/plain;
    return 200 "User-agent: *\nDisallow: /\n";
}

Here's a commit in my fork of the lemmy-ansible playbook. And here's a corresponding issue I opened in lemmy-ui.

I hope this helps someone :-)

[-] binwiederhier@discuss.ntfy.sh 11 points 1 year ago

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/

18

cross-posted from: https://discuss.ntfy.sh/post/30818

Hello friends 👋, it's that time again. A new ntfy release has landed. This one is pretty cool!

For those who don't know, ntfy is a a tool that lets you send push notifications to your phone from any script or server using a simple HTTP PUT/POST requests. It's 100% open source and self-hostable, and has an Android app and a web app. You can use ntfy like this (more in the docs). This will send a notification to your phone:

curl -d "Backup on $(hostname) complete" ntfy.sh/mytopic

I host free and open version on ntfy.sh, but you can host your own of course.

🔥 What's new? With this release, the ntfy web app now contains a progressive web app (PWA) with Web Push support, which means you'll be able to install the ntfy web app on your desktop or phone similar to a native app (even on iOS! 🥳). Installing the PWA gives ntfy web its own launcher, a standalone window, push notifications, and an app badge with the unread notification count. Note that this needs to be configured for selfhosted servers!

On top of that, this release also brings dark mode 🧛🌙 to the web app.

🙏 A huge thanks for this release goes to @nimbleghost, for basically implementing the Web Push / PWA and dark mode feature by himself. I'm really grateful for your contributions.

❤️ If you like ntfy, please consider sponsoring us via GitHub Sponsors or Liberapay, or buying a paid plan via the web app. Contrary to "popular" belief, I am not swimming in money due to the paid plans. 😬

Detailed release notes: https://docs.ntfy.sh/releases/

Other links:

Public topics:

4
6

Hello folks,

Request for testing: The next ntfy server release will contain a progressive web app (PWA) with Web Push support, which means you'll be able to install the ntfy web app on your desktop or phone similar to a native app (even on iOS! 🥳), and get basic push notification support (without any battery drain).

Installing the PWA gives ntfy web its own launcher (e.g. shortcut on Windows, app on macOS, launcher shortcut on Linux, home screen icon on iOS, and launcher icon on Android), a standalone window, push notifications, and an app badge with the unread notification count.

Testing instructions: The (hopefully) production ready version of the PWA is currently deployed on https://staging.ntfy.sh/app -- Install instructions with screenshots can be found in the docs (https://docs.ntfy.sh/subscribe/pwa/).

Please report bugs or issues on Discord, Matrix, or Lemmy (!ntfy@discuss.ntfy.sh). PLEASE HELP TEST

Huuuuge thanks goes to @nimbleghost for developing this entire feature top to bottom. If you throw donations (GitHub Sponsors or Liberapay) my way, I'll share them with him. He certainly deserves it for all this great work. 👏

-- If you don't know what ntfy is: ntfy (pronounce: notify) is a simple HTTP-based pub-sub notification service. You can use it to send push notifications to your phone via HTTP PUT/POST. You can selfhost it or use the hosted version on ntfy.sh

2
submitted 1 year ago* (last edited 1 year ago) by binwiederhier@discuss.ntfy.sh to c/asklemmy@lemmy.ml

I have asked this question to countless people (mostly in hair salons) as an alternative to small talk, and it always yields interesting results.

Rules:

  • You get the money right now, right where you are. If it's 10pm and you're in the middle of nowhere, your money will still go poof at 11pm.
  • As a result of the above, tell us what time it is and roughly where you are (big city, desert, small town, ...)
  • You must spend the money. You cannot give it to someone to hold on to it for you for a while.
  • Normal world rules apply, e.g. you cannot buy a $250k car at a dealership in 1h in cash, and you cannot buy a house in 1h either.
  • Remember that getting from where you are to the place you need to go takes time. Factor that in!

Edit: I'm glad you guys had fun with this one. Feel free to post similar hypothetical questions. I kinda like these.

Edit edit: Free advertising 😅 --> I run and maintain an open source push notification service called ntfy, which let's you send notifications to your phone via PUT/POST, like curl -d "backup successful" ntfy.sh/mytopic. Go check it out.

[-] binwiederhier@discuss.ntfy.sh 9 points 1 year ago* (last edited 1 year ago)

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.
[-] binwiederhier@discuss.ntfy.sh 12 points 1 year ago

I'll be sure to remind everyone that it was you who started the trend.

[-] binwiederhier@discuss.ntfy.sh 8 points 1 year ago

You just made it a thing. Congratulations, you started a trend.

[-] binwiederhier@discuss.ntfy.sh 5 points 1 year ago

I know this is possibly a little insensitive, but I find it quite poetic for the folks to die similarly, and in proximity to the Titanic. They must have really liked the Titanic, and they died doing something that they've probably looked forward to a long time.

[-] binwiederhier@discuss.ntfy.sh 41 points 1 year ago

You got a lot of heat in this discussion, but let me be one of the few to applaud you for actually making a proposal. Saying No is easy, but suggesting something and writing it down and putting it out there is hard.

I am a Principal Engineer by trade, and i do what you did here all the time. I put out suggestions to my team and let them absolutely wreck it. This is how you advance and enhance your idea. Listen and learn from the feedback and suggest another thing based on what you have learned. Rinse and repeat.

That's how you get to a great proposal. Keep at it. Well done.

[-] binwiederhier@discuss.ntfy.sh 11 points 1 year ago

The privacy stinks you say? Did you know that Likes and Dislikes are public too? That was the most shocking to me. Because it is very much not like Reddit or others.

It's still a fantastic piece of software, with all its flaws, though.

4
submitted 1 year ago* (last edited 1 year ago) by binwiederhier@discuss.ntfy.sh to c/selfhosted@lemmy.world

cross-posted from: https://discuss.ntfy.sh/post/3200

I use ntfy (on another instance) + healthchecks.io to wake me up at night when ntfy.sh is down (crazy inception, right?). It's the "poor man's PagerDuty" if you will. It works amazingly.

Here's how I set it up:

  • I signed up healthchecks.io (free plan) and configured a project for "ntfy.sh" with a "ntfy" integration, i.e. publish to ntfy.example.com/<secret> with max priority
  • I have two different hosts execute small "integration ntfy.sh tests" and only ping healthchecks.io if they succeed. If they don't healthchecks.io will publish to ntfy.example.com/<secret>
  • In the ntfy Android app, I subscribe to ntfy.example.com/<secret>, enable "Keep alerting on highest priority", and make it override DND (do not disturb) for this topic.

Now when ntfy.sh goes down, the integration tests in the cronjobs will fail, and so healthchecks.io will not be pinged, which will trigger it to publish to ntfy.example.com/<secret> and let my phone consistently ring until I acknowledge it.

(Disclamer: I am the maintainer of ntfy. Hope posting this is fine. Happy to answer questions; I also have a brand new ntfy community, feel free to join)

view more: next ›

binwiederhier

joined 1 year ago