@BeAware@social.beaware.live
I'm not sure how easy it is to tell if a post requires you to be logged in if you're already logged into bluesky
https://github.com/snarfed/bridgy-fed/issues/1267 this was proposed the other day though which would help
tom
joined 11 months ago
@BeAware@social.beaware.live which is absolutely a fair complaint! Like I said I don't like the current popular suggestion. But that's why it's the opportunity for people (who are significantly better at design than me) to debate the logo because I also don't like meta's version for the exact same reason and that's gonna be the one we end up with 5 years from now.
Hell, I'm sure there's a way to take the current fedi logo and modify it slightly so it does work in flipboard's (or tumblr or Ghost or whoever else joins in the near future) design language and I feel like it's an important discussion to have now before everyone just ends up with Meta's boring version.
@BeAware@social.beaware.live I get that and I also don't particularly like ⁂ as the option. But the idea that we can't find some more useful logo because it'll confuse people when most people are unaware of the Fediverse's current branding seems off. If there's any time to debate the logo it'd be now before all these massive companies with hundreds of millions of users settle on a logo w/o the input of the open-source side of the fediverse.
I doubt Threads will ever move on from their version, but Flipboard has signaled they're willing to change out the logo they're using
@BeAware@social.beaware.live I dunno, personally I don't like the current fediverse logo. Tried to make it look good on a site a couple months ago and gave up and just put the mastodon logo in there instead, which probably isn't great for a network defined by many different servers.
Threads introduced their own fediverse logo probably for the same reason Flipboard adopted Threads' version- that it's pretty difficult to make it look good in different scenarios- which means assuming we stick with :fediverse: the default for everyone else will probably end up being Meta's version
@FandaSin@social.linux.pizza @BeAware@social.beaware.live Yes this is possible and I think it's been discussed as a solution. The concern, last time I was reading about it, is that malevolent servers could poison a link preview and send fake images along with the url (the argument against this is you're already 'trusting' the server if you're federating with them, so that trust should extend to link previews)
Another proposed solution was just having servers wait a random amount of time before fetching the link preview so not every server is requesting the preview at the same time