cross-posted from: https://piefed.world/c/tech/p/1161559/sovereign-office-suite-euro-office-to-release-june-9

Hey folks! I know a while back there was a kerfuffle because syncthing-fork for Android went dark, and then a new person showed up and claimed everything was cool and they'd been privately given the keys or something, and people were concerned. I pinned my fdroid version to the at-that-time-current release until we got clarity.

Well, it's been a while and I just noticed I'm still on that old release. So... how'd it turn out? Do we like the new person yet? Is there a promising fork y'all are using? Or is the project dead? I'm sure I could just go look at the repo, but I'm also sure the repo would tell me "yeah, we're all cool" no matter what, so I'm curious what the community feelings are. Have there even been any useful new releases since then?

Thanks!

I bought an xbox360 years ago with a game stuck in it. I have since lost them but I enjoyed the game. It was large bulky man carrying a sword and possibly shield. I remember there was island type landscapes but I dont remember swimming or anything. Possibly there was dragons but I think I may be inventing that because of other games. It was old timey in terms of setting, castles, sand and stone. I dont remember magic.

En temps normal, la page d’accueil du site de Santé publique France (SPF) devrait être très largement consacrée à la vague de chaleur précoce qui touche la France depuis le 21 mai 2026. « Mais depuis deux mois, toutes nos campagnes de prévention sont bloquées, comme notre dispositif de prévention contre les fortes chaleur “Vivre avec la chaleur” », explique un représentant de l’intersyndicale de SPF sous couvert d’anonymat.

Pourtant, cet épidémiologiste, membre du collectif Santé publique en danger, promet que, en lien avec Météo France, « nous avions anticipé cette vague de chaleur, nous étions prêts ».

Le dispositif de prévention est habituellement déployé dès qu’un département passe en vigilance orange canicule. « On achète alors de l’espace publicitaire, on mobilise les réseaux sociaux pour diffuser des messages de manière localisée, des petites animations qui ciblent des populations qu’on choisit d’alerter : un sportif, un garagiste, une personne âgée, un jeune enfant », poursuit l’épidémiologiste.

Seulement, depuis le début de l’année, le budget réservé aux campagnes de prévention de SPF a baissé de 40 %. « Notre travail est empêché », estiment les agent·es* questionné·es par Mediapart. Critiqué par l’opposition pour cette impréparation, Sébastien Lecornu a tenu un conseil des ministres exceptionnel, jeudi 28 mai, censé arrêter « un plan de résilience » dont on ne sait rien – Matignon n’a pas donné suite à notre demande d’entretien.

« On ne fait pas de la prévention une semaine après », grince une agente de SPF. « Certes, ce ne sont pas des chaleurs extrêmes, mais l’événement est exceptionnel, car les corps ne sont pas encore habitués, les bons comportements n’ont pas encore été adoptés et la perception du risque n’est pas forcément juste », explique l’épidémiologiste déjà cité.

Depuis le 21 mai, cinq personnes se sont noyées en se baignant dans des fleuves ou des plans d’eau, deux autres lors de pratiques sportives – des décès « liés directement ou indirectement à la chaleur », a expliqué le 26 mai Maud Bregeon, porte-parole du gouvernement. Dans la nuit du jeudi 28 au vendredi 29 mai, un jeune couvreur de 19 ans est mort des suites d’une hyperthermie.

Et si les messages de santé publique face aux fortes chaleurs peuvent paraître évidents, c’est en réalité loin d’être le cas. « Des études montrent que la population n’a pas une bonne perception du risque, poursuit l’épidémiologiste. Les personnes âgées sont perçues comme les plus vulnérables. En réalité, tout le monde est vulnérable, selon les circonstances : un adulte en bonne santé n’est pas à l’abri d’un coup de chaleur, qui est une urgence médicale. »

Les bons gestes ne sont pas non plus les mêmes selon les lieux et les conditions de vie : dans une maison individuelle, à la campagne, il faut fermer les volets de 11 heures à 16 heures. Mais en ville, il faut attendre la tombée de la nuit, car dans les îlots de chaleur, la température peut monter jusqu’à 19 heures ou 20 heures.

« Ils ne comprennent pas ce que l’on fait »

Depuis plusieurs semaines, Santé publique France est sous la surveillance de l’Inspection générale des affaires sociales (Igas), missionnée par le premier ministre pour économiser 300 millions d’euros d’ici à 2027 grâce à une « refonte de la stratégie et des moyens de communication de l’État ». SPF est dans le viseur.

« Ce qui se passe avec cette canicule, c’est un très bon exemple des conséquences de ce projet de démantèlement de l’agence, qui n’est justifié que par des éléments de langage et par aucun fait étayé. Nous serions une de ces agences inutiles, dispendieuses. C’est ce que ne cesse de répéter l’extrême droite », assène une agente interrogée par Mediapart.

