From alex wennerberg to ~adnano/go-gemini-devel
Referring to the wildcard subdomain feature* (sorry, long day)
From alex wennerberg to ~adnano/go-gemini-devel
I appreciate the wildcard domain feature and I use it for flounder.online. However, I recently added a feature to flounder.online that supports users adding their own custom domains. I have this setup over http, but I'd like it cert creation worked easily and automatically with this library for gemini. Right now as a workaround I have it pull from a list of domains and call server.Register for each one on startup, but this doesn't work dynamically (ie, I'd have to restart the server every time a user adds a custom domain) Let me know what you think. If you're interested, I may add a patch for this All the best,
From alex wennerberg to ~natpen/gus
It looks like a lot of my replies got mangled in the patch UI, but the raw email should be viewable. Still getting used to this workflow Alex
From alex wennerberg to ~natpen/gus
Working on a v2 version of this patch! Knocked out some of the simpler fixes. Once Nat is able to answer some of the design Q's I'll send over a v2 patch On Tue Dec 15, 2020 at 3:30 AM PST, Remco wrote: > Hi Alex, > > I really like this addition and I am very curious about what it will > look and feel like in production. Here's a couple of things to think > about before we can push this to production: > > - "all" posts could be "a lot" Replaced "all" with "recent"
From alex wennerberg to ~natpen/gus
Already found an issue here -- it looks like I forgot to add url to the DB model. Still working on the email flow here, I think I would create a new v2 version of this patch? I can fix that after you are able to take a look at this -- maybe I can address other issues as well Thanks! Alex
From alex wennerberg to ~natpen/gus
I used gemini://testuser.flounder.online For testing if you're interested
From alex wennerberg to ~natpen/gus
* Look for gemlog feeds by searching for datetime logs
* Parse feed items from gemlogs, rss, atom, add to separate table
* Reformat existing feed finder to use new logic
* Add new endpoint to list items from aggregated list of feeds, sorted
by date
This isn't quite production ready, but it's ready for feedback! Here are
some open questions/issues: 1. Why is "rss.xml" excluded from crawling?
2. I currently pull all urls from rss/atom/gemlog feeds and feed them to
the user. Maybe I shoud parse these links as gemini resources and only
show those to the user? I'm still getting used to the structure of GUS
[message trimmed]
From alex wennerberg to ~sircmpwn/sr.ht-dev
Apologies for my mistaken previous patch -- this should be on the correct service. Alex --- lists.sr.ht/api.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lists.sr.ht/api.md b/lists.sr.ht/api.md index e443047..b985633 100644 --- a/lists.sr.ht/api.md +++ b/lists.sr.ht/api.md [message trimmed]
From alex wennerberg to ~sircmpwn/sr.ht-dev
Hope this is the right mailing list! Found some broken links in the mailing list API Alex --- lists.sr.ht/api.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lists.sr.ht/api.md b/lists.sr.ht/api.md index e443047..a00f4a9 100644 --- a/lists.sr.ht/api.md +++ b/lists.sr.ht/api.md [message trimmed]
From alex wennerberg to ~natpen/gus
Wanted to kick things off in this mailing list Now that Gemfeeds have been standardized (gemini://gemini.circumlunar.space/docs/companion/subscription.gmi) -- I am thinking that we could extended the feed crawler to look for gemfeeds Some implementation ideas: - In the crawler, check if a gemini page can be parsed as a feed by lookig for links that start with YYYY-MM-DD - Maybe create a new table called feeds with a list of all the pages and when they were updated based on YYYY-MM-DD dates or by atom.xml/rss dates - Maybe list feeds reverse chronologically by last updated date. - Maybe aggregate _all_ feeds together into one list