> A webring contained a list of websites that all contained a similar theme. A single moderator — or Ringmaster — was in charge of approving and adding each website to a webring. Sites participating in a webring would then place the ring’s navigation box at the bottom of their site, which would bring visitors to whichever site was next or previous in the list (depending on which option they selected). If a visitor was on the last site in the list and clicked next, the list would loop back and load the first website in the list, in essence forming a ring of websites.
Is there anything in the output html that would make this crawling easier to do?
RSS seems to persist because it’s on by default on almost all blogging platforms. How can we make this into an on by default option in the main static site generators and CMS’s?
However, if this Show HN tool is for static-site generator-based blogs, then individual bloggers may have more leeway on how to format their blogrolls.
However, the comparison to Electron is unfair. The base Electron package is well over 100M, more than 10x as large, and generally not statically linked. This binary also doesn't hog your RAM and CPU and GPU like Electron does.
Criticisms of something that needs a semi-permanent allocation of my laptop's memory (like slack or Spotify) don't really apply.
Alternatively, it's possible that the executable size is large because it: (1) actually contains a lot of in-use code, or (2) contains media files. I know on Windows, it's common for people to make media files part of the .exe file. The Windows Portable Executable (PE) format makes it quite convenient to do this; and the Windows API has functions that make loading up files bundled as part of the .exe file as seamless as reading from the file system.
Also there are no media files embedded, the whole project is 130LOC + some html markup:
You can’t really say “go gets away with it” as though these languages are doing the same thing.
That's just my anecdata
There are also quite a few self-hosted options, the most famous one that springs to mind is TinyTinyRSS (https://tt-rss.org/) but I'm sure there are folks who have more experience with any alternatives https://alternativeto.net/software/tiny-tiny-rss/
For those looking for something closer to the original Google Reader experience with a few extra (and very nice!) features, I would suggest Inoreader, which is what I've been using for many years now. It uses a Freemium model, rather than forcing everyone into an ad-based "free" version.
Any of the three were better feed readers than Feedly, which seemed closer to a Google News clone (or more recently, Mozilla's Pocket) that happened to have support for RSS feeds.
I don't use it anymore because I don't do RSS anymore. I found the constant browsing to be a bit of a desperate situation, the same way people constantly browse their Facebook account. I'd rather stumble upon a nice article.
Used https://tt-rss.org/ before, but had so much trouble after updates. Hit and miss.
I really like the simplicity and minimalism of Sfeed. I setup a nightly cronjob that generates an ordinary HTML page, from all the RSS feeds that I like to follow.
For reading the Reeder app (iOS, Mac)
How do you find the experience with sr.ht?
I made sr.ht :) I can't give you an unbiased opinion, but naturally I think it's quite nice given that I designed it explicitly to suit my needs. Check out the marketing page for some more details:
1. My primary projects of which I need private hosting contain many (less than a GB, currently) "large" files hosted. Of course, these files need to be tied to the source code. Currently I'm solving this with Git LFS. Now, I'm not exactly tied to the solution, I just want it to be fairly pain free and baked in, of which Git LFS does a good job on. I super look forward to Git LFS.
2. I know you're working on it, but I have no desire to change my workflow to be email oriented. I don't intend to debate it, it's just not what I desire. PR UIs would be hugely helpful.
#2 is barely an issue at all, because I know you're working on it. If I had GitLFS I would have signed up for $10/m as that's well worth it to me.
Appreciate the product, hope it does great things for you. I look forward to using it when/if you implement GitLFS or something like it :)
Thanks! As a potential customer I hope this was at least mildly helpful :)
edit: It should be noted that my GitLFS files are of course binary. 3D modeling, PSDs, that sort of thing.
Regarding point 1, I do eventually want to add git lfs support.
Regarding point 2, the only thing I can say is "don't knock it until you've tried it". As someone who's spent thousands of hours each in GitHub, Gerrit, and email, as well as some time in GitLab, Gitea, and Phabricator, I've tried a lot of workflows and email is by far the most efficient. However, in the future I plan on adding web UIs for review and patch submission which are backed by email underneath, so you can use the web or email - whichever you prefer. I think you ought to give email an earnest shot, though.
Also, lots of people use a subset of SourceHut, like the CI service for example, while still hosting git repos on GitHub or GitLab. Because it's modular in design, each piece can be useful ala-carte or composed freely with other solutions.
For now I'm building around Gitlab, possibly migrating to Github if I run out of LFS storage on Gitlab (Github lets you pay for more storage.. don't think I can on Gitlab yet..).
Appreciate your work :)
Its parser follows the POSIX utility syntax guidelines and behaves like most POSIX tools. The flag parser on the other hand is simpler, but can lead to some surprises if you are used to getopt-like parsing.
Looks a bit like what any RSS reader would provide. Or maybe it's meant to publish links to other blogs on a separate site, which could work if the articles have a somewhat permissive license, I guess.
I for one hope it catches on
Most centralized platforms seem to recommend other authors based entirely on the topic. You’re reading a post about Rails Generators? It’ll recommend other articles about the same thing. With WebRings it was way more diverse than that. End up on an electronics page and discover all sorts of other fascinating authors doing entirely different things.
Edit: I'm asking because I suspect your answer is going to be "it doesn't/that's not the point/who cares?" But people who read blogs will just flock to the centralized services that solve curation & search quite effectively and keep users reading. And then this centralized service will have strong incentives to become _more_ centralized, not less, and decentralized solutions like this one never really gain traction and become functionally irrelevant.
I don't think that's true. People read blogs by writers they like (they go directly to that writer) , or about topics that interest them (they follow links from a website or social account about that topic) , or because they're looking for a specific post about a specific thing (eg they Googled). None of those things are best served by gathering writers on a single centralised platform. In fact, so long as blog posts are open the reader probably doesn't care how the posts are published. (Side note: this is the flaw in Medium. No one want the subscribe to the Netflix of blogs. People might pay to access their favourite writer, but not in the long term.)
Centralized blog platforms serve the writer. They're easy, they often have good tools, and they have an audience, although I doubt that's actually very useful to most writers - just having more readers without caring who they are is pure vanity. You want relevant interested readers if your blog is going to be effective promotion for you.
Ultimately, blog platforms are fine. Writers are a great customer base to have. Just don't kid yourself blog platforms benefit readers. They don't.
They're generated by this software.
Looks like it takes RSS feeds and makes a blogroll. I thought most blogging platforms had that function built-in. Certainly Blogger does (ex: http://www.sloopin.com).
Maybe this is for if you built your own blogging platform and don't have a blogroll plug-in/feature available.
the subtitle is a little more informative: "A webring for static site generators." i'm glad to see this kind of the movement toward self-deplatforming.
i wonder how comments are both attributable and decentralized? i'm not a fan of comments being blog posts themselves (which would be one solution to this), as they're often "less formal" than a post and should reflect that.
The background technology: https://indieweb.org/Webmention
The rather unsuccessful try to do a indiewebring: https://indieweb.org/indiewebring
1/ Yes, it's a blogroll.
2/ It's meant for static site generators.
3/ It solves curation and search by you doing the curating yourself, in the form of providing links to RSS feeds of the blogs you like.
Looks really nice. I think I'll hook it up to my generator.
I understood what it's about after reading it in detail but I don't blame people who have questions here. That's all I'm saying.
> Search engines in general but Google in particular: they have warped the way we build websites, many websites used to have a splash or landing page first: “You have reached the Gates of Marlborodor” (complete with MIDI music) and a big Enter button. Search engines decided they didn’t like that so word spread to get rid of them. Rumors spread that large link pages (for surfing) might be considered “link farms” (and yes on SEO sites they were but these things eventually trickle down to little personal site webmasters too) so these started to be phased out. Then the worry was Blogrolls might be considered link farms so they slowly started to be phased out. Then the biggie: when Google deliberately filtered out all the free hosted sites from the SERP’s (they were not removed completely just sent back to page 10 or so of the Google SERP’s) and traffic to Tripod and Geocities plummeted. Why? Because they were taking up space in the first 20 organic returns knocking out corporate and commercial sites and the sites likely to become paying customers were complaining.
Comment is from here: https://www.kickscondor.com/when-the-social-silos-fall/#comm...
Blogrolls are returning here and there. Here's one I saw recently: https://www.gyford.com/phil/writing/2019/06/04/blogroll/
They have potential, but there are nuances to make them worth using
> ...fetch the latest 3 articles from among your sources... Then you can include this file with your static site generator's normal file include mechanism.