MurphyA/hacker-news huggingface dataset:
by ReinwatashiDev | 2025-08-18 14:29:00+00:00
Hey HN,

I’m excited to introduce Repurpose.cc, a lightweight web tool that helps creators turn existing content—like newsletters, podcasts, or blog posts—into10+ social media-ready posts in just a few seconds.

What it does:

Paste or import your long-form content (blog, newsletter, or podcast transcript)

Instantly generate multiple high-quality snippets optimized for social platforms

Choose from various post types: tweets, LinkedIn excerpts, Instagram captions, etc.

Minimal setup—no templates to fuss with, just quick, clean outputs

Why it matters:

Massive time-saver—no more manually chopping up content

Consistent voice across platforms—your brand stays coherent everywhere

Ideal for lean creators—especially solo bloggers, newsletter writers, and podcasters who want to expand their reach without investing hours

Refresh your library—giving old content a new life, effortlessly

Launch phase details:

Beta open now—free to try

Feedback loop onboard—I’m aiming to refine formats, tone matching, and platform variations

Roadmap: support for native image generation, hashtag suggestions, and scheduling

Would love to hear what resonates with the community—what types of content snippets you'd value most, and any quirks you’d want the platform to handle (like bullet vs. narrative styles, thread flows, or layouts).

[Link to Repurpose.cc] (with tracking-free UTM if preferred)

Thanks for checking it out—happy to answer questions, debug workflows, or brainstorm use cases.

— Rein Watashi
Show HN: Memori – Open-Source Memory Engine for AI Agents
by Arindam1729 | 2025-08-18 14:29:32+00:00
Hey HN! I'm Arindam, part of the team behind Memori (https://memori.gibsonai.com/).

Memori adds a stateful memory engine to AI agents, enabling them to stay consistent, recall past work, and improve over time. With Memori, agents don’t lose track of multi-step workflows, repeat tool calls, or forget user preferences. Instead, they build up human-like memory that makes them more reliable and efficient across sessions.

We’ve also put together demo apps (a personal diary assistant, a research agent, and a travel planner) so you can see memory in action.

Current LLMs are stateless — they forget everything between sessions. This leads to repetitive interactions, wasted tokens, and inconsistent results. When building AI agents, this problem gets even worse: without memory, they can’t recover from failures, coordinate across steps, or apply simple rules like “always write tests.”

We realized that for AI agents to work in production, they need memory. That’s why we built Memori.

Memori uses a multi-agent architecture to capture conversations, analyze them, and decide which memories to keep active. It supports three modes:

- Conscious Mode: short-term memory for recent, essential context. - Auto Mode: dynamic search across long-term memory. - Combined Mode: blends both for fast recall and deep retrieval.

Under the hood, Memori is SQL-first. You can use SQLite, PostgreSQL, or MySQL to store memory with built-in full-text search, versioning, and optimization. This makes it simple to deploy, production-ready, and extensible.

Memori is backed by GibsonAI’s database infrastructure, which supports:

- Instant provisioning - Autoscaling on demand - Database branching & versioning - Query optimization - Point of recovery

This means memory isn’t just stored, it’s reliable, efficient, and scales with real-world workloads.

We’ve open-sourced Memori under the Apache 2.0 license so anyone can build with it. You can check out the GitHub repo here: https://github.com/GibsonAI/memori, explore the docs, and join our community on Discord.

We’d love to hear your thoughts. Please dive into the code, try out the demos, and share feedback, your input will help shape where we take Memori from here.
by taylodl | 2025-08-18 14:29:37+00:00
The funny thing is, ARM is European tech - and it's the processor architecture behind most of the world's devices. Linux, also European, runs our network infrastructure and cloud servers. LibreOffice is another European innovation, and in my opinion, it's better than Word (though not quite as good as Excel). And let's not forget SAP, which powers much of the world's supply chain and enterprise resource planning systems. My point is European technology quietly powers the modern world in ways that are often overlooked. If there's any worry, it's that the US is too dependent on European tech.
by yawaramin | 2025-08-18 14:30:20+00:00
No, I am positive you are missing the point.

> no one would use its ridiculous link or image syntax.

