they arent doing anything atm

Logging out should bring me to the home page, not log in page.

Would be cool to add an image instead of just plain text when you have no unread notifications to show, similar to the image shown when you lose internet connection.

I enjoy the "Search for notifications" feature at the top. Found myself trying to filter for a particular project (repo), but had no luck

mounting the notifications component should probably fire off the real loader, not the syncer

Might be tricky since notifications logic happens above where toasts exist.

Might require larger refactor, which is entirely possible tbh.

• Move dark mode logic to index file
• Move toasts to index file

https://github.com/nickzuber/meteorite/blob/master/src/pages/Notifications/index.js#L157

Should be a one line fix -- just add .then(() => this.setState({error: null}))

I heard React hooks are great.

It would be awesome to see the status of the issue/PR notification.

I generally filter these out when looking through which notifications to read & respond to.

This should only happen for the current sorted status/filter.

There's probably a way to see if the tab has focus, probably sync on this.

Browser: Google Chrome Version 72.0.3626.119 (Official Build) (64-bit)
OS: macOS Mojave Version 10.14.3

Issue:
I'm not receiving any notification on my desktop.

I just discovered meteorite and already love the project. However I found an annoying UI issue on the notification panel as seen on the screenshot below:

Let me know If you'd like additional inputs.

Sometimes when I click on a notification, I want to come back to it later (RFCs, long and detailed PRs, etc).

It'd be great if there was an "undo" button somewhere that lets you "un-mark" as read for the notification you just opened.

We already support this manually, so this would just be an ease-of-access feature. Should be easy to add (famous last words).

and maybe resolved ones as well?

Support hotkeys to do things

Noticed that my "read notifications" bar shot up a ton after I archived a bunch of notifications – that shouldn't happen.

Simple fix – just remove the enhanced iteration of marking as archived

So "Desktop Progressive Web Apps" are a thing now, and they're AWESOME. Basically, with some work you can make an app "installable" and "first-class" on your OS, similar to how it'd work if it were wrapped in Electron. Its available on Windows, Linux, and Android on Chrome 70, and soon on macOS with Chrome 72.

In some ways, this just improves the feel of the app, but in other ways it can actually really make a UX difference. For example, if Meteorite were a PWA, then I could have a shortcut to it on my desktop that opened a siloed window (with no browser 'chrome') and could have native notification integration in the OS.

Also, PWA's basically require that your app uses a decent architecture, such as Service Workers, so you get all the benefits there too.

At the end of the day, if this were done, the app would feel basically native, which would be HUGE and super exciting, personally.

Create the ability to silence a thread from sending web notifications temporarily.

The trickiest part will be the UI/UX around this feature 🤔

It looks like the gatekeeper instance for production got hit when heroku took down the free tier.

I'm able to reproduce this issue consistently in production when trying to log in with my github account.

I think this functionality should be relatively easy to transition to a netlify, vercel, or cloudflare cloud function. Some prior art from a quick google search:

• https://github.com/gr2m/cloudflare-worker-github-oauth-login
• https://github.com/cadbox1/github-oktokit-oauth-netlify

Noticed that when I manually refreshed, it'd remove one of my notifications entirely.

Same when I searched.

Questions

Hi everyone.
Your project looks really nice and i will like to use it on my company private repos but it's asking for write access... so i am having trouble convincing them to allow me to use it. Is it really necessary to request write access to private repos of an organisation for it to work ?

Thanks in advance!

First time users should be get a few special treatments:

• first time loading the page, should check how many queued notifications there are.
  • a high number here could indicate that the user doesn't use notifications for triage, so we should ask them/recommend if they want to mark all as read

If a notification is staged and hasn't been updated in X minutes/hours/days, it should be set to closed.

Likewise, if a notification is closed and hasn't been updated in Y minutes/hours/days, it should be purged from the cache and effectively deleted.

It'd be cool to get a dark mode option :)

https://github.com/nickzuber/meteorite/blob/master/src/pages/Notifications/index.js#L353

Add a check here that only shows the notification if the ID is within our filtered notifications

Explore the idea of the website itself providing actual notifications to the user and what would go into this kind of feature

specific ones for:

• assigned prs
• review requested

Improve the name by making it more clear what that tab is

Hi, thanks for this great web app. In safari, on macOS Catalina 10.15.3, I've allowed notifications, yet I do not get any.

In the console log area, I see TypeError: undefined is not an object (evaluating 'Notification.requestPermission().then')

Thanks,
Linus

When the first and only notification is a review request, it doesn't seem to be popping up in any of the feeds.

We should make sure that things are being filtered correctly — we should also validate that this isn't just a bug with GitHub's REST API.

Hello, Nick. I am having trouble connecting my github notifications to Meteorite. I followed directions from the How to Use page, but still no connections. Any tips?

Also, apologies in advance. I'm a novice with programming.

i guess it is possible to get state_change reason if something happens after a PR/issue was merged/closed/etc

We should account for state_change and others, regardless of if we really see them or not.

🤦‍♂

The version in the footer right now is static — we should print the git hash from the latest commit.

This could be done via a pre-deploy hook which writes it to a txt file if we have to

With the search UI, we should be able to filter by repository and/or date; not just by PR name.

Might be a good opportunity to look into more rich query support here.

People who don't normally use their GH notifications for triage will have a lot of "unread" notifications that they might have already dealt with.

This button would allow as a soft escape hatch for starting fresh, without actually deleting anything from the cache.

An additional constraint should be that the last update is within X minutes/hours

Something like an inverted percentage backoff as the hourly limit is approaching.

I might not be using it a lot, but someone with a ton of notifications and subscribed to a lot of different repos (ahem, attius) might.