puf

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>

<item>
  <title>RISC-V is sloooow</title>
  <link>https://lobste.rs/s/ta3jjk/risc_v_is_sloooow</link>
  <guid>ta3jjk</guid>
  <pubDate>Tue, 10 Mar 2026 14:49:53 -0500</pubDate>
  <description><![CDATA[**The Gist:** The author, an ARM developer, shares their experience working with the RISC-V port of Fedora Linux over three months. While they've successfully triaged bugs and sent 86 pull requests for Fedora packages, a significant challenge is the "sloooow" performance of current RISC-V hardware, leading to drastically longer build times compared to aarch64, i686, ppc64le, s390x, and x86_64 architectures. For instance, building the binutils package takes 143 minutes on RISC-V, versus 25-46 minutes on others. This slowness necessitates disabling Link Time Optimization (LTO) to conserve memory and reduce build times. Current RISC-V builders typically have 4 or 8 cores and 8-32GB RAM, with performance comparable to older Arm Cortex-A55 cores.

puf

<?xml version='1.0' encoding='utf-8'?>
<rss xmlns:ns0="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
    <title>Lobsters</title>
    <link>https://lobste.rs/</link>
    <ns0:link href="https://lobste.rs/rss" rel="self" />
    <description />
    <pubDate>Thu, 12 Mar 2026 01:48:59 -0500</pubDate>
    <ttl>120</ttl>
    <item>

puf

<?xml version='1.0' encoding='utf-8'?>
<rss version="2.0">
  <channel>
    <title>Lobsters</title>
    <link>https://lobste.rs/</link>
    <description />
    <pubDate>Sat, 11 Apr 2026 16:00:27 -0500</pubDate>
    <ttl>120</ttl>
    <lastBuildDate>Sun, 12 Apr 2026 13:18:27 GMT</lastBuildDate>
    <item>

puf

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Classic Albums Live Upcoming Events</title>
    <link>https://classicalbumslive.com/events/</link>
    <description>Upcoming Classic Albums Live events.</description>
    <lastBuildDate>Mon, 20 Apr 2026 12:00:00 +0000</lastBuildDate>
    <item>
      <title>Bon Jovi – Slippery When Wet - Brantford, Ontario (Apr 21st, 2026)</title>
      <description>Concert by Bon Jovi – Slippery When Wet in Brantford, Ontario on Apr 21st, 2026.</description>

puf

<?xml version='1.0' encoding='utf-8'?>
<rss version="2.0">
  <channel>
    <title>Lobsters</title>
    <link>https://lobste.rs/</link>
    <description />
    <pubDate>Fri, 10 Apr 2026 12:32:45 -0500</pubDate>
    <ttl>120</ttl>
    <lastBuildDate>Sat, 11 Apr 2026 05:25:29 GMT</lastBuildDate>
    <item><title>Put your SSH keys in your TPM chip</title><link>https://raymii.org/s/tutorials/Put_your_SSH_keys_in_your_TPM_chip.html</link><guid>https://lobste.rs/s/ggum7f</guid><author>raymii.org by raymii</author><pubDate>Fri, 10 Apr 2026 12:32:45 -0500</pubDate><comments>https://lobste.rs/s/ggum7f/put_your_ssh_keys_your_tpm_chip</comments><description>&lt;p&gt;&lt;strong&gt;The Gist:&lt;/strong&gt; This article details how to enhance SSH key security by storing them in a Trusted Platform Module (TPM) chip, presenting it as a more secure alternative to filesystem storage, akin to Hardware Security Modules (HSMs) but device-bound. It offers a practical guide covering TPM setup for SSH, including software installation

puf

<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Lobste.rs Digest</title><item><title>Test</title><description>Setup works!</description></item></channel></rss>

puf

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Lobste.rs Daily Digest</title>
    <link>https://lobste.rs/</link>
    <description>Daily curated links from Lobste.rs</description>
    <language>en-us</language>
    <lastBuildDate>Wed, 24 Dec 2025 14:05:56 +0000</lastBuildDate>
    <atom:link href="https://gist.githubusercontent.com/" rel="self" type="application/rss+xml"/>

puf

puf

// In Firebase it is often better to *react* to authentication state 
// changes, instead getting the current authentication state everywhere.
// To respond to auth state changes, use an auth state change listener 
// like this:
FirebaseAuth auth = FirebaseAuth.getInstance();
auth.addAuthStateListener(new FirebaseAuth.AuthStateListener() {
    @Override
    public void onAuthStateChanged(@NonNull FirebaseAuth firebaseAuth) {
        if (firebaseAuth.getCurrentUser() == null) {
            Log.i("firebase", "AuthState changed to null");

puf

// To detect when a write operation is rejected by your Realtime Database
// security rules, add a completion listener to the `setValue()` call and 
// throw the exception if the task failed.
val ref = FirebaseDatabase.getInstance().getReference()
ref.push()
    .setValue(ServerValue.TIMESTAMP)
    .addOnCompleteListener(new CompletionListener() {
      @Override
      public void onComplete(Task<Void> task) {
        Log.i("firebase", String.valueOf(task.isSuccessful()))