eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

192
active users

#module

1 post1 participant0 posts today
adingbatponder<p><a href="https://fosstodon.org/tags/nixos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nixos</span></a> boot error <a href="https://fosstodon.org/tags/gnome" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gnome</span></a> pop-up using <a href="https://fosstodon.org/tags/zenity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>zenity</span></a> that warns of boot errors, unless the error has already been classified by you as harmless the last time it appeared in the pop-up,<br>see <a href="https://fosstodon.org/tags/flake" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>flake</span></a> <a href="https://fosstodon.org/tags/module" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>module</span></a> <a href="https://codeberg.org/adingbatponder/reticulum_nixos_flake/src/branch/main/modules/boot-error-notifications.nix" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">codeberg.org/adingbatponder/re</span><span class="invisible">ticulum_nixos_flake/src/branch/main/modules/boot-error-notifications.nix</span></a><br>The errors are manually checked with <a href="https://fosstodon.org/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> eg Claude before classifying them as irrelevant with a radio button &amp; hiding them henceforth from appearing. If no boot errors, no pop-up. This <a href="https://fosstodon.org/tags/nixosaiflakehack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nixosaiflakehack</span></a> was iteratively assisted by <a href="https://fosstodon.org/tags/claude" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>claude</span></a> . Spot bugs early when <a href="https://fosstodon.org/tags/tweakingflakes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tweakingflakes</span></a>.</p>
xoron :verified:<p><a href="https://infosec.exchange/tags/Decentralized" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Decentralized</span></a> <a href="https://infosec.exchange/tags/Module" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Module</span></a> <a href="https://infosec.exchange/tags/Federation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Federation</span></a> <a href="https://infosec.exchange/tags/Microfrontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microfrontend</span></a> <a href="https://infosec.exchange/tags/Architecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Architecture</span></a> </p><p>I'm working on a <a href="https://infosec.exchange/tags/webapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webapp</span></a> and I'm being <a href="https://infosec.exchange/tags/creative" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>creative</span></a> on the <a href="https://infosec.exchange/tags/approach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>approach</span></a>. It might be considered <a href="https://infosec.exchange/tags/overcomplicated" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>overcomplicated</span></a> (because it is), but I'm just trying something out. It's entirely possible this approach won't work <a href="https://infosec.exchange/tags/longterm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>longterm</span></a>. I see it as there is <a href="https://infosec.exchange/tags/onewaytofindout" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>onewaytofindout</span></a>. I don't recommend this approach. Just sharing what I'm trying/#investigating.</p><p>How it will be <a href="https://infosec.exchange/tags/architected" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>architected</span></a>: [<a href="https://positive-intentions.com/blog/decentralised-architecture](https://positive-intentions.com/blog/decentralised-architecture)" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">positive-intentions.com/blog/d</span><span class="invisible">ecentralised-architecture](https://positive-intentions.com/blog/decentralised-architecture)</span></a><br>Some <a href="https://infosec.exchange/tags/benefits" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>benefits</span></a> of the <a href="https://infosec.exchange/tags/approach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>approach</span></a>: [<a href="https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure](https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure)" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">positive-intentions.com/blog/s</span><span class="invisible">tatics-as-a-chat-app-infrastructure](https://positive-intentions.com/blog/statics-as-a-chat-app-infrastructure)</span></a></p><p>I find that <a href="https://infosec.exchange/tags/modulefederation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>modulefederation</span></a> and <a href="https://infosec.exchange/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>microfrontends</span></a> to generally be <a href="https://infosec.exchange/tags/discouraged" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>discouraged</span></a> when I see posts, but I think it works for me in my <a href="https://infosec.exchange/tags/approach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>approach</span></a>. I'm <a href="https://infosec.exchange/tags/optimistic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>optimistic</span></a> about the approach and the <a href="https://infosec.exchange/tags/benefits" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>benefits</span></a> and so I wanted to <a href="https://infosec.exchange/tags/share" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>share</span></a> details.</p><p>When I serve the <a href="https://infosec.exchange/tags/federatedmodules" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>federatedmodules</span></a>, I can also host the <a href="https://infosec.exchange/tags/storybook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>storybook</span></a> statics so I think this could be a good way to <a href="https://infosec.exchange/tags/document" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>document</span></a> the modules in <a href="https://infosec.exchange/tags/isolation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>isolation</span></a>.</p><p><a href="https://infosec.exchange/tags/Cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cryptography</span></a> modules - <a href="https://cryptography.positive-intentions.com/?path=%2Fdocs%2Fcryptography-introduction--docs" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">cryptography.positive-intentio</span><span class="invisible">ns.com/?path=%2Fdocs%2Fcryptography-introduction--docs</span></a></p><p><a href="https://infosec.exchange/tags/P2P" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P2P</span></a> framework - <a href="https://p2p.positive-intentions.com/?path=%2Fdocs%2Fe2e-tests-connectionstatus--docs" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">p2p.positive-intentions.com/?p</span><span class="invisible">ath=%2Fdocs%2Fe2e-tests-connectionstatus--docs</span></a></p><p>This way, I can create <a href="https://infosec.exchange/tags/microfrontends" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>microfrontends</span></a> that consume these <a href="https://infosec.exchange/tags/modules" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>modules</span></a>. I can then <a href="https://infosec.exchange/tags/share" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>share</span></a> the <a href="https://infosec.exchange/tags/functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>functionality</span></a> between <a href="https://infosec.exchange/tags/apps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>apps</span></a>. The following apps are using a different codebase from each other (there is a <a href="https://infosec.exchange/tags/distinction" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>distinction</span></a> between these apps in <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> and <a href="https://infosec.exchange/tags/closesource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>closesource</span></a>). Sharing those <a href="https://infosec.exchange/tags/dependencies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dependencies</span></a> could help make it easier to roll out <a href="https://infosec.exchange/tags/updates" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>updates</span></a> to <a href="https://infosec.exchange/tags/coremechanics" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>coremechanics</span></a>.</p><p><a href="https://infosec.exchange/tags/P2P" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P2P</span></a> chat - [<a href="https://chat.positive-intentions.com/](https://chat.positive-intentions.com/)" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">chat.positive-intentions.com/]</span><span class="invisible">(https://chat.positive-intentions.com/)</span></a><br><a href="https://infosec.exchange/tags/P2P" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P2P</span></a> file transfer - [<a href="https://file.positive-intentions.com/](https://file.positive-intentions.com/)" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">file.positive-intentions.com/]</span><span class="invisible">(https://file.positive-intentions.com/)</span></a></p><p>The <a href="https://infosec.exchange/tags/functionality" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>functionality</span></a> also works when I create an <a href="https://infosec.exchange/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Android</span></a> build with <a href="https://infosec.exchange/tags/Tauri" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tauri</span></a>. This could also lead to it being easier to create <a href="https://infosec.exchange/tags/newapps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>newapps</span></a> that could use the <a href="https://infosec.exchange/tags/modules" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>modules</span></a> created.</p><p>I'm sure there will be some distinct <a href="https://infosec.exchange/tags/test" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>test</span></a>/#maintenance <a href="https://infosec.exchange/tags/overhead" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>overhead</span></a>, but depending on how it's <a href="https://infosec.exchange/tags/architected" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>architected</span></a> I think it could work and make it easier to <a href="https://infosec.exchange/tags/improve" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>improve</span></a> on the current <a href="https://infosec.exchange/tags/implementation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>implementation</span></a>.</p><p>Everything about the <a href="https://infosec.exchange/tags/project" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>project</span></a> is far from finished. It could be seen as this is a <a href="https://infosec.exchange/tags/complicated" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>complicated</span></a> way to do what <a href="https://infosec.exchange/tags/npm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>npm</span></a> does, but I think this <a href="https://infosec.exchange/tags/approach" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>approach</span></a> allows for greater <a href="https://infosec.exchange/tags/flexibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>flexibility</span></a> by being able to <a href="https://infosec.exchange/tags/separate" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>separate</span></a> <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> and <a href="https://infosec.exchange/tags/closesource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>closesource</span></a> code for the <a href="https://infosec.exchange/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>web</span></a>. (Of course as <a href="https://infosec.exchange/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>javascript</span></a>, it will always be "source code available". Especially in the age of <a href="https://infosec.exchange/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a>, I'm sure it's possible to <a href="https://infosec.exchange/tags/reverseengineer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reverseengineer</span></a> it like never before.)</p><p>(mastodon might not be the place for something like this, so let me know if you dont like this kind of content. i typically post on reddit and would like to shift it more towards mastodon. i also use lemmy, but mastodon has a better reach.)</p>

