Discussion
I just went to enable the ATProto support on Wafrn and quickly realised this is *not* the native ATmosphere integration it's been promoted as.
The 'enable BlueSky' page in Settings says;
"To enable Bluesky, you will log in through the Bluesky flow and authorize your account."
Seems that it's essentially just an internal BS client, so it still requires a BS account, under the dominion of BS management. This is a bit disappointing.
(1/2)
@mrnnki
> Notice that it says our PDSes are not a Bluesky PDS. Your Bridgy account lives on Bridgy's PDS
This is how the feature is promoted, and what I was expecting. But how does this square with;
"To enable Bluesky, you will log in through the Bluesky flow and authorize your account."
Maybe that wording is just unclear. Because it gave me the distinct impression that BS is in control of the account, which implies they host it.
(1/2)
If I got the wrong end of the stick, then yay! But I suggest that this wording is clarified, so it's harder to misunderstand.
(2/2)
@strypey@mastodon.nzoss.nz
That's a fair point! I think I saw in the Discord that someone might be working on rewording it to prevent a misunderstanding like this from happening again
@strypey @admin @deadsuperhero have you tried reaching out to the admins of wafrn first or are you an idiot who can only act like wafrn just scammed you out of your life savings
@2ko
> have you tried reaching out to the admins of wafrn first or are you an idiot
Have you tried not being a charging up to strangers online and screaming abuse at them? It's remarkably effective ; )
There's a pretty big difference between a native ATProto integration and a BlueSky client. If the wording of is inconsistent between the promotion for this feature, and the description inside the app, I think it's only fair to point that out.
Maybe that's a UX problem devs might want to fix?
@strypey yeah and that could've been done in a better manner than making a public post like admin is purposefully trying to scam people
you really can't complain when you yourself speak in such a tone mate
@2ko Doubling down on your right to call someone an idiot, eh? And reacting without taking a second to think, to boot.
Learn some fucking manners you little punk. Go take a long walk off a short pier.
Muted for a month.
@strypey@mastodon.nzoss.nz @admin@app.wafrn.net @deadsuperhero@social.wedistribute.org
It's named that way for easy understanding since many people do not understand what AtProto means, but you can ask @gabboman@gabboman.xyz for more information.
@noahebalon
> It's named that way for easy understanding since many people do not understand what AtProto means
I get the logic. But wouldn't it be better to contribute to educating people, than to help entrench that knowledge gap?
I would use generic terms (ATProto or maybe ATmosphere) to label the features in the interface. Then explain the connection to BS during onboarding to Wafrn itself, and again in the text presented after clicking 'enable ATProto'.
@noahebalon@app.wafrn.net @strypey@mastodon.nzoss.nz @admin@app.wafrn.net @deadsuperhero@social.wedistribute.org
Its a “if you want to use the bluesky client”
Do not insult me like that strypey haha
@gabboman@gabboman.xyz @strypey@mastodon.nzoss.nz @admin@app.wafrn.net @deadsuperhero@social.wedistribute.org
Why are we creating fedi meta on a friday 🥲
#bluesky #atproto #wafrn #fediverse
@noahebalon@app.wafrn.net @strypey@mastodon.nzoss.nz @admin@app.wafrn.net @deadsuperhero@social.wedistribute.org
Check my pinned post
This isn't spelled out quite as clearly on the Wafrn website and it is in the 'enable BlueSky' page in the app's settings. But if you read to the bottom of the FAQ page on the BS 'sidecar', it's pretty clear you need to either already have or create a BS account to use it;
https://wafrn.net/faq/Bluesky.html
The whole reason I found this feature interesting is that I don't want an account on BS, or any ATProto-only service. Oh well ...
(2/2)
@strypey@mastodon.nzoss.nz
hello! we're just trying to understand your issue here
you "don't want an account on BS, or any ATProto-only service" but "went to enable the ATProto support on wafrn"
so, what was the intended behaviour you expected?
if some rewording on our FAQ and instructions is needed we can work on that, but I'm having a hard time understanding what exactly is your issue right now so please do give us more info on how you thought that would work. might be a misunderstand on any of the sides.
@strypey@mastodon.nzoss.nz
just to clarify
when you enable the bluesky connection, it creates a registry on the wafrn PDS, which is completely independent from bluesky. your dashboard, the people you follow and interact with you don't depend on any of bluesky architectures
we do use bluesky appview to display bluesky custom feeds and to integrate DMs, but everything else is independent!
our PDS creation currently automatically creates a bluesky profile record for you, since it was engineered thinking of the woots/toots/posts native integration with bluesky itself, but you can also use the PDS for other apps as well and you can disable your posts going to bluesky (its gonna just be a ghost empty profile on bluesky side)
at the moment its not possible to create a PDS without creating an account, but all your records lie in our structure and don't depend of bluesky
i believe things just got misunderstood here, but if you have any questions please let us know
@brotosolar
> you "don't want an account on BS, or any ATProto-only service" but "went to enable the ATProto support on wafrn"
If the PDS is hosted on the Wafrn instance, which also speaks AP, then it's not an ATProto-only service. BS doesn't speak AP (or any 2nd protocol), so it's an ATProto-only service. Make sense?
The wording;
"To enable Bluesky, you will log in through the Bluesky flow and authorize your account."
Implies that the Wafrn instance creates an account on the BS PDS.
(1/2)
Install Fedizen
Get the full app experience
@strypey@mastodon.nzoss.nz
is this not also what Bridgy does, but with more features and control than it has?
Here is your Bluesky/ATproto account as created by bridgy:
https://pdsls.dev/at://did:plc:fgltx44zk7r33d76v3z4g7kj
here's my account on the same viewer, for comparison:
https://pdsls.dev/at://did:plc:xn7uycuwxbg7xot6hdjm4bkk
Notice that it says our PDSes are not a Bluesky PDS. Your Bridgy account lives on Bridgy's PDS. My account lives on my Wafrn instance's PDS. Wafrn gives you full control of the ATproto account and allows you to directly view and interact with Bluesky accounts. While if you use Bridgy, Bridgy manages the account and you can only see bridged Bluesky accounts.
This article is written from a very pro-ATproto perspective, but it describes how Bluesky/ATproto works in comparison to ActivityPub quite well. I don't want to assume you're unfamiliar, but I wanted to link it in case you are: https://overreacted.io/there-are-no-instances-in-atproto/