Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix notification special name #157

Closed

Conversation

ghost
Copy link

@ghost ghost commented Apr 3, 2024

if not currently in utc, the dayjs function was returning the wrong timestamp for beginning the day. it still had my timezone as part of it. this update uses the utc dayjs plugin to ensure we are using a utc-based comparison since event.created_at in nostr notes are supposed to be in utc time.

also added a basic nix flake file for getting a basic dev environment setup. i can remove this and put these files in the .gitignore if that'd be preferred.

case added 2 commits April 3, 2024 16:39
if not currently in utc, the dayjs function was returning the wrong timestamp
for beginning the day. it still had my timezone as part of it. this update
uses the utc dayjs plugin to ensure we are using a utc-based comparison since
event.created_at in nostr notes are supposed to be in utc time.
@hzrd149
Copy link
Owner

hzrd149 commented May 18, 2024

Sorry for ignoring this for so long, but this may not be an issue anymore since the next version does not show the "Today" or "Yesterday" label on notifications anymore

@hzrd149
Copy link
Owner

hzrd149 commented Sep 11, 2024

This is no longer an issue with the new notification view

@hzrd149 hzrd149 closed this Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant