💾 Archived View for geminiprotocol.net › news › 2023_06_28.gmi captured on 2023-09-08 at 16:06:35. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Some minor following up with regards to the previously announced CAPCOM changes:
2023-04-16 news post "CAPCOM changes"
Firstly, due to a file permissions error, it was not possible to submit new URLs for inclusion on CAPCOM for most of the month of June. Sorry! If you tried to submit a URL and were told "Error processing submission. Is this a valid URL?", this was the reason. The issue is fixed, it is now possible to submit URLs again, and several have already been successfully registered. So, if your earlier attempts failed, now is a perfect time to try again! In a few days on July 1st, the new maintenance script will run for the third time. This means the many capsules in CAPCOM's database which have gone permanently offline will hit "three strikes" and be reclassified as inactive. The odds of any given active feed being sampled for inclusion will then increase substantially.
Secondly, CAPCOM's behaviour since the beginning has been to show the 64 most recent posts from all the capsules polled. This worked fine in earlier days, but now there are a number of fast paced (by Geminispace standards!) capsules in the database which routinely make dozens of posts every single day. When one of these capsules makes it into CAPCOM's 100 for a month, "the most recent 64 posts" becomes a very short temporal horizon and posts from more typically paced capsules quickly get pushed off the end. To address this, I made two minor changes earlier this month to CAPCOM's behaviour. First, the output now includes the 128 most recent posts, twice as many as before. Secondly and more importantly, any individual capsule's presence is now limited to its most recent 16 posts. So now no single capsule can account for more than 12.5% of the total output. Hopefully this strikes a good balance between allowing the occasional busy feed to feature on CAPCOM (they're not doing anything wrong, after all) while making sure this is not at the expense of posts to less active feeds staying on the page for a reasonable time.