Voyager now has experimental Piefed support in the App Store and Play Store. F-droid rolling out soon. 🥳

Make sure your app is up to date (v2.37.0 or greater) and enjoy!

https://getvoyager.app/

P.S. Support is under active development and there are known and unknown issues. Please post any feedback or questions!

Background image credit

https://images.nasa.gov/details/hubble-observes-one-of-a-kind-star-nicknamed-nasty_17754652960_o

Astronomers using NASA’s Hubble Space Telescope have uncovered surprising new clues about a hefty, rapidly aging star whose behavior has never been seen before in our Milky Way galaxy. In fact, the star is so weird that astronomers have nicknamed it “Nasty 1,” a play on its catalog name of NaSt1. The star may represent a brief transitory stage in the evolution of extremely massive stars.

First discovered several decades ago, Nasty 1 was identified as a Wolf-Rayet star, a rapidly evolving star that is much more massive than our sun. The star loses its hydrogen-filled outer layers quickly, exposing its super-hot and extremely bright helium-burning core.

But Nasty 1 doesn’t look like a typical Wolf-Rayet star. The astronomers using Hubble had expected to see twin lobes of gas flowing from opposite sides of the star, perhaps similar to those emanating from the massive star Eta Carinae, which is a Wolf-Rayet candidate.

Instead, Hubble revealed a pancake-shaped disk of gas encircling the star. The vast disk is nearly 2 trillion miles wide, and may have formed from an unseen companion star that snacked on the outer envelope of the newly formed Wolf-Rayet. Based on current estimates, the nebula surrounding the stars is just a few thousand years old, and as close as 3,000 light-years from Earth.

  • Jerry on PieFed@feddit.onlineEnglish
    8·
    2 days ago

    Hi. I’m the feddit.online Admin. Nice to meet you!

    I downloaded Voyager 2.37.2 onto my Android phone and tried logging in, and it says it doesn’t support signups from Piefed, although the above post says to make sure to use 2.37.0 or greater. I get the same error trying to log into piefed.social.

    I haven’t made any modifications to the PieFed software, but I am on the development branch, as is piefed.social.

    Which PieFed server have you been able to log into? Are you using an iphone?

    • aeharding@vger.socialOPMEnglish
      7·
      2 days ago

      That’s what happens when you try to signup, not login. There is a login button below pick a server button.

      Also, try the web at https://vger.app/, probably easier to debug!

      • Jerry on PieFed@feddit.onlineEnglish
        4·
        2 days ago

        I was able to log in with 2 different accounts.

        I’m answering from Voyager using my Android phone. I don’t use a + in my email address though, but in don’t think it would cause a problem.

        Can you try again? If it still fails I’ll check the logs

        • aeharding@vger.socialOPMEnglish
          7·
          2 days ago

          Thanks for checking!

          I was actually testing an invalid login, where it says “connection error” instead of “invalid login credentials” because the backend error isn’t sent due to a CORS issue.

          After attempting login with piefed.social vs feddit.online, here’s the screenshots. See the “CORS missing origin” error under trasnferred column for feddit.online. Also the lack of access-control-allow-* headers compared to piefed.social.

        • Rimu@piefed.socialEnglish
          5·
          2 days ago

          Jerry your Cloudflare is getting in the way. When I go to feddit.online and run this JS in my browser dev tools I get a 403 and a bunch of gibberish from Cloudflare in my console:

          fetch('/api/alpha/user/login', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    username: 'testuser',
    password: 'secretpassword'
  })
})
  .then(response => response.text())
  .then(text => {
    console.log('Raw response:', text);
    try {
      const json = JSON.parse(text);
      console.log('Parsed JSON:', json);
    } catch (err) {
      console.error('Failed to parse JSON:', err);
    }
  })
  .catch(error => console.error('Fetch error:', error));


          
<div class="cf-section cf-wrapper">
        <div class="cf-columns two">
          <div class="cf-column">
            <h2 data-translate="blocked_why_headline">Why have I been blocked?</h2>

            <p data-translate="blocked_why_detail">This website is using a security service to protect itself from online attacks. The action you just performed triggered the security solution. There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data.</p>
          </div>

          <div class="cf-column">
            <h2 data-translate="blocked_resolve_headline">What can I do to resolve this?</h2>

            <p data-translate="blocked_resolve_detail">You can email the site owner to let them know you were blocked. Please include what you were doing when this page came up and the Cloudflare Ray ID found at the bottom of this page.</p>
          </div>
        </div>
      </div><!-- /.section -->