If you long press community name you can block from feed. Same with usernames!
Punch nazis, trebuchet TERFs.
I am building Voyager, a client for lemmy!
- 45 Posts
- 711 Comments
Ah, lemmy.ml issue, I think I can fix that.
aeharding@vger.socialMto
Voyager@lemmy.world•[Feature Request] Clear web browser cookies per websiteEnglish
1·30 days agoInteresting request! Although I don’t think SFSafariViewController allows clearing cookies by website
aeharding@vger.socialMto
Voyager@lemmy.world•[~~Bug~~][Fixed!] Blocking a comm in feeds jumps up the feed.English
2·2 months agoDunno how I missed this so long! Thanks for originally reporting.
aeharding@vger.socialto
World News@lemmy.world•Rocket lifts off with four Artemis II astronauts on a mission to the moon and backEnglish
312·2 months agoI forgot I received this a few years ago from volunteering… let’s go Artemis!

608? That’s my area code 😆
@return2ozma@lemmy.world you are appreciated!!
aeharding@vger.socialMto
Voyager@lemmy.world•Is there a way to sync the web version of voyager to its mobile client(specifically for user tags )?English
2·2 months agoYou can export settings and import, should include tags.
Posted from my 2m aliexpress usb-c cable running at 40gbps
Awesome thanks!
What version of Voyager? You can check in Settings -> About
aeharding@vger.socialMto
Voyager@lemmy.world•Voyager semi broken from outdated webviewEnglish
3·2 months agoAnd please do feature detection
I’m not sure how you’d do that with safe area insets. You could check for zero but some modern devices megitimately have zero safe area insets. Capacitor itself has to check Blink version for the SystemBars plugin.
But the app works fine with a “too old” webview. Why warn about it?
If you go into dark mode the status bar will be white with white text, because safe area doesn’t work properly.
aeharding@vger.socialMto
Voyager@lemmy.world•Voyager semi broken from outdated webviewEnglish
2·2 months agoYou dont need the Android System Webview in particular. Android supports alt webviews. The important part is to make sure its based on Blink 140 or newer (haven’t tested other engines).
aeharding@vger.socialMto
Voyager@lemmy.world•Voyager semi broken from outdated webviewEnglish
3·2 months agoGotta keep your webview up to date! There’s alternatives as described in the comments but yeah, having a version of Chromium older than a year old is pretty dangerous/insecure.
I think most ‘normal’ android users never really think about it because Google keeps their webview up to date automatically, but if you dont use Play Store this can be easily overlooked. Really important for device security though.
Edit: As for why Voyager requires System WebView >= 140… Android recently overhauled safe area insets and their rollout was kinda botched with poor backward compatibility. This is a side affect unfortunately.
aeharding@vger.socialto
Technology@lemmy.world•System76 tries to talk Colorado down over OS age checksEnglish
1·2 months agoUsing pop/cosmic here, is awesome!
aeharding@vger.socialto
Programming@programming.dev•Projects are shutting down due to Microslop's Github CoPilot making AI contributions easy and plentiful
8·2 months agoWhy aren’t people moving away from Github?
I write open source software because it’s fun, and I publish on Github because it gives me a stronger professional profile.
So yeah for me it’s the potential difference between putting food on the table or not. Github stars suck for many reasons but they do help you stand out.
aeharding@vger.socialOPMto
Voyager@lemmy.world•Voyager v2.37.1, with experimental Piefed supportEnglish
1·5 months agoI think that’s a bug with the piefed API. There is a bug on Github, just have to make the Piefed devs aware.











What version of Android are you running?