It'd be great if schools taught foundations like how the internet works (not in-depth, but basics like what a server is) and how to create your own server. People would get gradually less afraid of technology and that'd enable systems like this.

As it stands, people are just more comfortable using walled gardens because their data is managed for them and they don't bear any responsibility for it.

Comments URL: https://news.ycombinator.com/item?id=48794162

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=48148115

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=47598511

Points: 423

# Comments: 484

Comments URL: https://news.ycombinator.com/item?id=47126287

Points: 4

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=47075400

Points: 105

# Comments: 95

Blogrolls are a cool way to share interesting feeds, be it the ones you follow personally or topic-specific collections. The existing editors I found were really basic, basically just textboxes.

I attempted to create one that's easier to use and includes more features.

If that contributes to blogrolls being more used in the future I'm happy to have done something. That's something I'd love to see. Anyway, would love to hear what you think.

The features this thing has are:

  * OPML import and export
  * Edit and share links (no account necessary for editing, can share readonly version)
  * Create copy and edit (to start from a readonly version)
  * Adding different link types: feed, website newsletter
  * Automatic feed finding (just add website and click on 'Check feed')
  * Showing feed metadata: publishing frequency, last post date, language
  * Inline email to feed creation: add a newsletter item, click 'Generate email', and subscribe to the newsletter with the email
  * Tagging of items
  * Reordering (that's a bit hidden, need to grab the icon on the top left to drag and drop)

Comments URL: https://news.ycombinator.com/item?id=47072302

Points: 1

# Comments: 0

I built a feed reader with that concept in mind, having a separate triage stage where you only decide if it's worth reading or not. This will make it easier to handle large feed lists and find the best articles from them.

https://lighthouseapp.io/

Comments URL: https://news.ycombinator.com/item?id=46374941

Points: 2

# Comments: 1

Many sites have rss, it‘s just not advertised as much as it was some years ago. I built a feed finder tool that goes far beyond rss autodiscover, it might be useful: https://lighthouseapp.io/tools/feed-finder

And an article how it works: https://lighthouseapp.io/blog/deep-dive-finding-rss-feeds

Textwave is a browser-based document editor. All data is stored in the browser (local storage and IndexedDB). Currently it's a side-project for me. The main differentiator is the version system. Typical editors only have one list of versions. Going back from version 5 to version 2, editing something, and creating a new version, appends to the list as version 6. Textwave's version system is closer to git (though not the same). It lets you go back, edit, and create a new version directly below the selected version. Basically it creates a new branch.

Current features (beyond normal document editing) * Comments, suggestions, and replies * Create/rename/delete versions * Showing added/removed words to previous version * Preview version on hover * Export to Markdown and HTML (inlines images with base64) * Export and import documents via JSON * Light and dark mode

Why did I develop it?

I wanted something where versions feel lighter than the web-based editors I'm used to. When I write an article, I want to create a version without much fanfare. Similar to what I am used to when creating a git commit. With other editors creating a version feels very heavy.

Another goal was that all history is preserved, so that I don't need to create versions for everything. Every change I make should be recoverable. Often I write something where I believe it might be useful later on, just not now. With that I can always recover it. Textwave currently already stores all changes, but doesn't expose them in the UI just yet.

What's planned for the future?

There are a couple of issues that I want to iron out. Larger features that I want to add (as time permits) are * Make usable on mobile * Shortcuts * Showing full edit history * AI integration (e.g. highlight text and ask for separate phrases, style checker, research assistant - the options are endless), with bring your own API key

I'd also love to calculate metrics like "information density", but less sure about that.

Comments URL: https://news.ycombinator.com/item?id=46137966

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=45517134

Points: 341

# Comments: 203

Comments URL: https://news.ycombinator.com/item?id=45289037

Points: 1

# Comments: 0