DAILY NEWS

Stay Ahead, Stay Informed – Every Day

Advertisement
YAML Formatter: a YAML Formatter tool that never sees your data



Most online YAML Formatter tools quietly send what you paste to a server. That’sfine until it isn’t — config blobs, tokens, and API responses are exactly thekind of thing you don’t want leaving your machine.

So YAML Formatter takes the opposite approach: it’s a single, self-contained pagethat runs entirely in your browser.

How it works

YAML Formatter is 100% in your browser — nothing is uploaded to a server. There’s no backend and no API call for the corefunction. You can verify it yourself:

Open the page.
Open DevTools → Network.
Use the tool.
Watch the Network tab stay empty.

The whole thing is one HTML file — View Source shows the JS that runseverything. It can’t leak your data because it never receives it.

What it does

Format and validate YAML — line/column error markers, 100% browser-side.

Fast, single-purpose, no signup
Works offline (save the page)
No tracking beyond a privacy-friendly analytics beacon

Why browser-side matters

The convenient online dev tools we paste into are an under-appreciatedsupply-chain risk. The fix isn’t a warning banner — it’s architecture: if thetool runs on your machine, there’s no breach to have. That’s the principlebehind the whole platotools.com set (JSON, JWT,hashing, encoding, regex, diff) — all client-side, all single-purpose.

Try it: https://yaml.platotools.com/

If you hit an edge case, I’d genuinely like the bug report.



Source link

Need your attention on my current project



I am currently working on a project. The concept is I select a github repository then it will automatically backs up that repository daily to a selected destination. Currently it only supports Google Drive and Dropbox for backup destination.

Current version is just a proof of concept. What I actually want to do is – it will take the repository and upload it to another git provider like gitlab etc. From then it will get only those commits that are not backed up and back up them. Basically automatic version controling.

It will help to have a back up copy of a project in other provider and easily migrate away from github to that git provider. I feel that we need this type of application now more than ever before. Slowly Github’s quality is going down, it is having outages frequently. Their uptime dropped to 90% from 99%. A lot of developers are moving away from it but few developers don’t want to. Perhaps they can’t for any reason. I myself don’t want to migrate away right now.

So I am thinking this concept can help those developers including me. What do you think. If you have any suggestions or queries let me know. Also you can check the project at nexrepo.qzz.io



Source link

TipTap + Yjs + Hocuspocus saves content, but other users only see updates after a page refresh



Hi everyone, I’m working on a Next.js app with a TipTap editor and I’m trying to enable real-time collaboration with Yjs and Hocuspocus.

Current setup:

Next.js app

TipTap editor using useEditor() and EditorContent

u/tiptap/extension-collaboration

u/tiptap/extension-collaboration-cursor

u/hocuspocus/provider on the frontend

u/hocuspocus/server running separately

Postgres stores normal TipTap JSON content

Postgres also stores a base64 Yjs state

Current behavior:

User A edits a document section.

The edit saves to the database correctly.

User B can see the update only after refreshing the page.

Without refreshing, User B’s editor does not update live.

What we tried:

Started the Hocuspocus server locally.

Added the Hocuspocus WebSocket URL to the frontend.

The editor can switch between normal TipTap mode and Yjs collaboration mode.

When collaboration mode is forced, the editor reads from Yjs state instead of the normal TipTap JSON content.

If the Yjs state is empty or stale, the document appears blank.

Main question:

What is the correct way to initialize a TipTap editor with existing saved TipTap JSON and then move it into Yjs/Hocuspocus collaboration mode without blanking the document?

Specific questions:

Should the existing TipTap JSON be converted into a Y.Doc before the editor is created?

In collaboration mode, should the TipTap editor content option be undefined?

What is the best practice for saving both Yjs state and normal TipTap JSON to a database?

How can I verify that two users are connected to the same Hocuspocus document and receiving updates live?

What are common reasons Hocuspocus/Yjs appears to save correctly but does not broadcast updates to other users?

Any guidance on the correct TipTap + Yjs + Hocuspocus flow would be appreciated.



Source link