Hacker News new | past | comments | ask | show | jobs | submit | letmeinhere's comments login

This advice is missing something crucial which is how to discover new creators sans feeds. Not saying it's impossible, but it's something they excel at and they've extinguished a lot of the old ways.

Great point. I'm personally trying linkblogging and following other link blogs inspired by Simon Willison [1].

The more people that do this the more we can start rebuilding networks of people we trust and still retain control over the diversity of our sources.

1: https://simonwillison.net/2024/Dec/22/link-blog/


Yeah this is super key. I think it's still possible to highlight new creators without algos, one way is to just involve more (only) humans in the process. This is what we're doing at Twigg, effectively letting users decide what gets highlighted and elevated to the rest of our members. - Too early to say how it'll play out, but it seems to be working well soo far...

A few ways I do this

* In Bluesky I read retweets and comments to find new people to follow.

* I send content to friends and they send some back. I’ve found creators this way.

* Search for interesting topics, see who is generating content on those topics. Follow/subscribe if you’d like to see more.


What's the contribution model moving forward? I see the repository is still active, but is it not still under the Eleven's control? How will it evolve when they stop accepting pull requests?


It won’t be under Elevens control, part of the deal I believe. They’re allowed to remain opensource. Not folded into ElevenLabs.

As for contribution model, it’s still something I’m trying to figure out. For the moment, it was just trying to get a self host build ready and working.

But I have admin rights to the repo, and am not working for ElevenLabs, nor officially Omnivore. I was just a contributor before.


That's good to know, thanks.


Only thing I'd quibble with is the reason most consumers switched off of pseudoephedrine. The manufacturers knew that the inconvenience of having to go to the counter would reduce sales so they just replaced it in the aisle with an identically branded product with a different active ingredient. Most people made no affirmative choice at all; they're just buying "Sudafed", but now it's a placebo.


Python doesn't use semantic versioning. The number after the first period is a major (annual) release and can and does contain breaking changes (though so far never on the scale of the 2->3 upgrade).

We may never see a 4.0 because of the scar tissue, but the language continues to evolve.


> We may never see a 4.0 because of the scar tissue, but the language continues to evolve.

They should do the opposite really. If it hurts, do it more often and get better at it. A perfect time would be when Python gets some nice JIT performance improvements which everyone will probably like.


Linux: let's bump the major version just because

Python: for the love of God [1] don't touch the version

I wonder if the scar tissue will ever heal and we'll see a Python 4 in two decades.

1: https://www.youtube.com/watch?v=asUyK6JWt9U


K8s: the major version will never change, so instead we’ll introduce breaking changes with minor versions.


Probably not before a Perl 6


I recently replaced mine and ruled out a bunch of others based on just two rules:

- the zero must have a mark - the base of the lower case L must go to the right and not the left, for better distinction from the number one


Has functions, static types, a tree sitter grammar, an lsp client, and lots of implementations. Seems to me to be the most mature of the many new programmable configuration languages.


Excellent work. And it seems maintained. Documentation is somewhat behind the implementation, but not too much. Looks like its going to the right direction... reminding that adding features are easier than removing them.

Wonder ;) how hard it would be to bootstrap the language?..


> how hard it would be to bootstrap the language?..

I would think this is impossible, since this language is designed to be non-turing complete and forbids arbitrary side effects. You would always need a container language to make anything happen


The C language also requires some assembly, or rather machine code, if you're starting strictly from scratch.

Ok, not bootstrap in a sense of creating a sublanguage which allows to write the rest. I'm curious about how to write Dhall in C. Dhall doesn't look like a large language, right?


Private equity owned businesses are run in an even more predatory manner, not for next quarter's profits but just to extract every dime of equity as fees and services for their parent or as loan principal that can never be paid back.

And then venture-backed companies are ticking time bombs that abruptly close shop when they run out of money or are acquired, or at best themselves turn into the publicly traded companies you loathe.

"Good" companies are mostly just a consumer-friendly stage of the investment lifecycle.


I hear what you are saying about PE backed and VC backed companies. Not wrong.

But there is a whole another world of companies whose investors are not shooting for next quarter extraction. Their horizons are larger and their returns are calculated beyond FCF and gross margins.

These kinds of companies are the local businesses, trying to upstart and grow for a smaller set of towns around their geographic location.

Obviously not all companies can work with such small scale and such investors. In such cases, stick to non-public ones. At least their horizons are beyond the next quarter.


Can you elaborate why? As in, you got hit by an insured driver and so your insurance was able to bill them, whereas you didn't have collision coverage of your own?


> whereas you didn't have collision coverage of your own?

That's the majority of people who don't have a lien on their title. Liability insurance covers what you do, it doesn't cover what someone does to you. So having evidence of who caused the accident is important when everyone just has liability coverage.

In California, though, I really do recommend you have the "Uninsured and Underinsured Counterparty" option on your insurance. It's usually far cheaper than the alternatives and it just covers you with no effort on your part.


I wonder if copyleft projects can use this to find license violations and force the altered code into the open.


Maybe not the point, but https://github.com/fastfetch-cli/fastfetch is a good alternative to the first of these.


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: