skysight-inc/HackerNews huggingface dataset:
100% agreement with you here. You have one of the first logical arguments for any push back.

> figure out a solution that doesn't involve a single dev spending 20m USD a year just to maintain an app that people like

Absolutely, I was hoping that would happen when I saw the first Apollo thread(s) a few weeks ago. But Christian took this very personally, and he decided to take his toys and go home. reddit is not at all innocent here. They definitely had many missteps, but I think both sides did. And now that talks have broken down, reddit has little reason to come back to the table.

> Paid API is NOT going to make reddit profitable, especially at this price. It's funny to me that anyone actually even believes that. Hosting costs are not the problem, they have 2000 employees. For a site that can't get any feature fully functioning, has one of the worst ads in the business that noone wants to buy and is almost fully maintained by community for free, it's quite a lot of employees.

This is the heart of it for me personally. reddit has much bigger problems than just the API hosting/pricing. Drawing the line in the sand about the API and profitability doesnt make a lot of sense. Having 2000 employees (why?), hosting images and videos (value?), nfts (why?) and not following through on features is their actual downfall. They pivoted away from their core competency -- content aggregation and easy to use forums. I think they will survive though.
> Nah, the software world is moving away from providing options and configurability and has been for years. I have nothing against the standard scrollbar. I have everything against people like you who think it's the optimal solution for everybody, that a single solution could ever cover all needs, and we should never have any choice in it.

It's a good job I didn't say that then: I don't want it first party. If you want to _configure_ some extension or application to provide it, more power to you, but don't conflate my argument with something that I didn't say.

> No, adding useful features that can be enabled/disabled by preference. Apparently that's a bad thing to you. But thanks for pushing your short-sightedness as if it's the better solution.

Enabled by preference is fine for the most common use pattern, which is the current status quo. OSes already provide this.

You've stretched yourself to put a lot of words in my mouth. Go back and read what I said again, it will help you to avoid this level of misbehavior in the future.
I see that there's some skepticism about running WebAssembly in containers and how it constitutes a next-gen serverless solution. It's important to note that the use of WebAssembly here is not just about the runtime environment but also about the features it brings. WebAssembly binaries can start up significantly faster than traditional VMs or containers. They also have a strong isolation model and security sandbox that allows running multiple tenants in the same supervisor, which can lead to reduced costs and better utilization of resources
How-to and guides are an amazing way to do docs. I love the guides of Ruby on Rails. I rarely used the API documentation.

There is a great article talking about the 4 different types of documentation named the “document system”.

https://documentation.divio.com/
Hacker News is till great though the more I get exposed to the whole ActivityPub fediverse thing the more I wish it wasn't disconnected. I was in a read only HN app earlier today and wanted to post a comment to HN and instantly wished I could post a link into jerboa's search and have Hacker News available as a community.

The technology is getting there. The problem is the communities need time to grow. Star Trek fans have made a real effort. The bulk of reddit content is lowest common denominator shit and those consumers want everything handed to them fully formed. They aren't going to deal with server instability and submit bug reports and try and build new communities. They will delete Apollo and install the Reddit official app.
Blocked (or down) in Singapore apparently
They were done the minute mods broke their habit of moderating their subreddits. Some dedicated mods might come back, but it is really hard to return to a lost habits so the damage is done already.
I don't disagree with your line of thinking here.

But the big difference you're missing is that the kind of users that use old.reddit or third party apps are the power users.

Sure the Reddit app sits in its position in the app stores, but you ask most frequent users on reddit, and they all say they transitioned to a third party app.

So my point is i see things like the app as entry points for new users, and then those users either churn or end up transitioning to third party apps to make their experience better.
Except pretty much everyone thinks the CCS2 connector sucks compared to the Tesla connector. The EU ought to mandate the Tesla connector instead. We're still in early days, no need to worry about the tiny number of cars that have already shipped.
This sales pitch ignores cloudflare workers, which sound pretty similar to me, with both webassembly and key-value storage.

The distinguishing part of the articles option seems to be that webassembly functions are uploaded in an OCI container, which I don't think anyone else supports, and I don't think was designed with this use case in mind?
World's Largest Fusion Project Is In Big Trouble, New Documents Reveal
I won‘t use it anymore since the third party shut down and the inferior product they themselves provide. And the heart of the Apple community migrated to Mastoton and it doesn‘t feel ethically right to use it right now due to right wing people being catered there.
Show HN: Rootful containers can be more secure than rootless ones [Podman]
While rootless containers are suitable for user-managed containers on a system, for server-based container deployments, utilizing the "--userns=auto" option provides a more secure solution in Podman.

In Podman, when running containers in a non-privileged environment (rootless), they operate within the same user namespace, potentially leading to attacks between containers.

