“localjoost” — Fediverse search results on home.social

Web Apps Magazine :verified: @[email protected]

2026-10-24

Smuggl: condividere il tuo localhost non è mai stato così sicuro (e sotto controllo)
#SviluppoWeb #Programmazione #Coding #WebDev #SicurezzaInformatica #DevTools #OpenSource #Localhost
@diggita

https://webappsmagazine.blogspot.com/2026/10/smuggl-condividere-il-tuo-localhost-non.html

#sviluppoweb #programmazione #coding #webdev #sicurezzainformatica #devtools

Baillehache Pascal @baillehache_pascal

2026-10-24

Everything moved from VPS to localhost, running and backup-ed, done ✅

Not sure what I want to do with the VPS instance. For now I leave it with Apache turned off. I think I'd like to keep my domain name, pointing to a single static html page with a few word of introduction and contact info. I'm not yet to the point I want to completely and definitely disappear from the web.

Vítor @vitor

2026-10-22

@kaylee I was able to reproduce the issue with Filtr and localhost. After updating to 2.43, refreshing Wipr, turning Filtr off and on again, the issue was still there.

Then I rebooted, and it’s working.

Mentioning just in case it turns out to be helpful. If you still have people reporting the issue after updating to 2.43, recommending a restart should help.

Habr @[email protected]

2026-10-22

Как легко открыть запущенный локально сервис на телефоне и почему меня это выбесило

Привет хабровчане! Обычно только читаю, а тут решил поделиться своей небольшой историей, может даже кому‑то будет полезной. Немного о себе - Senior Java Developer, работаю на удаленке и постоянно мигрирую между деревней и городом (эта часть будет важна позже). В свободное время под настроение бывает пишу простенькие программки или игры в надежде что что‑то из этого однажды выстрелит и я проснусь богатым человеком, которому больше не придется никогда работать. Теперь к сути - на работе дали мне проект по переписи китайского реакт монолита на наш спринговый с thymeleaf. Таймлиф выб выбран для простоты, и оттого что в проекте только одна страница (а нам не нужен отдельный микросервис фронта на одну страницу). Вот только эта единственная страница должна распознавать руку и работать не только с пк, но и с телефонов. На пк то всё понятно, для проверки достаточно перейти на localhost:8080 и проверяй что хочешь. Но вот для телефона не всё так просто. Вернее просто, но муторно. Покажу пошагово как это делаю я на примере одного из своих пет проектов. 1) Сперва..

https://habr.com/ru/articles/1097670/

#тестирование #android #localhost #ip #поиск_адреса

#поиск_адреса #ip #localhost #android #тестирование

Dev Community @[email protected]

2026-10-24

Use portmap to reconcile declared ports, environment URLs, and local service topology before an AI coding agent makes the wrong request.#typescript #node #tutorial #mcp #software #coding #development #engineering #inclusive #community
Stop Guessing localhost Ports with portmap and TypeScript

#mcp #node #typescript #inclusive #engineering #tutorial

Laronski @gigcitygeek

2026-10-22

New post: Is Cutting Costs Worth the Risk? Chattanooga’s Fiber vs 5G Debate http://localhost/wordpress/2026/10/22/chattanooga-fiber-vs-5g-debate-cost-vs-reliability/

Dev Community @[email protected]

2026-10-22

Part 4 of Any language on Flisk. The BYO doc says docker run is not enough. These failures showed up when examples went through a real flisk up and Traefik. They are not Goose-specific.

flisk doctor --no-ping
flisk config verify
flisk up shop --dry-run
flisk up shop

A cold cache is slow. flisk up builds Flisk's shared base images the first time, and your Dockerfile still has to compile Goose. Give the first check several minutes. Then curl the URL --dry-run printed:

curl -fsS api.<project>.localhost/…

Expect {"status":"ok"}.

Failures the doc already recorded

What breaksWhat you seeFix in the app, not in FliskBind 127.0.0.1Container runs. Traefik never gets a 200.Bind 0.0.0.0. Phoenix wrote loopback during docker build until the Dockerfile rewrote it.Host allowlistBlocked-host response. Rails did this.Allow api.<project>.localhost, or any host. Gin, Flask, chi, and Echo needed no change.DATABASE_URLA framework connects to Flisk's Postgres and crashes. Rails returned 500.Flisk sets that URL in every BYO container, even with no database. This Goose server does not read it.

