πŸ’Ύ Archived View for bbs.geminispace.org β€Ί u β€Ί gritty β€Ί 3470 captured on 2023-09-28 at 17:12:43. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2023-09-08)

➑️ Next capture (2023-11-04)

🚧 View Differences

-=-=-=-=-=-=-

Deep Space Network (DSN) Antenna

As per a suggestion by @solderpunk, I've rebranded my clone of Antenna to be Deep Space Network (DSN) Antenna, so as not to compete with the main site.

In addition, the theme of the site is non-technical: deep thoughts for the deep space.

I know that keeping technical posts off there will be challenging especially if you have 2 gemlogs back-to-back that are of both categories, but in the main I'd like to see more "thoughts about life" posts in DSN.

If I find that this is hindering rather than helping geminispace, I'll consider taking it down, but for the time being consider this an experiment for a themed antenna site

gemini.smallweb.space/antenna/

πŸ€ gritty

2023-07-25 Β· 2 months ago Β· πŸ‘ skyjake, moddedBear, Addison, mieum, Ruby_Witch, gyaradong, aRubes

19 Comments ↓

🐻 moddedBear

I was actually thinking the other day about what if we had different Antenna instances running for different categories, so I'm glad to see this experiment to see how it works out.

There's the obvious challenge like you say of how to publish different posts to different Antenna instances. The way it's set up right now would require writers to have a separate feed for each themed instance they want to publish exclusively to, which isn't terribly difficult but also isn't ideal either.

πŸš€ IO

Non-tech theme is a great idea. It’s like a hall of mirrors sometimes with all the tech posts so it will be a breath of fresh air to try something else.

🧢 mouseless

Love the no-tech focus, It's natural for the Gemini Community to skew extremely tech savvy And I find great comfort in a space trying to avoid that

β˜•οΈ mozz

Great name!

πŸ“» solderpunk

Sheeesh...I'm embarrassed to admit that I misunderstood Antenna's manual submission system (which I haven't used myself). You submit a feed URL after you post an update, you don't post a direct post URL. Shucks. That will, as folks have mentioned, make it hard to "quarrantine" occasionally non-tech posts from tech posts. Well, still, this will work to aggregate content from people who never post tech, and might even encourage people to start doing that if they previously thought nobody wanted that. Will definitely keep an eye on this!

πŸ“» solderpunk

Possible extra idea: when parsing the submitted feeds, drop any item if the title includes any of the words (case insensitive): linux, unix, bsd, plan9, nixos, mac, python, rust, golang, lisp, forth, fortran, compiler, gpl, fsf, foss....you get the picture. It won't be perfect, but a pretty short list will get rid of more than half the tech posts with minimal false positives.

πŸ„ Ruby_Witch

@solderpunk I don't know, I tend to mumble incoherently about Linux occasionally even when I'm talking about completely unrelated things sometimes. :)

But I think this is a nice idea! It's good encouragement for capsule content to broaden its focus a bit.

πŸ“» solderpunk

@Ruby_Witch I was thinking of applying the "blocked words" list exclusively to the title. You can mumble about Linux occasionally in the body of the post no worries. I would argue that if it's tricky to keep "Linux" out of the title, it's probably *not* completely unrelated. ;)

🐝 Addison

I'll echo the appreciation for non-tech content. πŸ‘

πŸš€ stack

Thank you! I love Antenna, but I think that decentralizing is good, and Antenna was becoming too central to (at least) my view of Gemini. Noobs may think that it is Gemini!

I think if you let it run free after minor shepherding it will naturaly become a less-tech or tech-free zone...

πŸ€ gritty

Thanks all, I appreciate the inputs

I was thinking that one solution would be if the static site generators out there could separate logs based on a topic. So for instance if you tag your gemlog "technical" it would put it in the technical gemlog page and so forth.

@solderpunk I like your idea of filtering...I may look into this. I also thought about a per-post aggregators but this could be cumbersome for the authors especially if you have scripts already setup.

2023-07-26 Β· 2 months ago

πŸ€ gritty

Adoption is going to be slow and that's totally fine and expected. I'm hoping that this turns into an Antenna network where we have numbers and link to one another, say like "DSN 1965" or similar. Time will tell.

πŸš€ stack

So I have a gemlog that does not separate between tech and non-tech posts... I don't see how I can submit only non-tech posts to you! If I skip submissions on tech days, next day's submission will force the tech post into yesterday's entries...

Auto-filtering by title may work, but I wonder if there is a way to have the users tag their posts... Or submit an actual URL of a post instead of index...

πŸ€ gritty

@stack yeah, I've been thinking about this. I don't expect everyone to do the same, but I just created a separate gemlog page for my technical entries. I also considered tags, but that would require a lot of parsing for every submission.

I'll have to think about this

πŸ€ gritty

For anyone looking to get Antenna set up themselves:

gemini://gemini.smallweb.space/tech-gemlog/20230725-setting-up-antenna.gmi

πŸ‰ gyaradong

+1 to just having the sites do the filtering. Maybe a dsn feed url instead of the full one.

πŸš€ stack

There seems to be a bug! I just submitted today's entry, and it picked up older entries yet again, doubling up. I think that today I submitted `.../gemlog` while yesterday, `.../gemlog/index.gmi` and it registered it as a different feed.

πŸ€ gritty

@stack Ah, I see that. I wonder if the main site does this too.

πŸš€ stack

Wonder no more - the main site does it too. So resolving aliases is not something Antenna does... To do so would require maybe keeping a hash of each ingested index page, and ignoring duplicate submissions, even if they come from a different URL... Or check the actual links (in the generated page) for duplicates.