cylo's comments

This has happened in the past (see: https://news.ycombinator.com/item?id=44934518) and it seems to be happening again at the moment. It's not clear where to report the outage to.

This has happened before and it will happen again. Outages happen.

Can you share with us what the best point of contact or escalation path to reach out to the next time it happens on the Algolia side?

Built a site that will follow development of popular upstream open source projects on a daily basis and uses AI to summarize the commits and attempt to make it easier to track what's going on with the project: https://gitpulse.org

I disagree that it's disingenuous. I would love to see Google and other corporations that make use of Debian fund the development of good default AppArmor profiles for many common daemons. Right now they simply don't exist and users are left to fend for themselves.

The point made in the article is that security is hard and often thankless work. So it's not something that's conducive to volunteers doing in their free time often. It does take funding to move the needle on this here, and I think Red Hat is proof of that.

That's a fair suggestion. I'll see about including some functionality for users to include additional news sites.

In the meantime, we did used to carry Al Jazeera but their endpoint had broken for some time. I've re-enabled it now to begin ingesting.

A very different approach, but same fundamental concept: https://brutalist.report

To echo the op's call to action:

If vim has ever played a role in your computing life, please make a donation in Bram's honor over at https://iccf-holland.org/

Sure, I suppose. I've never been called a sockpuppet before so I'm simultaneously insulted but also...honored in an odd way?

Anyway, I'm not sure what else you'd have me do here. We all have to start somewhere. I put my thoughts out there under something I directly control and I'd rather people focus on the central thesis of the thoughts being proposed over resorting to personal attacks.

I'll continue posting small essays on relevant topics under the domain.

Hi. Author here. I’m not a sockpuppet and genuinely have no affiliation with Oracle. It’s purely my own technical opinion.

I only recently registered the site and set up the blog because I had nowhere else to post it and did not want to use a hosted platform like Medium.

I was watching the recent Red Hat debacle from the sidelines and had some thoughts to put together about the general Enterprise Linux model.

It's true that Red Hat does pull in changes from upstream for several subsystems of Linux. It's genuinely a frankenkernel mixed with code from 6.3, 6.1, etc.

But you're still beholden to what the Red Hat maintainers are pulling in and focusing on. It's still not a general follow upstream wholesale.

You can see and track what UEK is doing by looking at their Github: https://github.com/oracle/linux-uek/commits/uek7/u1

This is a nicely designed application. I've always struggled to make UIs look good like this, even with SwiftUI which ostensibly should make it easier.

Any tips to share for how to approach SwiftUI code to achieve the sort of aesthetic you've got here?

Mine has been a retro news headline aggregator: https://brutalist.report

I really appreciate this effort. I think the web needs more of it and it’s why I built something similar over at https://brutalist.report.

Can you share any stats around the conversion rate for how many visitors end up converting to your Plus service?

I've implemented a 'limit' query parameter you can optionally supply to control how much content is returned back from search source.

Example: https://brutalist.report/?limit=10 or https://brutalist.report/topic/business?limit=10

I've now implemented a JSON API for you to use at /api.

Example to get the tech topic via API: https://brutalist.report/api/tech

Or front page: https://brutalist.report/api/

Enjoy!

The whole thing is written in Go on my end. Ingesting new headlines is handled in a goroutine that spawns within the process every 30 mins using a combo of the wonderful gofeed (https://github.com/mmcdole/gofeed) and colly (https://github.com/gocolly/colly) libraries.

When loading the front page, you're loading a 1-minute-cached HTML page of it that was constructed out of headlines already in my PostgreSQL database that were put there by the ingestion goroutine.

I like the idea of word clouds actually, I think you're on to something there. I think you just need to pre-generate them rather than doing it adhoc (if that's what you're doing here) for speed. Additionally, perhaps consider using sentiment in a way that orients stories based on positive and negative sentiment. Right now I am not seeing how I as a visitor/user can act on the sentiment analysis as it is presented now.

It would be neat to see a collection of uplifting stories grouped together through the sentiment analysis.

Anyway, food for thought. I hope you keep hacking away on it as it's just good fun to build things.

One takeaway from feedback I've seen is I'll be implementing support for filtering by keyword at the URL level.

I'm inclined to keep this completely javascript-free.

This should be able to get you close to what you're asking for once implemented.

No monetization plan. Nor is there the temptation to. This isn't really something I built to make money. As mentioned, I built it mostly for myself. Happy to share it with others along the way. :)

It's interesting to see how polarizing it is to some folks.

1.) It is a lot! The frontpage in particular is almost overwhelming. Browsing by individual topics makes it a bit more digestible. One element I could support is a parameter you can supply in the URL to limit the amount of articles returned per source. The challenge with providing 15-30 high quality links is the "human editing" element required to do that effectively. I'd like to avoid that if at all possible, as well as not get into the business of harvesting visitors' personal information. There's no tracking or harvesting going on here whatsoever and I intend to keep it that way.

2.) Great idea, I could perhaps add an [hn] tag to those stories to preserve the link to the discussion.

Thanks. Absolutely, please feel free to scrape. Though that's always a brittle solution. I've added a JSON API to my todo list for it.