And many don't, which is fine! But some do, if they remember the syntax. Markdown is tolerant of that, and ultimately if the file is rendered to HTML Markdown engines know to just turn raw URLs into hyperlinks.

> The reason you write with Markdown syntax is because you want to be able to format it

Maybe sometimes. Not always. That's the point. A lot of the time it's nice that most technical people who write docs in text files all agree on what headings, lists, emphasis etc. should look like in plain text so we don't have to constantly do a dance of negotiating what the markup is. And the bonus on top of that is we can also get a reasonable HTML page out of it.

> If you don’t know the rules well enough, your mental parse will be incorrect, and you’ll produce errors. Errors that won’t be detected by your computer. That’s the hazard with Markdown

I mean, 'hazard'. Kind of an over-the-top way to put it. It's a text file for documentation purposes, not a production system handling money or something. Nobody cares if the Markdown has a few syntactic errors. The point is to convey information to other humans in a reasonably efficient way.
by tomconnors | 2025-08-18 14:30:28+00:00
I recently used c.a.flow for a program that reads files from s3, massages the data a bit, and writes to a database. The code came out very easy to understand. The challenges were:

- getting back pressure right. You need to tune the buffers for the input chans correctly, which takes some thinking, and in my case, some blowing up in prd.

- flow monitor (the UI for debugging flows) can't handle large process states, which makes it pretty much useless for my program.

- understanding the flow as a whole (rather than specific processes, which are easy to understand in isolation). For example, answering questions like "why hasn't this process received a message for a while?" was tricky.
by jcgl | 2025-08-18 14:30:39+00:00
> this will not take off I'm afraid, because locking these unitfiles down is offloaded to the end-user

Maybe your point is that this isn't done by the vendor in practice. And I'm sure there's room for lots of improvement. However, one of the great things about how systemd units can be provided by the vendor and seamlessly tweaked by the administrator is that the vendor (i.e. packager and/or distro) can set these up easily.

There definitely are packages that ship with locked-down files. Tor and powerdns (pdns) are two off the top of my head.

→ Overall exposure level for pdns.service: 1.9 OK → Overall exposure level for tor.service: 7.1 MEDIUM
by mrcwinn | 2025-08-18 14:30:44+00:00
I think this analysis is directionally right but the supportive arguments are quite weak. Maybe the iPhone is the wrong form factor, but do we really doubt Apple's ability to create a new hardware device and tightly integrate software?

The deeper issue, in my view, is that Apple is violating its own philosophical belief, articulated by Steve Jobs himself: that Apple should always own the primary technology behind its products (i.e., multi-touch, click-wheel). This is central to Apple's "we need to make it ourselves" approach.

Camera lenses are commodities. AI models are foundational. Apple's own executive leadership likened models to the internet, and said, well surely we wouldn't try to build and own the internet! This misplaces AI as infrastructure when in fact it's foundational to building and serving useful applications.

They further see "chat" (and by extension) as an app, but I think it's more like a foundational user interface. And Apple's certainly always owned the user interface.

When Siri was first announced, there was excitement that voice might be the next paradigm shift in user interface. Partly because Siri is so bad for a decade now, and partly because people didn't feel like talking to their screens, Apple may have learned a very unhelpful lesson: that Siri is just a feature, not a user interface. In this age though, chat and voice are more than features, and yet Apple doesn't own this either.

Apple should not buy Perplexity. Perplexity is smoke and mirrors, and there's nothing defensible about its business. Apple cannot get the talent and the infrastructure to catch up on models.

So what then?

OpenAI is not for sale. Anthropic is likely not for sale, but even if it were, Apple wouldn't buy it: Anthropic is very risky to Apple's profit margin profile and Apple can't unlock Anthropic's bottleneck (capacity).

In fact, to Apple's advantage, why not let the VCs and competitors like Microsoft and Amazon and Google light their money on fire while this industry takes shape, provided you have an option in the end to sell a product to the consumer?

The best option, in my view, is Search Deal Redux: partner deeply with Google and Gemini. Google very obviously wants as much distribution as possible, and Apple has more hardware distribution than any company in history.

