I am a junior engineer who is attempting to stave off the hell of writing javascript for the rest of his life. Originally went to school for embedded sytems programming but then got into the real world and realized that degrees and area of study mean nothing.
From ShockTohp to ~sircmpwn/email-test-drive
--- shocktohp | 1 + 1 file changed, 1 insertion(+) create mode 100644 shocktohp diff --git a/shocktohp b/shocktohp new file mode 100644 index 0000000..66cb3d4 --- /dev/null +++ b/shocktohp @@ -0,0 +1 @@ I have successfully used git send-email! -- 2.42.0 [message trimmed]
From ShockTohp to ~sircmpwn/email-test-drive
--- shocktohp | 1 + 1 file changed, 1 insertion(+) create mode 100644 shocktohp diff --git a/shocktohp b/shocktohp new file mode 100644 index 0000000..6d0ecfd --- /dev/null +++ b/shocktohp @@ -0,0 +1 @@ I'm about to try git send-email -- 2.42.0 [message trimmed]
From ShockTohp to ~adnano/astronaut-discuss
This is why I asked. Not looking to implement something undesired and out of scope. > > 1. Would the subscriptions be checked periodically while astronaut is > > running, when astronaut is first launched, or manually (e.g. on page > > refresh)? Are users expected to keep astronaut running in the > > background? I would check on subscription page load and reload, that seems reasonable. No point in checking if the user isn't navigating to that page after all. No need to keep astronaut running, as the state would be stored locally. > > 2. How would the subscription state be stored? How do you expect to
From ShockTohp to ~adnano/astronaut-discuss
I have been using astronaut as my main gemini browser for a few weeks now, and one thing has caught my attention. Many of the gemlogs I read either provide an Atom feed or have indexes set up as a feed[1]. I would like to be able to have astronaut subscribe natively to these and have a "subscriptions page that displays updates like an rss reader would, then let's me link to the new posts. I believe I could implement a bare-bones version of this myself, but want to know if it's in scope for astronaut to do this before I even begin. Thanks for the feedback!
From Kevin Conyers to ~sircmpwn/email-test-drive
--- This fixes the issues raised from the first patch. kevin | 1 + 1 file changed, 1 insertion(+) create mode 100644 kevin diff --git a/kevin b/kevin new file mode 100644 index 0000000..66cb3d4 --- /dev/null +++ b/kevin @@ -0,0 +1 @@ I have successfully used git send-email! [message trimmed]
From Kevin Conyers to ~sircmpwn/email-test-drive
--- kevin | 1 + 1 file changed, 1 insertion(+) create mode 100644 kevin diff --git a/kevin b/kevin new file mode 100644 index 0000000..b4380e4 --- /dev/null +++ b/kevin @@ -0,0 +1 @@ I'm about to try git send-email! -- 2.34.1 [message trimmed]
From Kevin Conyers to ~sircmpwn/email-test-drive
From: Drew DeVault <sir@cmpwn.com> --- README.md | 3 +++ kevin | 1 + 2 files changed, 4 insertions(+) create mode 100644 kevin diff --git a/README.md b/README.md index 224333d..e50be57 100644 --- a/README.md +++ b/README.md @@ -3,3 +3,6 @@ This repository is here to help users test drive their git send-email [message trimmed]
From Kevin Conyers to ~sircmpwn/email-test-drive
--- kevin | 1 + 1 file changed, 1 insertion(+) create mode 100644 kevin diff --git a/kevin b/kevin new file mode 100644 index 0000000..36ae7a4 --- /dev/null +++ b/kevin @@ -0,0 +1 @@ I am about to try git send-email -- 2.34.1 [message trimmed]