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!
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.
You must log in or register to comment.
I figure this is the best spot to make my first Piefed comment. Thanks for baking this in, I love Voyager!
Awesome. Thank you for all your work!
posted from Voyager on PieFed
Fantastic!!
Wait what is piefed? Anybody got a short easy to understand description of it or a link to something that’s easy to understand? Or is piefed like another instance of Lemmy?
By the way, Blahaj.zone has a piefed instance as well.
Does this blahaj.zone also not allow downvotes? I love the blahaj.zone community, but I need to see downvotes on news articles to know if there is some controversy, either with the news site, the content, or something else. I know why blahaj.zone doesn’t allow downvotes, and I support it, but I can’t have it be my main account’s instance because of my personal use case.
Comments and reports are usual better at calling out controversy than downvotes
I’m disappointed that this link opens an instance of Safari instead of just navigating to the front page of the instance in Voyager.
Feature request!
Still early beta, I think Harding might be waiting on bug reports before keeping all traffic in app.
No worries! just commenting on the state of things.
It’s a lot like Lemmy, but with a few important key differences, most importantly IMO, it has good onboarding and much better UX.
See more details here https://join.piefed.social/features/
It’s part of the Fediverse so it shares much of the same content, check it out https://piefed.social/Don’t forget the part where Piefed isn’t developed by tankies. That’s been a common point of contention for a lot of people who are reluctant to try out the platform (I don’t agree with the view, but people hold it).
Performance is also much better in my experience.
Lemmy’s backend is very performant, the UI is janky though. Using the lemmy frontend and then an app that just talks to its APIs is night and day.
Piefed is also new, with only about thousand users. Active users are going to be much less than that. It’s also written in Python, we’ll see how that scales.
Lastly, the official instance is behind cloudflare, so all your login credentials are going to CF before it reaches piefed servers. CF is most likely tracking users too. This is a no-go if you give a shit about privacy. But with a CDN, yes it connects faster.
So ya, kinda. It’s too early to tell and also comes with security (MITM) and privacy concern (on the official instance) with the CDN.
It’s nice to see Lemmy and their egotistical devs getting some competition though.
More options FTW.
Lastly, the official instance is behind cloudflare, so all your login credentials are going to CF before it reaches piefed servers. CF is most likely tracking users too. This is a no-go if you give a shit about privacy. But with a CDN, yes it connects faster.
I honestly don’t get why people always complain about this. The exact same thing can be said of the CDN services provided by Akamai, Amazon (AWS), Google, Microsoft, Fastly, and every other CDN in existence. If you don’t trust CDN’s then you should stop using the internet since most major sites use one CDN or another.
If you really want to be paranoid about your data being sniffed then you should be more concerned about companies that use services like SiteSpect. They basically operate as a MITM on your unencrypted data between the CDN provider and your origin, and their tools are specifically designed to modify that content.
If you don’t trust CDN’s then you should stop using the internet since most major sites use one CDN or another.
I’m trying my best 🙂
Lastly, the official instance is behind cloudflare
Isn’t this the case for most Lemmy instances as well?
Lol yes
1600 users, 948 monthly active. https://piefed.social/about
Across all instances, about 1500 mau and rising.
Exactly what I was thinking with Python. I love Python, and it definitely enables more devs to contribute and use it, but it is never something I would use for a backend because it will not scale without a lot of work. I don’t know a lick of Rust, but I know that it’s insanely good with scaling and latency, so if I was building a social media platform that I had high hopes in, I would just start with that and learn it.
It’s nice to see that the fediverse can expand laterally though and have many different options. I may open a PieFed account just to see how it goes. I’m optimistic about the future of the fediverse having been here for 3 years.
Let’s go! Thank you.
Might well be what pushes me to give piefed.zip a go :)
No offense to Interstellar’s app dev, but losing Voyager has been an almost killing blow for my use of Lemmy. Thank you for your work on bringing this over!
Whats this about Interstellar or losing Voyager?
Many lemm.ee users used Voyager, I think, myself included. However, lemm.ee shutdown as of yesterday. As far as I was aware those migrating from lemm.ee to a piefed instance could not utilize all the benefits of piefed without using a phone app that was compatible with those instances. Interstellar was one of the more similar apps to Voyager which worked with piefed instances. 🤷♂️ I’m not 100% sure on those details, however.
I just love having options!
Thanks! Writing this message from piefed.social via https://vger.app
Seems to be working. Nice work!
Trying image embedding:
Not able to see the embed, unfortunately
The image link is broken, doesn’t work in the browser either
FWIW, I used Voyager to paste an animated gif to Piefed. It accepted it, but it’s not showing. I use that function all the time with Lemmy.
Here’s a static image loaded from the photo gallery instead.
Attempt 1: It was a screenshot of a cartoon strip I had saved from Lemmy. Got an error posting, saying: “Problem uploading image: cannot identify image file app/static/tmp/jh0gouudldmvNK9.webp’. Please try again.”
Attempt 2: Image from photo roll I took of a book at the library. This is on an iPhone 15. This time it said: “Problem uploading image. filetype not allowed.” Guessing it might be an Apple HEIC format. Also, those files are usually pretty big. May have to convert it to jpg and downsample?
Attempt 3: An image copy/pasted from DDG browser. Got error again, saying:
“Problem uploading image: cannot identify image file ‘app/static/tmp/fPNxFlrGkybeGtK.jpeg’. Please try again.”
Hope this helps narrow it down.
Sounds like I have a new test pod to set up. Lemmy is nice, but the devs are kinda out there. Lack of app support has been the big holdback from trying out PieFed.
Great !
Based
Tried setting up an account on feddit.online and logging in but getting a connection error.
Can log in via browser fine, no vpn. Have a + in my email so maybe that’s causing it? Or need to wait for registration to propagate ?
Do you know the admins? It looks like CORS is broken on signin (POST req), which causes the PWA to break.
Works for all the other instances so maybe they are doing something custom
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?
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!
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
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.
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 -->Unrelated but sorta: there’s also these errors in the console, because Cloudflare is trying to inject a bunch of analytics and tracking which PieFed’s CSP is blocking:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015. (Reason: CORS request did not succeed). Status code: (null).
None of the “sha512” hashes in the integrity attribute match the content of the subresource at “https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015”. The computed hash is “z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==”. register
Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. node.js:417:1
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015. (Reason: CORS request did not succeed). Status code: (null).None of the “sha512” hashes in the integrity attribute match the content of the subresource at “https://static.cloudflareinsights.com/beacon.min.js/vcd15cbe7772f49c399c6a5babf22c1241717689176015”. The computed hash is “z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==”.
deleted by creator
🎉🎉🎉 let’s go!
