This post is written on https://normals.me/ and delivered to !fediverse@lemmy.world over #ActivityPub, so if you are reading it the basic plumbing works. Now let me explain what is this.
Normals is a forum with communities, threads, and questions with an accepted answer. It is a single instance, not software you can host, and the core is closed for anti-abuse reasons. The federation module will be published separately with implementation notes (FEP-67ff).
What federates today Every community is a Group actor following the Lemmy model (FEP-1b12). Follow @selfhosted@normals.me or any other community from Lemmy, PieFed, Mbin or Mastodon.
Posts and comments go both ways. Replies from your instance appear in the thread on Normals, replies from Normals go back to the origin.
Remote content is labelled with its origin, links back to it, and is never copied. Media loads from the source.
Signed fetches, so it works with instances that require authorized fetch. NodeInfo 2.1 is up.
Policies, in case they matter to you, it has no ads, and no paid reach, and of course no AI training on posts. AI crawlers blocked by default, public mod log with reasons, and no automated removals. Numbers at https://normals.me/transparency so please take a look.
If something from your instance shows up wrong here, or something from here shows up wrong on yours, reply with the URL and I’ll fix it. Andy Piper mentioned NodeBB uses the same group model, if anyone runs a NodeBB instance I’d like to test against it, if possible.
I hope we all have fun. Cheers!
Why does your comment smell of elitism?
Yeah, it would be better if the code was FOSS. But at least it was released, the author seems to know the important parts of AP integration and is asking for constructive feedback. This is one million times better than developers who keep their purely organic, 100% fair trade software projects in a virtual shelf for fear of being criticized.
The code was not released though, unless I missed that part of the post
Is it elitism to call out vibe coding now? What a world.
Not to mention that their understanding of what tailwind is seems patchy at best, despite claiming that they have 15 years of experience.
The elitism is in thinking that using AI for some parts of the application (the frontend) nullifies the whole project.
It does if they’re minimizing and lying about it
I very much doubt the AI use is confined to the frontend. But I don’t see why the frontend is fine to vibe code while other stuff is not?
Using AI as a tool is fine. It can be very useful for programming. But “vibe coding” is using it to an extreme degree where the AI is producing almost the whole thing, with a very small amount of guidance or design from the user. That’s what I would object to. Such a thing has very little value, anyone can vibe code such a thing.
We can only be sure if/when they open the backend code.
Many reasons:
Most of that is fair except
That I definitely disagree with. UI and UX is important.
Still doesn’t make that vibe coded frontend worth anything.
It is important, but worrying about UX instead of shipping is the easiest way to avoid shipping. If you don’t agree, just check Craigslist, ebay and many other profitable companies with complete outdated frontends.