I prefer the Fediverse to BlueSky, because it solves your three problems.
I choose to see every post on my (small country) instance, so if there is an echo chamber, it's an instance-shaped one. Which I like - I see the range of views prevalent in my small country. "Elite" posters depend on posting good content and are rewarded only by other people boosting their posts.
I tend to use Mastodon which makes finding a post's popularity a click away, and so emphasises posting for interest instead of outrage. This may also be an artifact of living in a small country that expects more civilised discourse from it's citizens.
Having no algorithm definitely makes the Fediverse more "boring" - I had to persevere after moving from Twitter. But I soon realised this was due to the lack of outrage, and that that was what I wanted, and what I was seeing was far more "real". Big fan now, and it's made my social media consumption a lot healthier.
All of them are optional and can be disable at the instance-wide level, in addition to some of them having account level opt outs.
They also are still generally bound to an instance's own horizon: there's no global "trending feed" (and it would be really hard to create one), these optional "algorithmic" tools still differ from instance to instance based on what that instance follows and its trading relationship to its neighbors.
His (compelling) evidence for that assertion is that printers still jam after 40 years. For humans, writing something on a piece of paper is absolutely trivial, and if something goes wrong, grabbing a new piece of paper or a pen is also trivial. Computers _can_ now write on paper tolerably fast and well, but they absolutely can't handle even simple failure modes. And the real world is _massively_ failure-prone, in contrast to the digital domain.
Think about Tesla's pivot to "AI robots". My guess is that they'll get to something that can very slowly pick up a dropped sock and put it in the washing basket. But that it will fall over occasionally on the stairs, wrecking your kid's photos and the vase standing at the bottom, and dinging the wall. It might do a passable job of picking up the shards of pottery, but gluing the picture frames together, plastering the wall and repainting it... well maybe in in Elon's chemical dreams.
I like to think about it this way: why do printers need me to give it more paper? Why do I need to go buy paper from the store? These at the most trivial real-world things a human can do but I can’t imagine any robot doing that for a very long time.
Forget self-driving cars, how about a printer I don’t have to unjam or fill with paper?
But I doubt that kind of thing will happen in my lifetime.
This article (and holiday spare time) made me update and check zed again. I really liked it when I tried it a few months ago, but it failed miserably when doing work on remote code. It would hang, and I couldn't find any diagnostics to debug it's fairly complex remote agent to find out what went wrong.
But now it works fine! Remote work is noticeably snappier than via mounting the remote server as a drive, and remote git seems to work nicely. A very nice Christmas present - thanks, Zed!
Your "About" links seem not to work. In my case I was interested in where data is hosted, and the only information I see (from your HN post) is that you are from Paris. Does this mean EU hosting (which is good)?
Yes, sorry — I’ve focused more on the actual logic of the dashboard rather than the landing page, which still lacks polish.
Regarding the data, all your files are stored on Backblaze B2 servers (EU-central), with their data centers located in Amsterdam, Netherlands.
I hope I’ve answered your question correctly.
This will kill open source. Anything of value will be derived and re-derived and re-re-derived by bad players until no-one knows which package or library to trust.
The fatal flaw of the open internet is that bad players can exploit with impunity. It happened with email, it happened with websites, it happened with search, and now it's happening with code. Greedy people spoil good things.
Copyright was the base protection layer. Not in the "I own it" sense, but in the "you can't take it and run with it" sense.
With the current weakening of it, it opens the door to abuses that we don't have the proper tools to deal with now. Perhaps new ones will emerge, but we'll have to see.
Until now, people have had the leverage/cost asymmetry in their favor where they could easily differentiate and make rational choices.
AI has tipped that nuanced balance in a way that is both destructive, and unsustainable. Just like any other fraud or ponzi.
Cost/loss constraint function now favors the unskilled, blind, destructive individual running an LLM who spits on all those that act with good faith. Quite twisted.
Or use the API to program in anything you want. We use Google Sheets for our accounting system, loading data via bank APIs and a cron-driven python script. We used to use Xero, but it couldn't handle the different tax regimes we operate in.
That looks like a great usecase. Would you be able to write about the architecture. A lot of us would love to be able to do things like this in Sheets, I'm personally trying to integrate a forecast estimate into Sheets
I own my company so have no fear of losing my job - indeed I'd love to offload all the development I do, so I have no resentment against AI.
But I also really care about the quality of our code, and so far my experiments with AI have been disappointing. The empirical results described in this article ring true to me.
AI definitely has some utility, just as the last "game changer" - blockchain - does. But both technologies have been massively oversold, and there will be many, many tears before bedtime.
reply