NRW.social

0 Beiträge0 Beteiligte0 Beiträge heute

Kevin Karhan :verified:<a href="https://social.vivaldi.net/@ajsadauskas" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ajsadauskas</a> <a href="https://infosec.exchange/@JessTheUnstill" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@JessTheUnstill</a> also <a href="https://infosec.space/tags/BlackBerry" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BlackBerry</a>'s <a href="https://infosec.space/tags/PlayBook" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PlayBook</a> <a href="https://infosec.space/tags/Tablet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tablet</a> <a href="https://www.youtube.com/watch?v=lYmHId9kJP4" rel="nofollow noopener noreferrer" target="_blank">was released</a> as a accessory screen for their Phones, which gave it "<a href="https://infosec.space/tags/WiiU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WiiU</a>-Effect" in terms of marketing.<ul><li>Plus <a href="https://infosec.space/tags/RIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RIM</a> relying hard on business clients and their proprietary applianced mail systems and having big carriers upsell to business people made them look outdated & quite literally out of touch once <a href="https://infosec.space/tags/iPhone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iPhone</a> went mainstream.</li></ul>I mean, the hardware was never their problem and <a href="https://infosec.space/tags/SMS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SMS</a>-Typists swear by their <a href="https://infosec.space/tags/BlackberryCurve" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BlackberryCurve</a>'s <a href="https://infosec.space/tags/keyboard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#keyboard</a> but BlackBerry's <a href="https://infosec.space/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> - just like <a href="https://infosec.space/tags/SymbianOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SymbianOS</a>'s - was just hideous to the point that devs like <a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fuchsiii</a> didn't even want to try making <a href="https://infosec.space/tags/Apps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apps</a> for those devices.<ul><li>Unlike <a href="https://infosec.space/tags/Mozilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mozilla</a> fucking up <a href="https://infosec.space/tags/FirefoxOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FirefoxOS</a> by refusing to sell devices to <a href="https://infosec.space/tags/developers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#developers</a>, by the time RIM & <a href="https://infosec.space/tags/Nokia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nokia</a> came from their high horses, their market shares had been squeezed into mere "rounding errors" by <a href="https://infosec.space/tags/iOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iOS</a> and <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> as it was way cheaper and easier to get <a href="https://infosec.space/tags/Apps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apps</a> developed, tested, sold, bought and use them than on their devices. </li></ul><a href="https://infosec.space/tags/Sony" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Sony</a> even released some <a href="https://infosec.space/tags/Symbian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Symbian</a> <a href="https://infosec.space/tags/S60" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#S60</a> devices but since they didn't have the same signing keys, one couldn't even <a href="https://infosec.space/tags/sideload" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sideload</a> apps (not to mention they didn't had the <a href="https://infosec.space/tags/OviStore" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OviStore</a> on those either!)...

Dr. Brian CallahanA new <a href="https://bsd.network/tags/blog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#blog</a> post appears!I built a native GCC 14.2.0 for Mac OS X 10.4 Tiger PowerPC.<a href="https://briancallahan.net/blog/20250329.html" rel="nofollow noopener noreferrer" target="_blank">https://briancallahan.net/blog/20250329.html</a><a href="https://bsd.network/tags/macos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macos</a> <a href="https://bsd.network/tags/macosx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macosx</a> <a href="https://bsd.network/tags/tiger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tiger</a> <a href="https://bsd.network/tags/powerpc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#powerpc</a> <a href="https://bsd.network/tags/power" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#power</a> <a href="https://bsd.network/tags/unix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unix</a> <a href="https://bsd.network/tags/bsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bsd</a> <a href="https://bsd.network/tags/freebsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freebsd</a> <a href="https://bsd.network/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openbsd</a> <a href="https://bsd.network/tags/netbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#netbsd</a> <a href="https://bsd.network/tags/dragonflybsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dragonflybsd</a> <a href="https://bsd.network/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://bsd.network/tags/solaris" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#solaris</a> <a href="https://bsd.network/tags/illumos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#illumos</a> <a href="https://bsd.network/tags/gcc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gcc</a> <a href="https://bsd.network/tags/llvm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#llvm</a> <a href="https://bsd.network/tags/clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clang</a> <a href="https://bsd.network/tags/compiler" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#compiler</a> <a href="https://bsd.network/tags/compilers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#compilers</a> <a href="https://bsd.network/tags/assembler" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#assembler</a> <a href="https://bsd.network/tags/linker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linker</a> <a href="https://bsd.network/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> <a href="https://bsd.network/tags/freesoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freesoftware</a> <a href="https://bsd.network/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a> <a href="https://bsd.network/tags/gnu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gnu</a>