Et d’ajouter : « Sous prétexte d’efficience, on a bloqué quelque chose qui existe depuis dix ans, qui s’appuie sur des travaux scientifiques, qui fonctionne. Ils ne comprennent pas ce que l’on fait : ce n’est pas de la communication, mais de la promotion de la santé. Pour protéger la population, on cherche à faire évoluer les comportements, en s’appuyant sur des données scientifiques robustes. »

Au-delà de Santé publique France, d’autres agences sont elles aussi menacées : l’Ademe, l’Anses, l’Office français de la biodiversité, le Centre d’études et d’expertise sur les risques, l’environnement, la mobilité et l’aménagement (Cerema)… Une situation qui pousse les agent·es à s’organiser pour renforcer la mobilisation, déjà historique, au sein de SPF.

« La priorité, ça semble être de détruire ces agences qui ont pour mission de préparer la France au réchauffement climatique. C’est dramatique pour la santé publique. Cela fait dix ans qu’on le répète et qu’on propose des solutions, rarement mises en œuvre. On préfère aujourd’hui priver l’État de sa capacité à protéger la population », regrette l’épidémiologiste.

Caroline Coq-Chodorge

0.9 is out.

Quick context if this is your first time: Ideon is a self-hosted visual workspace, an infinite canvas where you drop blocks for your Git repos, notes, tasks, files, and now automation. Everything about a project in one place.

The last release post ended with "move from visibility to control." This is the start of that.

Webhook block: drop one on the canvas, it becomes a live HTTP endpoint. CI pipeline finishes, monitoring alert fires, form submits, POST to the URL and Ideon reacts. Configure what happens: set a block's visual state, change its color, create a Kanban task, prepend text to a note. Runs server-side, no open browser tab needed.

Cron block: same action set, triggered on a schedule instead of an event. Preset or custom cron expression.

LaTeX block: several people asked for it. Write $...$ or $$...$$, toggle preview, done. Turned out to look better on the canvas than I expected.

Proxy / Header Auth: probably the most relevant one for this crowd. Already running Ideon behind nginx mTLS, Traefik, or Authelia? You can now configure it to read user identity straight from the headers your proxy injects. No OAuth round-trip, no separate IdP. A few env vars, and all auth events still go to the audit log.

Still open source, still self-hosted only.

GitHub: https://github.com/3xpyth0n/ideon

Docs: https://www.theideon.com/docs

If you ever ran eMule or MLDonkey back in the day, this will feel familiar — but it's built from scratch in Rust on modern infrastructure.

rucio is a decentralized peer-to-peer file sharing app. No trackers, no central servers, no relay nodes for the actual data. Peers find each other and the files through a Kademlia DHT (plus mDNS on the local network), keyword search rides on Gossipsub, and bytes move directly between peers.

I started it partly out of nostalgia and partly because I wanted a P2P stack I actually understood end to end — discovery, transfer, NAT handling, the lot — instead of a black box. It grew into something I now use daily, so I'm putting it out there.

What it does today:

• Fully decentralized — Kademlia DHT over the internet, mDNS on the LAN, no infrastructure to run (though you can run a bootstrap node if you want one).
• Web control panel — manage shares, searches and downloads from the browser. It's served by the daemon itself (Leptos/WASM), no extra process.
• Command-line client — a scriptable rucio CLI for everything, locally or against a remote daemon.
• Magnet links — share any file with a single rucio:<hash> link, generated entirely offline if you like.
• Resumable downloads — interrupted transfers pick up where they left off after a restart.
• Directory sharing — point it at a folder and every file inside gets indexed, hashed and announced automatically.
• NAT-friendly — HighID/LowID-style handling so peers behind NAT can still download; publicly reachable nodes serve chunks to everyone.
• Single binary — the same rucio binary is the daemon (ruciod) and the CLI depending on how you invoke it.

The eMule/Kad bridge (the fun part): rucio can optionally talk to the eMule Kad2 network. That means you can search Kad and download ed2k:// links right alongside native rucio transfers. It's opt-in (a build feature), but it's there because a chunk of those old files are still out there and still moving.

Some screenshots:

Try it (container):

docker run -d --name rucio \
  -e RUCIOD_API_LISTEN=0.0.0.0:3003 \
  -e RUCIOD_UPNP=false \
  -v rucio-data:/var/lib/rucio \
  -p 4321:4321/tcp \
  -p 3003:3003/tcp \
  -p 4662:4662/tcp \
  -p 4672:4672/udp \
  ghcr.io/ogarcia/rucio:latest