However, running the containers as root (rootful) with the "--userns auto" flag, Podman ensures isolation within distinct user namespaces, thereby enhancing security.
> It's as if the leadership was replaced with people who don't understand Reddit at all.

You're assuming they care, or ever cared. Maybe I'm getting too cynical, but I feel it's pretty clear Reddit leadership doesn't give a damn about Reddit the discussion/community site. For them, it's just a late-stage company that's been pumped and needs to be dumped. Where we see Reddit as its own unique artifact, they see it as just another money-producing asset, mature and ripe for harvest. They'll destroy it to cash out, as it has always been the plan - it's almost always the plan with startups in general - and find some other thing to repeat the process.
I remember times in 90's when we planned a software system in UML powered tool called Rational Rose. Oh my god its was clumsy and slow process. But yes, sequence diagrams are very useful tool.
Well Reddit hasn’t paid me shit for my contributions to the Reddit community. You’re right! By your correct reasoning, Reddit does not own their community, they’re just a consumer of it!

You seem to think that the users need Reddit more than that Reddit needs its users. I think it’s exactly the other way around.
Ah the memories! I used to run JLime and NetBSD on Jornada and MobilePro machines. While definitely not perfect, they were really nice and useable, and far more portable than contemporary laptops.

You could run X11, they had PCMCIA (for wifi and extra storage), and were just such a wonderful mix of weird and useful.

Glad to be reminded of those good times :)
My take on this kind of announcement structure, independent of language: the specifics (e.g. train/flight number) should be repeated at the beginning and end of the message. Why? Because people listen differently, also depending on the context and how many low-importance messages are being broadcast into the environment. When I'm at a station/airport and there is an announcement every two minutes of something mundane, e.g. which platform or gate is the next departure, I filter them all out, because I've already looked up that information on the screens or on my phone. Only when I subconsciously register something like 'cancelled' or 'changed platforms' or 'severe delay' do I start listening to hear if it is pertinent to me or not. That's when it's useful for the announcer to reiterate which service they are talking about, for those who only started paying attention half way through the message.
Oof, Winamp? Check this out: https://www.cvedetails.com/cve/CVE-2008-0065/
https://www.youtube.com/watch?v=gCWtkvDQ2ZI&

This video is a little old but I remember finding it really interesting and I think dives into it a bit.
Considering he was a major force driving the rewrite of Reddit from Lisp (the version that HN is based on currently) to Python, adding features like Markdown support (a language he helped create in 2002), Aaron defined major parts of the site that have persisted across multiple rewrites of Reddit's codebase.
> Like searching for logical replication, you find lots of information for pg_logical for older versions of postgres, but many of those parts are now baked into postgres, but with a different syntax, etc.

I tend to see this as duality of static/ephemeral. On one hand you have "vendors" treating software as rolling moving target - latest and greatest is all there is. On the other hand, there are community guides and tutorials that are out there and never retracted or amended.

Let's say I find an article that luckily states being written against older version of software. How do I know whether the information is still valid and applicable to a newer version? Well, if I am lucky and the vendor publishes growing changelog I have to read it and judge of the changes are applicable. Maybe I have to hunt down changelogs from all the interim versions just to see if anything important to me changed. Most probably I will find a very succinct summary of the change like "toll x was merged into tool y" or "updated interface of x". Now I have to try and find the discussion around the change in mailing lists (hopefully the team has not migrated to Discord).

Contrast this with hardware. Quite possibly I will find erratas and/or product change notices discussing the changes, maybe even application guides discussing how to apply changes. Unless there is an entirely new product line being released there is high change there will be rather detailed documentation on changes. Software is usually majorly lacking in this regard.

And no, versioned documentation is not the answer. Documentation gets updated not only technically, but also as discussed structurally. Once a piece of documentation gets moved to another section or even reworded I can no longer reasonably search for changes. Documentation of a changing, evolving thing is hard and interestingly this is where open source gets hit the most - there are almost no incentives for someone to write good documentation.
"we are lazy assholes who can't keep docs up to date, therefore docs are useless"

Is essentially the argument i see over and over again. And every time i start a new project and that project has docs or uml or whatever I appreciate it. Even if it is a bit out of date, it's way better than nothing.

In my opinion, every project should have a readme file with instructions for running the project locally, and ideally also a high level visual representation of the system.

It should be separated into sub systems/modules for separate functionality and each module could have it's own set of readme and high level visuals. In addition, modules should have small coupling points, typically interfaces and these should have documentation comments describing what they do, inputs, outputs etc. APIs should have something like a swagger doc.
I'm currently not considering Porkbun because you don 't have .fr, it would be a great option otherwise.
> Serverless apps are applications that are not written as software servers. “Server-less” code is code that responds to events (such as HTTP requests), but does not run as a daemon process listening on a socket. The networking part of serverless architectures is relegated to the infrastructure.

The networking part was always and always will be relagated to the infrastructure.
Really not sold to the all "serverless" fiasco.
SMEs or often peopling claiming to be SMEs. They'll outright lie often too - chatgpt eat your heart out
> If I didn't want a walled garden, I'd get an Android phone.

You also have a walled garden on Android, maybe with slighly lower walls but it's still pretty far from a truly open platform.

And that's there we see that the "it's the user choice" argument isn't working very well.

The open platforms are either very outdated devices (this HP, the N900...) or niche Android forks for tech people on a very limited amount of devices. Users never really had a choice in the first place.
Ocean discovered beneath Earth's crust, more water than on the surface
> Right, because people don't use credit cards for the additional protection, points or miles.

I actually don't know, because I'm not American. Over here just having a credit card draws questions about one's financial stability and responsibility.

At the end of the day it's really not your money you're spending like that. I mean - it's in the name even. You'll have to pay it back eventually.
Supermarkets are already doing that in Europe.
I think you're misinterpreting it. The full quote:

> Long Covid is looking less like a cloudy mass of speculation and shoulder-shrugging, and more like a problem that medical science can start to unravel, using the tools we already have:

> When a disease is too poorly defined, it follows that it is almost impossible to modify either the incidence of that disease or the distribution of its outcomes—that is, unless the treatment effect is so great, and the true target population so common in the assembled denominator, that any corresponding signal dilutions are offset. The present study suggests that, even with definitions as amorphous and heterogenous as those currently in use for diagnosing long COVID, there was to be found within this study population an ample cohort of individuals with syndromes similar enough that disease incidence could be modified, and metformin appeared to achieve that. Furthermore, the finding that long COVID is modifiable, although here showing prevention, offers hope. . .

This is definitely the first time I've seen anything showing a reliable effect on long Covid. Pretty much everything else I've seen has been a collective shoulder shrug of "well, we saw this, and it's maybe something about Covid, but we really don't know, and we have no idea how to treat this" and a bunch of people saying "it's just a possible side effect of an infection, we've been seeing this for decades". I have no idea how you can dismiss this as something we already know and that this isn't a positive and meaningful step forward.
Your reply seems to just be empty mockery unworthy of you. Do you dispute the figures I gave? Do you think the price given makes nuclear nonviable?
I believe so. and while it's not significantly worse, it is worse. thumbnails don't populate as consistently, the menu has me full screening a chat sometimes, it's just not as nice.
They did.

Say what one wants about Amazon or how they treat delivery drivers. My son told me of some experiences he's had--including having his car totaled on an icy river bridge at four in the morning--and Amazon was on top of it, empathetic, and did more than what was expected.
I'm also against building and compiling (I work with Python and Ruby on the backend) but there were good reasons to have those steps, at least in the past and probably still now. Short and very incomplete list, feel free to reply and add points:

* slow network, especially on mobile

* reduce the size of the download by minifying

* reduce the number of calls by bundling files in a single one

* Inconsistent JS and HTML feature support among browsers

* transpiling to a common older version of JS

* add polyfills to implement missing features

* add widgets to implement fucked up default implementations or widgets that are nearly impossible to standardize (date and time pickers might need tons of features and are projects on their own)
Well, GP seems to have edited their comment to flip its meaning 180°; earlier, IIRC (don't have a cached copy up) they were advocating for establishment of "safe spaces" of the kind that people who use term "safe spaces" establish - which for everyone else are more like digital equivalent of Lebensraum[0].

--

[0] - https://en.wikipedia.org/wiki/Lebensraum
So does Astro, many others. These are frameworks with no build steps that can be included from a CDN, though.
As far as I know this is false. They will track your web browsing habits through tracking scripts they use on web sites all over the web.
> We know because this exact strategy works just fine on Apple's other computer platform, the Mac

And Apple sells around 20 million Macs a year and 250 Million+ iPhones/iPads. It’s not exactly a mass market product with around 10% market share or less.

> The future on a long timescale may not be so nice. Were this to change, you don't easily have a say in alternative software.

In the long term your phone will be useless as a phone. Right now, the 2012 iPhone is the oldest phone that you can connect to modern cell phone networks as older protocols get turned off.

How much software do you really have that’s iOS only or that you would have to buy again if you wanted to choose Android.

But the answer is really not that hard. If you don’t like Apple’s “walled garden”, buy an Android like 85% of the world.
> The whole evil ISPs tampering with your data thing is just "reading too many Jon Brodkin articles on Ars".

No, it's personal experience. German Telekom did this crap by default until 2019, when they finally relented after criminal charges were filed [1], and they were far from the only one - NXDOMAIN abuse was shockingly common for a long time [2], including court-ordered censorship (e.g. The Pirate Bay, but governments liked to do DNS censorship against Twitter and other services too to squash resistance movements).

> What scares me a lot more is not just the actively malicious work shipped through Google's various platforms to target society's most vulnerable (usually seniors), but the sheer amount of money that has been dumped around every journalism outlet, activist org, and lobbyist to sell the narrative you just posted, all to protect a trillionaire corporation that watches your every move, and happily provides that information to all of the organizations you're worried about for free while convincing you it's doing you a favor.

In the end, you will always be fucked over by someone. At least if you're getting fucked by Google, you're not paying money for the privilege of getting fucked.

> In short, screw governments, but screw Google making it hard for me to filter out the traffic that lets them figure out whose visiting abortion clinics, which they are absolutely handing over to the authorities who ask about it.

Agree with you on that one, dragnet surveillance is plain bad. But the fix for that one is to get rid of DeSantis and his Evangelical ilk one way or the other, these laws have impact far beyond Google. It won't take long until some US state makes it a crime to travel to another US state for obtaining an abortion or for someone to transport a pregnant person to another US state for that purpose, so you'll see women essentially being trapped in these states (particularly those unable to afford their own car). Yes, that may be unconstitutional, but it will take years to reach the Supreme Court in the first place and it isn't guaranteed that the SC will block such outrageous crap.

[1] https://www.golem.de/news/t-online-navigationshilfe-telekom-...

[2] https://en.wikipedia.org/wiki/DNS_hijacking#Manipulation_by_...
wasn't it already nerfed?
It is. It's was a really neat idea in 2013. But it's a decade late. There's so much VR and AR headgear now that people expect better visuals.
I've just learned about lemmy today (so not exactly an expert...), but the fact this event is positioned as a negative seems like a harmful take.

This decision makes perfect sense. Beehaw requires applying to sign up with a sort of cover letter. If their community is more restrictive, they should only federate with similar-minded nodes.
As someone who pulled part-time scrum master duties in a seed stage startup, the problem is that engineers, even good ones, tend to be not-so-great communicators. Having someone to grease the wheels in stand ups and planning meetings decreases the time it takes for issues to surface. The other half of the job is cleaning the backlog and keeping the product owner from derailing development. It’s more about waste reduction than adding value.

Granted this was just my very limited experience, and we didn’t spend much time on estimating and standups consisted of a scheduled daily Slack ping instead of a meeting since we had major timezone offsets. People over process and all that.
I don’t get the AI angle. The data already exists in dumps. How does restricting access to the API stop that?

Sure, you don’t get access to new data but I doubt anybody cares about that given that there’s 15 years of existing data already. Especially if they kill all the interesting subs and turn Reddit into cat picture central.
What you say is true but unrelated to the concept of an iphone that allows individual users to root and or sideload.
I absolutely hate AWS with a passion but I might actually have to transfer my domains to them now
1. Try selling soap blocks and porno comics to an Amazon tribe or Australian native. Do they have "sell"? Do they need soap blocks? Do they need porno comics? It’s very narrow how you paint it.

2. Behavioral modernity in humans including the way we use language is thought to have emerged 70000-55000 years ago. You can’t go further back and expect to be understood.

3. Humans keep changing. The domestication of the dog ca. 28000-26000 years ago also changed the human brain by turning the dog into our wild senses.

4. Humans self-domesticated themselves the past 6000 years. Human brains show the same changes that domesticated cows have versus wild cattle species. Have you noticed that you can stay in a room with 50 strangers and not attack or sexually assault anyone? This same change led to the development of civilizations.

5. Your thought experiment only really makes sense if you go the furthest, say 12000 years back. Trade might not make sense to humans before.

6. Humans still keep changing.

7. Culture is more diverse than you think. By far more diverse. Just an example: Among human tribes across the globe 40% practice kissing, 60% never kiss. Your concepts will not translate.
I'm sure there are major methodological issues with what gets added to that list (I myself have seen some very questionable includes), but ultimately it's a trivial objection -- the overarching theme is very clear -- you cannot trust these products and services to exist for more than a year or two.

Also it's a sidebar, but astroturfing by company employees who stand to benefit from increased stock prices on comment boards such as this seems problematic.
Yes, by "storage" I mean storing the hydrogen for those rainy days.

Can I take this to mean you don't know where to find reliable numbers on this?
It seems likely to me that meaning-making, like consciousness, is on a sliding scale across all life. So trying to find the first homonids that "had it" seems futile.