Partnership is the only path because, yes, Apple missed this one badly. There is one area where I agree with Tim Cook, though: being late doesn't guarantee you lose, even in AI.
by thiht | 2025-08-18 14:30:54+00:00
> I don’t see how either of those exhibits demonstrate your point.

Natural language is easy to do for a human and a hard computing problem.

Polish notation is extremely simple to implement, but relatively "hard" for a human, even knowing the rules and how to read it. See: `+ * - 15 6 / 20 4 ^ 2 3 - + 7 8 * 3 2`
by OrvalWintermute | 2025-08-18 14:30:57+00:00
> Amazon’s AWS is predicated on the idea of commoditized infrastructure at scale where price is the priority. But with AI, quality/performance is the priority.

cost is not the priority with AWS. To quote my collaborator, "I just scaled up to 600 PB for our event"

When I think AWS I think speed, scale-up, scale-out, capacity & dynamic flexibility are more key.

AWS is not the "cheapo commodity option", nor is Azure
by ngcc_hk | 2025-08-18 14:31:08+00:00
Is Intel lost the mobile? Or a better question has arm lost mobile … the key is today the most profitable part is not arm even it has the isa.

Intel lost the hardware fight. But it lost all along as the most profitable part is software or who control the ecosystem. Microsoft and Apple. Not Intel.

It is amd cannot beat nvidia but the ecosystem of Ai (but not game) is what the lost is.

Now what ecosystem apple and Amazon lost … can it get to avoid nvidia controlling their Ai ecosystem. I doubt very much.
by c-smile | 2025-08-18 14:31:09+00:00
Well, Highlight API ( https://developer.mozilla.org/en-US/docs/Web/API/Highlight ) should just work inside <textarea> too.

At least it works in my Sciter like this:

<style> textarea::mark(myHighlight) { background-color: yellow; color: red; } </style> <body> <textarea>Lorem ipsum dolor sit amet</textarea> </body> <script> // Select a range of text to highlight const range = document.createRange(); const textNode = document.querySelector('textarea').firstChild; range.setStart(textNode, 6); // Start at the 6th character range.setEnd(textNode, 11); // End at the 11th character // Highlight the range range.highlight("myHighlight") </script>

Ask your browser vendor to enable highlight API in <textarea> too :) so such tricks will not be required.
by OtherShrezzing | 2025-08-18 14:31:14+00:00
> AI unlocks what seems to be the future: dynamic, context-dependent generative UIs or something similar. Why couldn’t my watch and glasses be everything I need?

If you earnestly believed that dynamic generative UIs are the future, surely you'd be betting on Apple.. The company with fully integrated hardware already capable of cost effectively running near-frontier generative models on the end user hardware.
by mlnj | 2025-08-18 14:31:22+00:00
And that's exactly why I want to collaborate with folks who are striving towards the same direction in society.

There are numerous conversations that led to me losing respect for people because they see fascism as a completely valid step forward. I now make a conscious choice to support and lead folks that share similar political leanings because if I don't respect your sincere beliefs, I cannot support you in proliferating those beliefs in society.
by 6thbit | 2025-08-18 14:31:28+00:00
I feel the feature would be better aligned with the rest of nextdns if the message was “Avoid ID checkpoint”, which is more privacy focused and less confrontational than the current presentation.

But that’s when I thought this was a sort of blocklist of ID processors. If what you’re doing really is forcing the site to be served from a different geolocation then maybe just have that as a top level feature. “Use foreign DNS” or something, maybe allow configuring a list of domains I want to happen that on, or geographies I’m ok with connecting to.
by danielvaughn | 2025-08-18 14:31:46+00:00
The approach I've taken to "vibe coding" is to just write pseudo-code and then ask the LLM to translate. It's a very nice experience because I remain the driver, instead of sitting back and acting like the director of a movie. And I also don't have to worry about trivial language details.

Here's a prompt I'd make for fizz buzz, for instance. Notice the mixing of english, python, and rust. I just write what makes sense to me, and I have a very high degree of confidence that the LLM will produce what I want.

fn fizz_buzz(count): loop count and match i: % 3 => "fizz" % 5 => "buzz" both => "fizz buzz"
by TheTaytay | 2025-08-18 14:31:59+00:00
I don't understand the part where you said that you have a very good handle on it. I really want to believe that it's as simple and solvable as you say it is. or do you mean that it's easily solvable - it's just that no one has done it yet? (In which case I think you are Simonw are saying the same thing?)

