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" />
    <item>
      <title>Rewriting Our Database in Rust</title>
      <link>https://medium.com/airtable-eng/rewriting-our-database-in-rust-f64e37a482ef</link>
      <comments>https://lobste.rs/s/ekhniu/rewriting_our_database_rust</comments>

puf

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Lobsters Digest</title>
    <link>https://lobste.rs/</link>
    <description>Detailed summaries of top Lobsters articles and discussions</description>
    <item>
      <title>Mothlamp Problems</title>
      <link>https://unfoldingdiagrams.leaflet.pub/3mft6olldos26</link>
      <guid>https://lobste.rs/s/4pqmdx</guid>

puf

<?xml version='1.0' encoding='utf-8'?>
<rss version="2.0">
  <channel>
    <title>Lobsters Digest</title>
    <link>https://lobste.rs/</link>
    <description>Detailed summaries of Lobsters posts and comments.</description>
    <item><title>Linux Internals: How /proc/self/mem writes to unwritable memory</title><link>https://offlinemark.com/an-obscure-quirk-of-proc/</link><description>**The Gist:** The article "Linux Internals: How /proc/self/mem writes to unwritable memory" discusses an obscure but intentional quirk of the `/proc/*/mem` pseudofile. This file exhibits "punch through" semantics, allowing writes to succeed even on virtual memory marked as unwritable. This behavior is actively leveraged by projects such as the Julia JIT compiler and the rr debugger.&lt;br/&gt;
&lt;br/&gt;
**The Lobsters Take:** The provided content indicates there are 3 comments on the Lobsters discussion, but the actual comment text and discussion content are truncated and not visible. Therefore, no summary of the discussion or 

puf

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
	<channel>
		<title>Classic Albums Live Events</title>
		<description>Upcoming Classic Albums Live Concerts</description>
		<link>https://classicalbumslive.com/upcoming-shows/</link>
		<item>
			<title>Fleetwood Mac – Rumours - New Braunfels, TX (Mar 12th, 2026)</title>
			<description>Venue: , Ticket Link: </description>
			<link>https://classicalbumslive.com/upcoming-shows/</link>

puf

<?xml version='1.0' encoding='UTF-8'?>
<rss version="2.0">
  <channel>
    <title>Lobsters Digest</title>
    <link>https://lobste.rs/</link>
    <description>Summarized Lobsters feed</description>
    <item><title>Mozilla is working on a big Firefox redesign, here is what it looks like</title><link>https://www.neowin.net/news/mozilla-is-working-on-a-big-firefox-redesign-here-is-what-it-looks-like/</link><description>&lt;p&gt;&lt;strong&gt;The Gist:&lt;/strong&gt; The provided content was a Cloudflare security challenge page, preventing access to the actual article about the Mozilla Firefox redesign. Therefore, the content of the article could not be summarized.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;The Lobsters Take:&lt;/strong&gt; The discussion among Lobsters users is largely critical of the proposed Firefox redesign, focusing on concerns about wasted screen space and frequent, seemingly unbeneficial UI changes. Many users expressed frustration with the idea of "tabbar, sidebar and content as 3 separate top-leve

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()))