Linaro LimitedLinaro’s Toolchain team is one of the leading contributors to <a href="https://mastodon.social/tags/Arm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Arm</a> support in <a href="https://mastodon.social/tags/GNU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNU</a> <a href="https://mastodon.social/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> projects. In this blog we look at a year's worth of Linaro's CI results for the <a href="https://mastodon.social/tags/GDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GDB</a> testsuite: <a href="https://ow.ly/n7KT50V3xJH" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ow.ly/n7KT50V3xJH</a>

Kevin Karhan :verified:<a href="https://infosec.exchange/@ryanc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ryanc</a> add the file used to store it into <code>.gitignore</code> is propably not an option?Maybe you can setup a build script that merges that <code>secrets.list</code> into a final build file and exclude that as well?I mean, I did such seperation and build scripting in some cases a while ago...<a href="https://infosec.space/tags/git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#git</a> <a href="https://infosec.space/tags/ESP8266" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ESP8266</a> <a href="https://infosec.space/tags/Secrets" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Secrets</a> <a href="https://infosec.space/tags/GitSecrets" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitSecrets</a> <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InfoSec</a> <a href="https://infosec.space/tags/Firmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Firmware</a> <a href="https://infosec.space/tags/Compiling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Compiling</a> <a href="https://infosec.space/tags/Toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Toolchain</a> <a href="https://infosec.space/tags/gitignore" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitignore</a>

Ben RosengartLike all Apple internships, this is paying work.In 30 years of IT work, I’ve seen fads come and go. There are a few areas that are absolutely evergreen, and an ornament to any resume. Linkers/loaders is one of these, so I’d strongly encourage any qualified early-career software dev to take a look at this.If you’re from an underrepresented background and you want me to go over your resume with you, I’ll be happy to do it. <a href="https://tilde.zone/tags/FediHire" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediHire</a> <a href="https://tilde.zone/tags/ToolChain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ToolChain</a> <a href="https://tilde.zone/tags/SoftwareEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareEngineering</a> <a href="https://sfba.social/@DarGoul/113289784472286550" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://sfba.social/@DarGoul/113289784472286550</a>

Kevin Karhan :verified:<a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dalias</a> personally I think that <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://infosec.space/tags/Kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kernel</a> needs to prioritize what it wants.<a href="https://infosec.space/tags/AFAICT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AFAICT</a> Linux always prioritized clean, lean & human-readable <a href="https://infosec.space/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> code over features, efficiency and sometimes even security.<a href="https://infosec.space/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> being turned into an integral part would extremely complicate the <a href="https://infosec.space/tags/build" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#build</a> process and add a shitload of <a href="https://infosec.space/tags/dependencies" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dependencies</a> to build <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@OS1337</a> or any other <a href="https://infosec.space/tags/minimal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#minimal</a> / <a href="https://infosec.space/tags/embedded" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#embedded</a> OS that it would be a net negative by just making the whole <a href="https://infosec.space/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> bigger, <a href="https://infosec.space/@kkarhan/113056809739446456" rel="nofollow noopener noreferrer" target="_blank">bulkier, more complex and convoluted</a>.

Kevin Karhan :verified:<a href="https://linuxrocks.online/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BrodieOnLinux</a> <a href="https://fosstodon.org/@that_leaflet" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@that_leaflet</a> <a href="https://aus.social/@AuntyRed" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@AuntyRed</a> <a href="https://infosec.exchange/@SecureOwl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@SecureOwl</a> if this ain't some <a href="https://infosec.space/tags/StateSponsored" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#StateSponsored</a> <a href="https://infosec.space/tags/SupplyChainAttack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SupplyChainAttack</a> it was at least so methodical that it's definitely some sort of specific attack against a specific target...I mean, I've seen weird <a href="https://infosec.space/tags/3Dchess" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#3Dchess</a> in <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ITsec</a> so I'd not be surprised if this was just some <a href="https://infosec.space/tags/1337hax0r" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#1337hax0r</a> wanting to take revenge on an employer/client who still owed them pay...I mean, that whole <a href="https://infosec.space/tags/xz" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xz</a> <a href="https://infosec.space/tags/backdoor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backdoor</a> has serious <a href="https://infosec.space/tags/nocom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nocom</a> vibes:<a href="https://www.youtube.com/watch?v=elqAh3GWRpA&t=79s" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.youtube.com/watch?v=elqAh3GWRpA&t=79s</a><a href="https://infosec.space/tags/TLDW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TLDW</a>: people literally gaslit an admin with specific packet flooding into filing a specific bug report so a specific fix would be implemented that would get a <a href="https://infosec.space/tags/backdoor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backdoor</a> implemented in <a href="https://infosec.space/tags/Spigot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Spigot</a>, a popular <a href="https://infosec.space/tags/Minecraft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Minecraft</a> <a href="https://infosec.space/tags/Server" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Server</a> <a href="https://infosec.space/tags/Toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Toolchain</a>...