As you can see in the screen cap the project has grown beyond just a one-man show

It is vital to understand that the project would not have been scaled in this manner & at this logarithmic rate, had it not been for important partners, who due to the power of the FediVerse, were quickly introduced to the project

Did not only gave words of interest they actually contributed with giving server space to boxyBSD.

Reed the Alt text voor more information

An insightful article was written by @gyptazy
If this is of your interest, and you take the time to read, analyze between the lines what has been said, you will learn a lot from this

If you are passionate about Proxmox like I am, you will love to read these kind of posts, because they've been systematically, logically and relatively simply formulated, so that it's digestible for the end user of proxmox all the way up to the diehard programmer who hacks in Proxmox code

A creepy tidbit from Fever Swamp, a swampcrawl module by Luke Gearing:

"These spirits of lost children are desperate for a light to lead them home. Their shadowy forms clamber through the trees, their large, blank faces staring greedily from above. Once the time is right, they reach down, snatching any candles, lanterns and oil before hurriedly fleeing. They can be pacified with sweet treats. They will not try to fight."

Just released Node Pebble version 5.1.1

• Updated to Pebble version 2.7.0.

• Now also supports macOS and arm64 (because Pebble itself does).

codeberg.org/small-tech/node-p

Node Pebble is a Node.js wrapper for Let’s Encrypt’s¹ Pebble² that:

• Downloads the correct Pebble binary for your platform.

• Launches and manages a single Pebble process.

• Returns a reference to the same process on future calls (safe to include in multiple unit tests where order of tests is undetermined)

• Automatically patches Node.js’s TLS module to accept Pebble server’s test certificate as well as its dynamically-generated root and intermediary CA certificates.

¹ letsencrypt.org

² “A miniature version of Boulder, Pebble is a small RFC 8555 ACME test server not suited for a production certificate authority.” github.com/letsencrypt/pebble

Codeberg.orgnode-pebbleA Node.js wrapper for Let’s Encrypt’s Pebble (a small RFC 8555 ACME test server not suited for a production certificate authority)
#LetsEncrypt#TLS#SSL

Physically-Based Hydrologic Modeling Using GRASS GIS - r.topmodel [tutorial]
--
workshop.isnew.info/omu-2024-r <-- link to technical resource / workshop / tutorial
--
“This workshop will introduce r.topmodel (Cho 2000), the GRASS GIS module for a physically-based hydrologic model called TOPMODEL (Beven 1984)..."
#GIS #spatial #mapping #water #hydrology #Hydrologic #model #Modeling #GRASS #GRASSGIS #topmodel #workshop #tutorial #onlinelearning #TopographyModel #catchments #R #SAGA #module #ISPSO #particleswarmoptimization #algorithm #continuingeducation

#AndroidAppRain at apt.izzysoft.de/fdroid today brings you 10 updated and 1 added apps:

* Mindful Attention Awareness Scale: Find out how mindful you are on a scale of 1 to 6. 🛡️

RB status: 343 apps (28.3%)

At apt.izzysoft.de/magisk today 1 #Magisk #module was added, and 2 updated:

* Audio HD Enhancer: Improve audio output to 320Kbs systemless for both Internal Speakers & Bluetooth

Status there: 120 modules

Enjoy your #free #Android #apps with the #IzzyOnDroid repo :awesome:

IzzyOnDroid App RepoIzzyOnDroid F-Droid RepositoryThis is a repository of apps to be used with your F-Droid client. Applications in this repository are official binaries built by the original application developers, taken from their resp. repositories (mostly Github, GitLab, Codeberg). Updates for the apps are usually fetched daily, and you can expect daily index updates.

Eisenbahn macht Spaß!

In der Mittelschule in Wolkersdorf im Weinviertel gibt es sogar ein Fach "Modelleisenbahn"... wo die Schülerinnen und Schüler anhand des Baues von #Modellbahn #Module mit unterschiedlichster Technik in Berührung kommen.
Holzbearbeitung, Klebstoffe, Elektrik, Löten, Elektronik, Farben, Pläne zeichnen, Karton schneiden, usw. usf.

Jeder baut sein eigenes Modul, ganz ohne Vorgabe, oder mehrere gemeinsam. Am Ende werden dann die einzelnen Module zu einer großen Anlage zusammengeschraubt und das Ganze ist weit mehr als nur die Summe der Teile.

youtube.com/watch?v=XVRJcZeKy7…

Und der Verein, bei dem ich Mitglied bin, die #SMBG smbg.at/ unterstützt diese Schule auch dabei. z.B. unter anderem mit Schmalspur-Modulen wenn die Anlage aufgebaut wird.

Eine richtig coole Sache. Würd ich mir für die Schule meines Kindes auch wünschen.