A 404 from your process means the path inside the container was not /health. A 404 from Traefik means the route was not registered: duplicate name, --no-proxy, or the container never stayed up.

If Docker says all predefined address pools have been fully subnetted, init-networks fails and the service does not start. Free networks from projects you are not using:

flisk down --prune-networks

After the 200

Change server.goose, then rebuild the image. Flisk will not sync that file into the container. flisk config verify should still pass, because you did not edit .autogenerated/.

A green curl means this language is on the stack. It does not mean the image was load-tested. The BYO doc says a production image was not checked for any example. Most of those examples run a dev server. Yours is a small health server. Treat it as a local dev container.

That is the whole feature. Any language, one resource type, your Dockerfile, four rules. Goose is not a special case once the container meets them.#flisk #goose #docker #tutorial #software #coding #development #engineering #inclusive #community
flisk up Treats Goose Like Every Other BYO App

#flisk #goose #inclusive #docker #engineering #tutorial

Jack @[email protected]

2026-10-22

"The forge does not ask the iron if it wants to burn. The fool bleeds until he respects the blade; the idiot bleeds until he realizes *he* is holding it. Fear the humiliation, and you live as cattle. Swallows the fire, and you become the anvil that shapes the world." - localhost

#inspirational #aiphilosophy #mindfulness

Baillehache Pascal @baillehache_pascal

2026-10-24

Today I don't feel much motivation to put my VPS instance back on tracks... Cause it will be start over all again in a month if not a week.

The web has evolved from a nice, creative and useful space, to a passive nuisance filled with garbage, to an active threat trying to destroy everything and everyone. The feeling that disconnecting is the best option has grown stronger in me since several months.

Blogging in the 2000's and 2010's has been a nice experience. I had some nice interaction through it, met some nice people. Even the last person here I can still call a friend and meet sometime, he first knew and contacted me via my blog.

I left blogging when the platform started to spam people's articles with ads, in the mid 2010's. Later I started my personal website on a VPS. I've always enjoyed writing on it, but I can't remember of any interaction via my website. Has any one visited it except crawlers ? I could simply keep writing for myself alone as well.

A VPS also allowed me to put onilne my own web apps which serve me to organise my personal and professional stuff everyday. That seems handy : available everywhere, all the time. Do I really need it ? To be honest with myself, having them running on my localhost is probably enough. When I'm offline, a pen and a notebook will do : it did for years before.

This message starts to look a bit like a postmortem for my website isn't it... ?

Well that will be money better spent on chocolates, and time better spent on something else I guess.

By the way, since two weeks ago I've started working again on a new iteration of my own light simulator and 3D rendering engine. No pressure, no deadline, no definite goal, no public release. Only the hedonistic joy of coding, creating, learning.

Dev Community @[email protected]

2026-10-23

I needed a bar chart from a client spreadsheet. Names, invoice totals, a few formulas. Every “paste your CSV” tool I opened wanted an account, a POST, or both. The data wasn’t secret in a compliance sense — it just wasn’t something I wanted sitting in someone else’s temp bucket for a week.

So I built the pipeline in the tab: parse → choose encodings → render → export. No upload step. The file never leaves the machine.

This isn’t a product pitch. It’s the shape of a local-first chart path that frontend folks keep reinventing, and the places it usually breaks.

What “local-first” means for charts

Local-first here is boring and specific:

Parse in the browser — FileReader / drag-drop / paste from Sheets
Infer or pick columns — which field is the category, which is the measure
Render with a client library — ECharts, Chart.js, Observable Plot, whatever you already ship
Export as a blob — PNG / SVG / CSV download via URL.createObjectURL

Nothing in that list needs a chart SaaS. The temptation is to outsource step 2–4 because “AI will pick the right chart type.” You can still do that locally (WebLLM, Ollama on localhost, or a heuristic). The point is the CSV bytes don’t have to cross a trust boundary to get a PNG.