You mentioned the boundary between GET/POST args in a web app and a SQL query...but we have a system that is (by nature) mingling all of the parameters and execution together. It would be as if everyone's web server had a first line of their handler function that said something like "params = eval(user_based_params)", and you couldn't remove it...
by GistNoesis | 2025-08-18 14:32:14+00:00
Some times it's useful to see the elemental transformations, but often striving for a higher level view makes understanding easier.

It's particularly true when you try to apply it to physics. Often where you are introduced to vector calculus for the first time, things like Maxwell's equation, or fluid mechanics.

In physics there are often additional constraints, like conserved quantities. Like you calculate a scalar the total energy of a system, call it the Hamiltonian, auto-differentiate it with respect of the degrees of freedom, and you got very complex vector equations.

But taking a step back you realise it's just a field of "objects" of a certain type and you are just locally comparing these "objects" to their neighbors. And the whole mess of vector calculus is reduced to in which direction, you rotate, stretch and project these objects. (As an example you can imagine a field of balls in various orientation, whose energy is defined by the difference of orientation between neighboring balls)

When you wrap around that the whole point of vector calculus (and why it was invented) is to describe a state as an integral (a sum of successive) of linear infinitesimal transformations, this make more sense. These "objects" being constrained and continuous, by moving in infinitesimal steps along the tangent space (and then reproject to satisfy the constraints (or exponentiating in a Clifford algebra to stay in the space) ).

All the infinitesimal transformations are "linear", and linear transformations are rotating, stretching, mirroring, projecting to various degrees.
by kevindamm | 2025-08-18 14:32:17+00:00
While bottom-up evaluation is the norm in datalog, it is not a requirement and there are datalog engines that evaluate top-down or all-at-once.