Kevin Karhan :verified:<a href="https://infosec.space/@topher" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@topher</a> build a fully-reproduceable & minimalist <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> from scratch that is completely auditable wothin a reasonable timespan.Like <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@OS1337</a> ...You won't get that <a href="https://infosec.space/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> run under <a href="https://infosec.space/tags/Windows2000" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Windows2000</a> nor would you be able to download it with <a href="https://infosec.space/tags/Netscape" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Netscape</a> these days...But feel free to proove me wrong and build OS/1337 on that config...<a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OS1337</a>

Leibniz Supercomputing CentreWir starten mit Terminen in die Woche, für die Sie sich noch anmelden sollten. • <a href="https://mastodon.social/@FAU" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@FAU</a> Erlangen-Nürnberg und LRZ trainieren ab morgen Paralleles Programmieren von Supercomputern: <a href="https://indico.scc.kit.edu/event/3893/timetable/#all" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://indico.scc.kit.edu/event/3893/timetable/#all</a> • Fürs nachhaltiges <a href="https://mastodon.social/tags/programmieren" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programmieren</a> präsentiert REGALE_EU eine <a href="https://mastodon.social/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a>: <a href="https://regale-project.eu/?p=546" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://regale-project.eu/?p=546</a> • Am 1. März startet in Tutzing der Workshop mit der <a href="https://suma-ev.social/@osf" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@osf</a> zur "Orientierung in der digitalen Welt": <a href="https://www.ev-akademie-tutzing.de/veranstaltung/orientierung-in-der-digitalen-welt/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.ev-akademie-tutzing.de/veranstaltung/orientierung-in-der-digitalen-welt/</a><a href="https://mastodon.social/tags/freesoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freesoftware</a>, <a href="https://mastodon.social/tags/openscience" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openscience</a>, <a href="https://mastodon.social/tags/hpc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hpc</a>, <a href="https://mastodon.social/tags/discoverLRZ" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#discoverLRZ</a>, <a href="https://mastodon.social/@HPC_Guru" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@HPC_Guru</a> , <a href="https://mast.hpc.social/@whpc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@whpc</a>

Joachim (he/him, white)Teil des <a href="https://literatur.social/tags/Kunstprojekt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kunstprojekt</a> ist auch, das Entstehen zu dokumentieren und die <a href="https://literatur.social/tags/ToolChain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ToolChain</a> / <a href="https://literatur.social/tags/Werkzeuge" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Werkzeuge</a> zu dokumentieren. Durchaus mit dem Gedanken, es anderen (oder mir) einfach zu machen, weitere Durchläufe zu machen. Next steps: meine Gedanken gehen viel in Richtung <a href="https://literatur.social/tags/Ausstellung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ausstellung</a> . Bilder hab ich ja schon. 2 erwähnen <a href="https://literatur.social/tags/B%C3%BCcher" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bücher</a>, die hab ich auch.Für den Text zum Bild hab ich mir überlegt, dass ich jeweils eine <a href="https://literatur.social/tags/Bildbeschreibung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bildbeschreibung</a> machen kann, die den <a href="https://literatur.social/tags/Text" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Text</a> dann natürlich auch wieder enthält. <a href="https://literatur.social/tags/TextForm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TextForm</a>

