Live data from Hacker News

Show HN: Openring, a free and decentralized network of blogs

git.sr.ht

61–70 of 101 posts

Re: Show HN: Openring, a free and decentralized network of blogs

#61
post #52

Earlier quoted context omitted.

Some people like Feedly, but I've always strongly disliked it for reasons I'll get into only if someone wants. (Some of them may not even be current, I haven't really checked the ecosystem since the year Google Reader died.) 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…

I also hated Feedly, whose cardinal sin seemed to be that it's not Google Reader. Nowadays I use Newsblur, which is close enough to Google Reader, and I wholeheartedly recommend it.

Newsblur was one of two others that I gave a go after the Google Reader demise (also TheOldReader). While I liked it okay, I ended up preferring T.O.R. (and then Inoreader) to it because the interface (at the time) was very messy and they had scaling problems with the deluge of new users at the time.

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.

Re: Show HN: Openring, a free and decentralized network of blogs

#62

It's interesting that none of the comments so far complain about the size of the binary (13MB!). Nodejs and Electron projects get flak for this all the time, but Go somehow gets away with it.

Wow, I didn't know Go had large binaries. There's no reason it should though. As Go programs are compiled down to native code, if as the last step of compilation, the equivalent of unix strip (or the JavaScript world's tree shaking or the JVM world's ProGuard) was run, the binary would only have code that's actually used. Since Go is a relatively young language, it might be that implementing this was just not that hi…

Related: https://golang.org/doc/faq#Why_is_my_trivial_program_such_a_...

Also there are no media files embedded, the whole project is 130LOC + some html markup:

https://git.sr.ht/~sircmpwn/openring/tree/master/openring.go

Re: Show HN: Openring, a free and decentralized network of blogs

#63

Earlier quoted context omitted.

How would you go about getting that information on existing blogs? A great many blogs have 'blogrolls' but scraping that information seems far more time-consuming than it ought to be due to the variations in layout etc. etc.

Wordpress-based blog proprietors are likely to maintain their blogrolls using Wordpress’s Links feature. Because this is a standard module that produces more or less the same output across all WP blogs, it is rather easy to parse for and scrape. 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.

I'll give that a look. It's been a while since I checked into it but I've been wanting to map a particular blog network for a long time so that sounds very helpful.

Re: Show HN: Openring, a free and decentralized network of blogs

#64

Looks nice. Is there any reason to use getopt over flag in Go? How do you find the experience with sr.ht?

I prefer getopt because it's more succinct and more standardized. 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: https://sourcehut.org

Heya, so I just checked out Sourcehut and despite really wanting to use it (and pay) I decided not to. But because I find the product cool, I figured I should note why. So,

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.

Re: Show HN: Openring, a free and decentralized network of blogs

#65
post #15

What do everyone use for feed reader !? My old phone used to have a built in feed reader. And my old browser also used to have a feed reader. Looked on Google play and there where very little to choose from. Thinking of creating my own feed reader ... Or have "blogging" moved over to "Youtubing" and the occasional podcast !?

I went through a handful of RSS readers over the years till I settled on QuiteRSS (https://quiterss.org/). It's a Qt native application with builds for many operating systems. It's still in active development, fast, and has a nice interface.

Re: Show HN: Openring, a free and decentralized network of blogs

#66

It's interesting that none of the comments so far complain about the size of the binary (13MB!). Nodejs and Electron projects get flak for this all the time, but Go somehow gets away with it.

I’ve never seen anybody complain about binary size in Electron. Most complaints are about RAM and CPU usage.

Re: Show HN: Openring, a free and decentralized network of blogs

#67

It's interesting that none of the comments so far complain about the size of the binary (13MB!). Nodejs and Electron projects get flak for this all the time, but Go somehow gets away with it.

Go binaries tend to be fairly static, relying very little on system libs. It also makes some size tradeoffs for better load times. Also, compared to NodeJS and Electron... it’s still tiny. Not that anyone cares so deeply anymore.

Re: Show HN: Openring, a free and decentralized network of blogs

#68

Earlier quoted context omitted.

I prefer getopt because it's more succinct and more standardized. 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: https://sourcehut.org

Might I ask whether you have any intention to revisit this issue? https://todo.sr.ht/~sircmpwn/todo.sr.ht/176

Isn't that what the issue says he will do?

Re: Show HN: Openring, a free and decentralized network of blogs

#69

Earlier quoted context omitted.

I prefer getopt because it's more succinct and more standardized. 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: https://sourcehut.org

Might I ask whether you have any intention to revisit this issue? https://todo.sr.ht/~sircmpwn/todo.sr.ht/176

I stated my intentions on the ticket.

The puritanical (not to mention sexist) complaints that you can see the knees of an alledgedly "high school" girl on an obscure corner of the legacy site is not something I have a lot of patience for. This ticket is really a thinly veiled hatred of anything "anime". Eventually the page will likely go away in the due course of development of the service, but I'm not in any rush to appease puritanical jerks who make a moral appeal to hide their distaste for anything Japanese. These people are not uncommon, you get pretty good at recognizing them.

Re: Show HN: Openring, a free and decentralized network of blogs

#70

It's interesting that none of the comments so far complain about the size of the binary (13MB!). Nodejs and Electron projects get flak for this all the time, but Go somehow gets away with it.

I could definitely stand to strip the binary (saves about 2M), but the main issue is that (1) it's statically linked and (2) I actually pull in a surprising amount of dependencies for a ~100 line program. It uses an template parser & renderer; an HTML cleaner; a time formatter; an RSS/Atom parser; TCP, HTTP, and XML implementations; and extra handling for Unicode. Even then, 11M is a bit excessive.

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.

Post reply on HN