Then open http://localhost:3003/. There are slimmer image flavors too — latest-headless (daemon only), latest-cli (standalone client), and latest-bootstrap (a DHT bootstrap node). Pre-built binaries for Linux and macOS (x86_64 + aarch64) are on the releases page as well.

Note: If you download the precompiled binary from releases, when you extract it, create a symbolic link from ruciod to rucio, and run ruciod for the daemon and rucio for the CLI.

Honest caveats (it's early):

• I work with AI, so I’m not going to lie to you—there’s some vibe coding involved. I review and go over what I’ve done, but I want to be honest. If you don’t like it, just skip this app.
• This is v0.1.0, pre-1.0 — expect breaking changes (DB schema, API, config) between releases. I'll happily break things to get them right.
• There is no built-in authentication. If you expose the daemon beyond your own machine, put it behind a reverse proxy with auth (the docs have an nginx + basic-auth example). Keep the API port private otherwise.
• It's the work of one person so far. Rough edges exist.

Links:

• Source: https://github.com/ogarcia/rucio
• Containers: ghcr.io/ogarcia/rucio
• License: GPL-3.0

Today's game is Halo 3: ODST. Me and my friends have been making a playthrough of this on Heroic recently. It's afforded me a bit of introspective since i believe this is my least played Halo game. On top of that since i go back through in Theater because it makes it easier too take screenshots without getting people's names in them, it allowed me to have some fun with taking photos. I personally am really fond of this one. I think if i could have though i'd have gotten the player model entirely in the red box and zoomed in more. Unfortunately there was a Lamp Post in the way.

ODST is interesting to me because it's got a very city feel that i don't feel like appears in any other game. Even the other game this feel appears in it's different. It also feels a lot more Military than something like reach to me. Which is ironic, as i feel like Reach is more military drama. I think it's the fact the game makes you wander the war torn streets alone (or with exact duplicates of yourself if you're playing Co-op).

While we're on the subject of this game though, i think one of my reasons for not coming back too it often is that I resent it a little for the Audio Logs. I'm mostly being dramatic but it really took a lot out of me collecting all of this in one sitting. The game really makes you work for them.

We started the Escort mission and after that everyone seemed kind of done, so i think we all took that as our cue too get off. It's funny to me because that's the second time escort missions killed a run of something for me in this month. The last time was a few weeks ago in twilight princess.

cross-posted from: https://piefed.world/c/tech/p/1160169/a-danish-pension-fund-has-blacklisted-spacex-calling-it-grossly-overvalued-with-catastro

AkademikerPension will not buy SpaceX shares at any price near the $1.8 trillion IPO target, saying the company cannot reasonably be worth more than $1 trillion and that Musk’s voting control makes it effectively uninvestable

cross-posted from: https://lemmy.world/post/47534332

I have spent a long time at Synology Photos, along with my family. We have tags and albums. Is there a good way to migrate? I'm even open to migrating manually (album by album) if I could trust the process.

Hi, so I have a little Proxmox box with two VMs: VM1 and VM2 which is a clone of VM1. I change the mac of VM2 to avoid conflict and I reset the machine ID of VM1. I then have a seperate pfSense machine machine that that acts as router, firewall and DHCP server. Proxmox is on the 192.168.20.1/24 domain. In the DHCP server, Proxmox get IP 192.168.20.8 explicitly assigned. All good to this point. I've set VMs on pfSense to get the 192.168.20.9X addresses assigned. VM1 gets 192.168.20.91 assigned, while VM2 should be getting 192.168.20.92.

But this is what actually happens:

• VM1 gets 192.168.20.106 assigned, despite telling pfSense to assign it 192.168.20.91. This happens even with VM2 shutdown. The DHCP Lease table is showing 91 up and running and does not list 106. Yet, the ARP table shows 106 assigned and no 91 assigned. This is even with me deleting the 106 entry from the ARP table several times and rebooting both the VM and the Proxmox server.

• The VM is definately getting 106 assigned as I can log into it with 106 IP but 91 doesn't respond (no route to host).

Is this something to do with the bridge configuration on Proxmox? Iv'e added a screenshot of what I see. It doesn't seem to be that complicated to setup a bridge?

I can't get my head around this so tips are welcome.

EDIT: I've just run 'sudo ip' on the VM and i see the ens18 interface with the MAC I assigned to it and the 106 IP assigned to this interface. There are then seven of 'vethXXX' interfaces. Not sure what these are. There are also four 'brXXXX' interfaces, one 'loXXXX' interface and one 'docker0' interface, the latter probably used by the docker subsystem running on the VM. I imagine the 'brXXXX' interfaces are the docker containers themselves (I think I have four running). But what are the 'vethXXXX' interfaces? Sounds like its something to do with "virtual interface". Why so many and what is creating these?