GNU/Linux.chOpen Toolchain FoundationOpen-Source Ecosystem für besseres Engineering. <a href="https://social.anoxinon.de/tags/Engineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Engineering</a> <a href="https://social.anoxinon.de/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> <a href="https://social.anoxinon.de/tags/Hardware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Hardware</a> <a href="https://social.anoxinon.de/tags/Entwicklung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Entwicklung</a> <a href="https://social.anoxinon.de/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a><a href="https://gnulinux.ch/open-toolchain-foundation" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gnulinux.ch/open-toolchain-foundation</a>

Kevin Karhan :verified:<a href="https://social.pixie.town/@joepie91" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@joepie91</a> Don't forget: - <a href="https://mstdn.social/tags/Mumble" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mumble</a> for <a href="https://mstdn.social/tags/VoiceChats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VoiceChats</a>- <a href="https://mstdn.social/tags/Linphone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linphone</a> as <a href="https://mstdn.social/tags/SIP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SIP</a> / <a href="https://mstdn.social/tags/VoIP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VoIP</a> client- <a href="https://mstdn.social/tags/gparted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gparted</a> and <a href="https://mstdn.social/tags/ddrescue" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ddrescue</a> as well as <a href="https://mstdn.social/tags/testdik" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#testdik</a> & <a href="https://mstdn.social/tags/photorec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#photorec</a> for halding storage and recovering data.And ofc all the tools I need daily like <a href="https://mstdn.social/tags/SSH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSH</a> (<a href="https://mstdn.social/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSSH</a>), <a href="https://mstdn.social/tags/OpenVPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenVPN</a>, <a href="https://mstdn.social/tags/WireGuard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WireGuard</a>, <a href="https://mstdn.social/tags/IPsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPsec</a>, <a href="https://mstdn.social/tags/pfSense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pfSense</a>, <a href="https://mstdn.social/tags/OPNsense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OPNsense</a>, <a href="https://mstdn.social/tags/ipFire" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipFire</a>, <a href="https://mstdn.social/tags/LUKS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LUKS</a>/ <a href="https://mstdn.social/tags/dmcrypt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dmcrypt</a> and the whole <a href="https://mstdn.social/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> needed for OS/1337 like <a href="https://mstdn.social/tags/gcc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gcc</a>, <a href="https://mstdn.social/tags/musl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#musl</a>, <a href="https://mstdn.social/tags/toybox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toybox</a>, <a href="https://mstdn.social/tags/dropbear" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dropbear</a> and so on.<a href="https://mstdn.social/tags/OS1337" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OS1337</a> <a href="https://os1337.com" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://os1337.com</a>

Johannes BrakensiekThe simplicity of <a href="https://fosstodon.org/tags/UNIX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UNIX</a> has healed me from using <a href="https://fosstodon.org/tags/Java" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Java</a>. Looks like these days I'd rather write a <a href="https://fosstodon.org/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> tool (or even use <a href="https://fosstodon.org/tags/GObject" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GObject</a>) than use Java tools again. (I still like <a href="https://fosstodon.org/tags/Java" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Java</a> as a language, but the <a href="https://fosstodon.org/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> is incomprehensible.)

Ivan Enderlin 🦀An update on the GCC front end for Rust, <a href="https://rust-gcc.github.io/2023/04/24/gccrs-and-gcc13-release.html" rel="nofollow noopener noreferrer" target="_blank">https://rust-gcc.github.io/2023/04/24/gccrs-and-gcc13-release.html</a>.The focus for the next months will be about the `core` crate, along with the borrow checker. Goal is to pass the Rust 1.49 test suite. The ultimate goal is to get it merged in GCC 14, and later, to back port it to GCC 13.2.> This will enable users to easily start experimenting with the compiler for #![no_std] Rust programs and, hopefully, some embedded targets.<a href="https://fosstodon.org/tags/RustLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a> <a href="https://fosstodon.org/tags/gcc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gcc</a> <a href="https://fosstodon.org/tags/compiler" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#compiler</a> <a href="https://fosstodon.org/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a>

Linux MagazineLunar Lobster OS: <a href="https://ubuntu.social/@ubuntu" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ubuntu</a> 23.04 beta is available now <a href="https://www.linux-magazine.com/Online/News/Ubuntu-23.04-Beta-Now-Available-For-General-Testing" rel="nofollow noopener noreferrer" target="_blank">https://www.linux-magazine.com/Online/News/Ubuntu-23.04-Beta-Now-Available-For-General-Testing</a> <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://fosstodon.org/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ubuntu</a> <a href="https://fosstodon.org/tags/LunarLobster" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LunarLobster</a> <a href="https://fosstodon.org/tags/GNOME" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNOME</a> <a href="https://fosstodon.org/tags/kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kernel</a> <a href="https://fosstodon.org/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> <a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://fosstodon.org/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> <a href="https://fosstodon.org/tags/distro" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#distro</a>

