Tootfinder

Opt-in global Mastodon full text search. Join the index!

No exact results. Similar results found.
@june_thalia_michael@literatur.social
2025-07-15 06:50:35

#EroticMusings 7: Do you have a distinct style? Did you develop it intentionally? Do you want to change it?
I think that my choice of vocabulary, especially in the erotic passages, is quite unique. Also my tendency to start German sentences with "but" and my very own brand of gender neutral language, because German is everything but (unless you costumise it).
Some of …

@metacurity@infosec.exchange
2025-09-08 13:25:56

Check out today's Metacurity for the most critical infosec developments you might have missed over the weekend, including
--Chinese espionage campaign targeted House staffers ahead of trade talks,
--Ethical hackers uncover catastrophic flaws in restaurant chain's platforms,
--Salesloft Drift hack began last March,
--Customer data stolen in Wealthsimple breach,
--Trump to formally nominate Harman for NSA/Cybercom slot,
--Don't trust XChat's e…

@arXiv_mathOC_bot@mastoxiv.page
2025-07-10 09:09:01

Real-time Optimization of Transport Chains for Single Wagon Load Railway Transport
Carsten Moldenhauer, Philipp Germann, Cedric Heimhofer, Caroline Spieckermann, Andreas Andresen
arxiv.org/abs/2507.06621

@lysander07@sigmoid.social
2025-08-27 09:18:52

In case you didn't have the chance to visit our poster on NFDIcore 3.0: A Mid-Level BFO2020-Compliant Ontology for Sustainable Research Data Interoperability Across Consortia, you can find it here on Zenodo:
zenodo.org/records/16946279
Corresponding abstract:

This poster is presented at CoRDI 2025 in Aachen, Germany. 

The National Research Data Infrastructure (NFDI) initiative has led to the creation of consortia spanning all scientific disciplines in Germany. Each consortium develops customized research data infrastructures tailored to its domain-specific requirements. While addressing these individual needs, achieving interoperability remains an important objective of the NFDI, as it ensures a cohesive and sustainable approach to research data ma…
@arXiv_csRO_bot@mastoxiv.page
2025-09-03 14:12:23

Classification of Vision-Based Tactile Sensors: A Review
Haoran Li, Yijiong Lin, Chenghua Lu, Max Yang, Efi Psomopoulou, Nathan F Lepora
arxiv.org/abs/2509.02478

@metacurity@infosec.exchange
2025-07-18 14:01:36

Don't leave for the weekend until you've checked out today's Metacurity for the most critical infosec developments you should know, including
--Data on UK SAS forces and MI6 officers exposed in massive Afghan leak,
--Google sues BadBox 2.0 ops,
--Salt Typhoon continues telco targeting,
--Paradox.ai developer used password of 123456 for Fortune 500 customers,
--EU sanctions Russians for disinformation campaigns,
--Qantas gains order blocking rele…

@arXiv_csCV_bot@mastoxiv.page
2025-07-29 08:27:01

Pre- and Post-Treatment Glioma Segmentation with the Medical Imaging Segmentation Toolkit
Adrian Celaya, Tucker Netherton, Dawid Schellingerhout, Caroline Chung, Beatrice Riviere, David Fuentes
arxiv.org/abs/2507.19626

@jaygooby@mastodon.social
2025-08-15 17:07:14

Puts a "Deploy" button in Strapi so rather than webhooks triggering builds on every change, you can decide when to publish. Supports self-hosted Gitlab instances and pipeline variables.
Built from a fork-of-a-fork plus some retracted PRs.
All I really did was swear at `npm` until I figured out that I was missing a "prepare" step in package.json

@arXiv_csCR_bot@mastoxiv.page
2025-06-23 09:51:40

Emission Impossible: privacy-preserving carbon emissions claims
Jessica Man, Sadiq Jaffer, Patrick Ferris, Martin Kleppmann, Anil Madhavapeddy
arxiv.org/abs/2506.16347

@mgorny@social.treehouse.systems
2025-08-18 08:42:07

If you're writing a library, you should really avoid #CMake. CMake is designed to lock you in. As in, once you release a #FreeSoftware project using CMake, you can't switch to another build system with causing real trouble to your users. And if you support multiple build systems, as soon as you start supporting CMake, some of your users are going to start locking everyone else in.
That's because CMake uses a custom package discovery mechanism that's hardly compatible with anything else, and that is so complex that it's very hard to reimplement it with any other build system. So when others start relying on the CMake config files being installed (and they naturally will, since that's how CMake does things), you can't stop installing them without actually breaking stuff. And if you want to preserve them without actually using CMake, well, good luck with that.
And if CMake is one of the options you support, then some of your consumers will accidentally start relying on it anyway. And this will be much worse for everyone, because now their projects won't work for people who build your project with any other build system. Which in turn will force more projects to use CMake anyway. Which in turn will make more people rely on CMake being used…
Use #Meson as the build system, it's clean and not designed to lock you in. Use pkg-config for library data; it's simple and portable.
#OpenSource