Thanks for this awesome patch! Now I can post from Piefed.ca easily!
Voyager
The official lemmy community for Voyager, an open source, mobile-first client for lemmy.
Rules
- Be nice.
- lemmy.world instance policy
Sponsor development! 👇
💙
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
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 -->
I've got some work to do tonight, then. Thanks for the assist!
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%E2%80%9D. 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%E2%80%9D. The computed hash is “z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==”.
Thanks, everyone, for pointing out these issues. I had a little time, so I took a look. I believe all the issues are resolved now. There is no longer an API error and I no longer see the console errors.
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.
Great !
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.
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
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!
Might well be what pushes me to give piefed.zip a go :)
Let’s go! Thank you.
Great work, thanks for this.
🎉🎉🎉 let's go!
I figure this is the best spot to make my first Piefed comment. Thanks for baking this in, I love Voyager!
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.
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 ask 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/
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.
1600 users, 948 monthly active. https://piefed.social/about
Across all instances, about 1500 mau and rising.
Lastly, the official instance is behind cloudflare
Isn't this the case for most Lemmy instances as well?
Lol yes
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).
Awesome. Thank you for all your work!
posted from Voyager on PieFed