Tech News WorldwideA CH32V003 Toolchain — If You Can Get One To Try It On <a href="https://hackaday.com/2023/03/02/a-ch32v003-toolchain-if-you-can-get-one-to-try-it-on/" rel="nofollow noopener noreferrer" target="_blank">https://hackaday.com/2023/03/02/a-ch32v003-toolchain-if-you-can-get-one-to-try-it-on/</a> <a href="https://aspiechattr.me/tags/Microcontrollers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Microcontrollers</a> <a href="https://aspiechattr.me/tags/microcontroller" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#microcontroller</a> <a href="https://aspiechattr.me/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> <a href="https://aspiechattr.me/tags/CH32V003" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CH32V003</a> <a href="https://aspiechattr.me/tags/WCH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WCH</a>

Kathy ReidEach year, I write a post on the <a href="https://aus.social/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> I'm using - the hardware, products and platforms that help me be productive and effective in whatever role I happen to be in. In this year's post, I cover <a href="https://aus.social/tags/NocoDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NocoDB</a> and <a href="https://aus.social/tags/Keychron" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Keychron</a>. <a href="https://blog.kathyreid.id.au/2022/11/13/state-of-my-toolchain-2022/" rel="nofollow noopener noreferrer" target="_blank">https://blog.kathyreid.id.au/2022/11/13/state-of-my-toolchain-2022/</a>

Aljoscha Rittner (beandev)Von <a href="https://social.tchncs.de/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Google</a> gibt es auch einen <a href="https://social.tchncs.de/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> Day am 1. September.Themen:Adopting and Interoperating with Rust in Large Codebases, Rust in the <a href="https://social.tchncs.de/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://social.tchncs.de/tags/Kernel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kernel</a>, Keeping your Rust <a href="https://social.tchncs.de/tags/Toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Toolchain</a> and Dependencies Up To Date and Running FastPorting a C++ Library to Rust.Home und Registrierung:<a href="https://opensourcelive.withgoogle.com/events/rust-day-2022" rel="nofollow noopener noreferrer" target="_blank">https://opensourcelive.withgoogle.com/events/rust-day-2022</a>

Joachim (he/him, white)Bonus-Punk: Ich hab den produktiven Umgang mit <a href="https://literatur.social/tags/Leanpub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Leanpub</a> nun schon mal durchgespielt.Falls ich mal ein "richtiges" Buch schreibe - oder sonnst irgendwas mit "Text veröffentlichen" machen will - kann ich auf die Erfahrung zurückgreifen. <a href="https://literatur.social/tags/JoachimKreativWeg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JoachimKreativWeg</a> <a href="https://literatur.social/tags/Tools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tools</a> <a href="https://literatur.social/tags/ToolChain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ToolChain</a> <a href="https://literatur.social/tags/Werkzeuge" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Werkzeuge</a> <a href="https://literatur.social/tags/LeanPublishing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LeanPublishing</a>3/3

Joachim (he/him, white)Noch weiter gedacht: wenn das Buch fertig ist, landet es per weiterem Knopfdruck im <a href="https://literatur.social/tags/AutorinnenBuchShop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AutorinnenBuchShop</a> ...und 5 Tage später beim lokalen Buchdrucker ( gibts das bzw. macht das Sinn? Was <a href="https://literatur.social/tags/BoD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BoD</a> zentral kann, kann vielleicht auch mein lokaler Copyshop dezentral? ).Bei mir sind das nur Ideen - aber wahrscheinlich machen das andere schon so oder ähnlich? <a href="https://literatur.social/tags/leanPublishing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#leanPublishing</a> <a href="https://literatur.social/tags/autorenleben" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autorenleben</a> Oder haben schon gelernt, dass das so doch nicht geht?<a href="https://literatur.social/tags/JoachimKreativWeg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#JoachimKreativWeg</a> <a href="https://literatur.social/tags/kreativeWertsch%C3%B6pfung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kreativeWertschöpfung</a> <a href="https://literatur.social/tags/toolchain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#toolchain</a> 2/2

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#toolchain