But I still agree with you about the capitalization. Some formats, like KIF, use a '?' prefix instead, and I've seen some HRF notations that mix the '?' prefix with non-KIF formatting (':-' operator and '.' terminator).
by twobitshifter | 2025-08-18 14:32:19+00:00
Apple is not focusing on AI with any real emphasis. The engineers asked for $50B to train a model and Apple instead did stock buybacks. The stock kept underperforming and so they touted apple intelligence and a revamped Siri, only for it to fall flat. Siri was underinvested in for many years and should be at least as good as Claude or ChatGPT. ‘They’re not investing in a chatbot’ is a huge miss by apple who had a chatbot on everyone’s devices and a headstart on the whole concept.
by DaiPlusPlus | 2025-08-18 14:32:34+00:00
Assuming the courts simplify Otter AI down to being a glorified call recording and transcribing tool (because the fact it's "AI" isn't really relevant here w.r.t. privacy/one/two-party-consent rules then doesn't the legal responsibility here lie with whichever person added Otter AI to group-calls without informing the other members?

----

EDIT: So the crux of the matter is whether-or-not having Otter AI automatically join meetings via their Slack/Zoom/etc integrations is by-itself legally wrong - or not:

> "In fact, if the meeting host is an Otter accountholder who has integrated their relevant Google Meet, Zoom, or Microsoft Teams accounts with Otter, an Otter Notetaker may join the meeting without obtaining the affirmative consent from any meeting participant, including the host," the lawsuit alleges. "What Otter has done is use its Otter Notetaker meeting assistant to record, transcribe, and utilize the contents of conversations without the Class members' informed consent."

I'm surprised the NPR article doesn't touch on the possible liability of whoever added Otter in the first place - surely the buck stops there?
by adrianmav | 2025-08-18 14:32:44+00:00
After 6 months listening to 2,500 beta users, Secria is officially open to everyone.

Email is still broken. Your address gets sold constantly. Tracking pixels follow you everywhere. Quantum computers are coming to crack today's encryption.

So we started building.

One-click alias rotation so you control who has your real address. Post-quantum encryption that survives future attacks. Code exchange verification so you know who's really emailing you. Zero data collection and zero-knowledge architecture, not even we can read your emails. And much more.

No ads scanning your messages. No tracking pixels. No selling your data.

Just email built by people who actually listen to users instead of advertisers.

This community shaped every feature. Your feedback drove our roadmap. Your requests became our priorities.

Sign up at secria.me

Thank you for being a part of Secria, loads more on our roadmap coming soon!
by LooseMarmoset | 2025-08-18 14:33:01+00:00
LASIK can absolutely correct astigmatism.

Source: Had LASIK in 1999. Severe myopia and astigmatism, corrected to 20/10 and 20/15 (right and left eye).

My night vision was definitely worse after the surgery, but improved over a year or two. I still get blurry when my eyes are dry and tired, but otherwise remain glasses-free at 50+.
by garbthetill | 2025-08-18 14:33:34+00:00
Yep, Apple is great at this. There have been times when random Android phones were ahead feature wise, but this doesn’t cause Apple to lose its customer base, even when Apple releases the same feature 2–4 years later. The same thing happened with smartwatches, Apple entered that industry late, yet the Apple Watch now dominates the market against well established players
by fzeroracer | 2025-08-18 14:33:39+00:00
Consider the following scenario: You're a developer in charge of implementing a new service. This service interfaces with one of your internal DBs containing valuable customer data. You decide to use a coding agent to make things go a little bit faster, after all your requests are not very complicated and it's bound to be fairly well known.

The agent decides to import a bunch of different packages. One of them is a utility package hallucinated by the LLM. Just one line being imported erroneously, and now someone can easily exfiltrate data from your internal DB and make it very expensive. And it all looks correct upfront.

You know what the nice thing is about actually writing code? We make inferences and reasoning for what we need to do. We make educated judgments about whether or not we need to use a utility package for what we're doing, and in the process of using said utility can deduce how it functions and why. We can verify that it's a valid, safe tool to use in production environments. And this reduces the total attack surface immensely; even if some things can slip through the odds of it occurring are drastically reduced.
by styanax | 2025-08-18 14:34:05+00:00
The readme clearly directs the reader to the F-Droid package, which are built on their buildservers and signed with their APK keys. This does not answer the security question directly, but it's the same model as say Debian repos. There are eyeballs on it by an independent third party packagers who use code scanners and manual review to detect malfeasance, and often have to tweak builds and code to get rid of unwanted things present in some upstreams.
by eythian | 2025-08-18 14:34:17+00:00
My feeling, without evidence, is that a lot of the hate is vocal people who don't like this thing that does stuff differently to what they're used to. I get the feeling, I still understand /etc/init.d and runlevel symlinks and /var/log better than systemd, but that's because I have many more years of experience interacting with it, breaking it, fixing it. Whenever I have to do stuff with systemd it's a bit annoying to have to go learn new stuff, but when I do I find it reasonably straightforward. Just different, and most likely better.
by Bender | 2025-08-18 14:34:21+00:00
You know your power will be cut, and you know it will be a certain amount of time, and you know roughly where you are in the schedule.

Knowing when the power will be cut will not help unless I am misunderstanding you. If the data-center loses power for even a minute the generators will all fire up and then every ATS will count-down and transfer in 30 seconds. Battery backup only lasts just long enough to do a quick return to service on a failed generator and even that is sketchy at best. A properly engineered data-center can run on reduced generator capacity.

Some data-centers are indeed on circuits deemed to be critical but I could see regulations changing this so that they are "business critical" vs. "life support critical" and some changes could be made at substations so that data-centers could participate in shedding. I think you are right that they will be thinking about this and adding to this probably filing preemptive lawsuits to protect their business. Such changes can violate SLA contracts businesses have with power companies and Texas is very pro-business so I can not compare it to California.
by gota | 2025-08-18 14:34:29+00:00
Just FYI, I stumbled upon this discussion the other day. This [1] is not the same source that was going around but states the same thing.

"STEM graduates, often hailed as the golden ticket to career success, are facing unemployment rates that might make you double-take. For instance, computer engineering majors are grappling with a 7.5% unemployment rate, while art history majors—yes, the ones often mocked for their “impractical” degrees—are sitting pretty at just 3%. What’s going on here?"

[1] https://capwolf.com/why-stem-grads-struggle-to-find-jobs-in-...