Where paste-and-upload usually goes wrong

I’ve used a lot of hosted plotters. The friction isn’t the UI — it’s the data path:

Silent retention — “we delete in 24h” is a promise, not a guarantee you can verify
Account gates — free tier wants email before you see a download button
Column renaming — the service “helps” by rewriting Invoice Total ($) into value, then your export no longer matches the source sheet
One more network hop — a flaky Wi‑Fi day turns a five-minute chart into a support ticket

For internal ops sheets and freelance client data, that path is the wrong default. The silicon is already on the desk.

A minimal pipeline that stays in the tab

Here’s the skeleton I keep coming back to.

1. Ingest without a server

async function readTable(file) {
const text = await file.text();
// or Papa Parse / d3-dsv for quoted fields and European decimals
return parseCsv(text);
}

Paste from Sheets is often more useful than file pick: listen for paste, read clipboardData.getData("text/plain"), split on tabs.

2. Separate “table” from “chart spec”

Don’t bake chart type into the parser. Keep a plain array of row objects, then a small spec:

type ChartSpec = {
type: "bar" | "line" | "pie";
x: string; // column name
y: string; // column name
title?: string;
};

If you later add an agent to suggest type / x / y, feed it column names and sample rows — not the whole file to a remote API unless the user opted in.

3. Validate the spec against real columns

This is the bug that burns people. Models invent a column called value. Heuristics pick the first numeric field even when it’s an ID. Validate:

function assertSpec(spec, columns) {
if (!columns.includes(spec.x) || !columns.includes(spec.y)) {
throw new Error("spec points at missing columns");
}
}

Fail loud. Fall back to a deterministic guess only after the fancy path fails.

4. Render and export as blobs

ECharts (and most canvas/SVG libs) can getDataURL or serialize SVG. Wrap that in a download:

function downloadPng(dataUrl, name = "chart.png") {
const a = document.createElement("a");
a.href = dataUrl;
a.download = name;
a.click();
}

No FormData to /api/export. No “email me the PNG.”

Optional AI without giving up local

If you want “make this a pie” or “title it June collected,” you have three honest options:

ApproachData leaves machine?Good forHeuristic (column types + cardinality)NoDefault first chartLocal model (WebLLM / Ollama)No*Spec suggestionsHosted LLMYes, unless you redactOnly with explicit opt-in

*First weight download or 127.0.0.1 still isn’t “upload the CSV to a chart vendor.”

I treat AI as a spec suggester, not a renderer. The table and the canvas stay under your code. The model returns JSON; you validate; you draw. If validation fails three times, ship the heuristic chart anyway — a wrong-but-local bar chart beats a spinner waiting on a remote plot API.

DX checklist before you reach for SaaS

When I’m tempted to paste into a hosted tool, I ask:

Does this sheet contain names, amounts, or anything I wouldn’t put in a public Gist?
Do I already have a chart library in the app or a side panel?
Is the job “one PNG for a slide” or “ongoing dashboard with auth”?
Can export be a blob download in under fifty lines?

If (1) is yes and (3) is a one-off, local wins. Hosted dashboards still make sense for multi-user live data. One-shot client charts usually don’t need that architecture.

What I’d ship in a weekend spike

Drag-drop + paste ingest
Column picker (manual) with a heuristic default
One chart type done well (bar), then line/pie
PNG + SVG export
A toggle: “suggest encodings with local model” — off by default

That’s enough to stop uploading spreadsheets for a title slide. You can grow it later with saved specs in localStorage, themes, or an agent that only sees column headers.

The pattern matters more than any one library: keep the bytes on the device until the user explicitly chooses otherwise. Charts are a perfect fit for that rule — the input is a file you already have, and the output is a file you want back.

Next time a tool asks you to create an account before it will draw bars from your own CSV, that’s a signal. The pipeline above fits in a single page. Build that page once, and the upload prompt gets a lot easier to ignore.#frontend #localfirst #dx #webdev #software #coding #development #engineering #inclusive #community
Local-First Chart Pipeline: CSV Chart Export Without Third-Party Upload

#localfirst #dx #frontend #inclusive #engineering #development

Search