• Joined on 2024-02-08
b pushed to main at sigit/sigit.io 2024-09-12 12:17:49 +00:00
675a763af3 Merge pull request 'New Release' (#200) from staging into main
bf1b3beb63 Merge branch 'main' into staging
32a6f9d7a3 Merge pull request #199 from hotfix-remove-loop-9-12 into staging
5f0234a358 fix: remove unstable fetch events loop
235e76be4e fix: processing gift wraps and notifications (#193)
Compare 10 commits »
b merged pull request sigit/sigit.io#200 2024-09-12 12:17:47 +00:00
New Release
b commented on pull request sigit/sigit.io#195 2024-09-11 11:18:37 +00:00
Add Sigit ID as a path param

sigit id - what is this? should be defined

b commented on pull request sigit/sigit.io#195 2024-09-11 10:15:37 +00:00
Add Sigit ID as a path param

I would like to see:

  • more comments (eg, explanation of what the id is)
  • consistent, clear naming convention. sigit, sigitid, id, sigitkey (what are these?) vs sigitCreateId ->…
b opened issue sigit/sigit.io#197 2024-09-11 09:31:30 +00:00
Update licence to AGPL
b commented on issue sigit/sigit.io#196 2024-09-11 09:28:59 +00:00
Unable to log in

The popup box should be like the below, but without the autoclose timer, and using the text above instead of 'loading':

image

b commented on issue sigit/sigit.io#196 2024-09-11 09:14:19 +00:00
Unable to log in

Looks like that link above also considers Flamingo to be deprecated: https://github.com/aljazceru/awesome-nostr#deprecated

b reopened issue sigit/sigit.io#196 2024-09-11 09:06:02 +00:00
Unable to log in
b commented on issue sigit/sigit.io#196 2024-09-11 09:06:01 +00:00
Unable to log in

re-opening as we can fix the infinite spinner issue with a timeout and helpful message, eg:

Your nostr extension is not responding - please check for a popup window.
Note that not all…

b closed issue sigit/sigit.io#196 2024-09-11 08:56:51 +00:00
Unable to log in
b commented on issue sigit/sigit.io#196 2024-09-11 08:56:51 +00:00
Unable to log in

@humblegoat - thanks for raising the issue. We investigated (per comment above) going ahead and fixing this in the Flamingo extension, however we decided against it given the technical challenges…

b commented on issue sigit/sigit.io#196 2024-09-11 07:31:36 +00:00
Unable to log in

Seems this is due to an issue with the underlying extension: https://github.com/t4t5/flamingo/issues/2

This extension has not been maintained since.. Well, ever (there has only been one push…

b pushed to notification-debug at sigit/sigit.io 2024-09-10 12:44:08 +00:00
4c45a227f0 Merge branch 'staging' into notification-debug
e2b3dc13fb chore(git): merge pull request #192 from cache-checks-9-9 into staging
0244090c6a Merge branch 'staging' into cache-checks-9-9
f0ba9da8af fix: outdated cache checks
1d1c675dd7 Merge pull request #191 from lint-0-warnings into staging
Compare 9 commits »
b pushed to cache-checks-9-9 at sigit/sigit.io 2024-09-09 18:44:39 +00:00
0244090c6a Merge branch 'staging' into cache-checks-9-9
1d1c675dd7 Merge pull request #191 from lint-0-warnings into staging
70f646444b fix: add types to rootReducer, rename userRobotImage types
Compare 3 commits »
b pushed to main at sigit/sigit.io 2024-09-06 18:59:36 +00:00
09229f42c7 Merge pull request 'new release' (#190) from staging into main
f516fe82d7 Merge branch 'main' into staging
bf506705e6 chore(git): merge pull request #182 from 174-add-users-updates into staging
b8811d730a fix(review): remove inline styles
479cca2180 chore(git): merge pull request #183 from 172-sign-marks-scroll into 174-add-users-updates
Compare 69 commits »
b merged pull request sigit/sigit.io#190 2024-09-06 18:59:34 +00:00
new release
b pushed to staging at sigit/sigit.io 2024-09-06 15:37:18 +00:00
f516fe82d7 Merge branch 'main' into staging
20496c7e3e Merge pull request 'Releasing new design' (#161) from staging into main
Compare 2 commits »
b created pull request sigit/sigit.io#190 2024-09-06 15:37:04 +00:00
new release
b commented on issue sigit/sigit.io#180 2024-09-05 11:38:00 +00:00
Mobile flow with Fedi app

This is great!

However, nsec login is available for development purposes only, it's not a recommended (nor secure) way to use sigit.

Can we test again using the native Fed (NIP-07) signing…

b opened issue sigit/sigit.io#181 2024-09-04 19:29:10 +00:00
offline flow on mobile