aeharding

joined 1 year ago
MODERATOR OF
[–] [email protected] 3 points 6 days ago (4 children)
[–] [email protected] 1 points 6 days ago (6 children)

Not at all. thanks for letting me know (that was the hope of making the original post!) try the next build coming down in a sec

[–] [email protected] 1 points 1 week ago (1 children)

Thanks for your help, try the next build when it comes down the pipe

[–] [email protected] 3 points 1 week ago (13 children)

Try build 698, just released :)

Should fix piefed.social. ca still has known issues with admin array not returned for some reason

[–] [email protected] 1 points 1 week ago (17 children)

.ca has known issues. .social should work though. What build number do you see on the About page?

[–] [email protected] 3 points 1 week ago (2 children)

Thanks! Try the next build ([697] d0aef95), it should fix these problems.

[–] [email protected] 4 points 1 week ago

That's the goal. Especially since the compat lib is separate, I'm hoping to get it mature enough to the point that it could eventually be community maintained.

[–] [email protected] 3 points 1 week ago (4 children)

How strange. Only other thing I can think of is Piefed will rate limit API logins, to 6 per hour. After that it will fail.

[–] [email protected] 4 points 1 week ago (1 children)

Ah, it's not you, piefed.ca is the main piefed instance people are having issues with. It looks like its just running a slightly outdated version of Piefed, hopefully fixed soon!

[–] [email protected] 3 points 1 week ago (26 children)

piefed.social should be fine, that's what I've been testing with! I'll keep my eyes out though.

[–] [email protected] 4 points 1 week ago (5 children)

I think I saw that issue on first login. However it should go away on refresh/restart app, does that work?

[–] [email protected] 2 points 1 week ago

piefed.ca is running slightly outdated version, hopefully that's fixed soon :)

piefed.social should connect, that is what I used to test. Are you seeing issues with that instance?

 

Well I couldn't find this on the internet anywhere-

I was having issues setting up active-backup bonding on my Mikrotik router via this guide.

Whenever I turned on both interfaces, I experienced packet loss.

The solution was to TURN OFF hardware offloading. It doesn't work with active-backup. The docs even say it doesn't work with hardware offloading, but it failed in a way that was hard for me to debug.

So yeah! Now works great, router <-> unmanaged switch with bond bridged.

 
 

Hi everyone!

2025 is here, and I'm curious to hear your thoughts on Voyager for Lemmy.

  • What features would you like to see added to Voyager in 2025?
  • Are there any bugs or issues that are bothering you?

💜

 
 

Voyager F-droid/Github/Standalone releases on lemmyapps.com say last updated 9 months ago, but that's not right

 

Hello!

I’ve updated Voyager’s build and release process to automatically include new fixes and features in test builds.

iOS users have always had TestFlight, and now Android users can join testing through Google Play Open Testing:

👉 Google Play Open Testing

I’m looking for Android testers! If you’re okay with occasional bugs and want to help out and report issues on Github, I’d be grateful.

P.S. Also new: For PWA users, you can now test updates here:
👉 beta.vger.app

Thank you!

 

I've been getting a few messages about blurry images from lemmy.ml users due to lemmy v0.19.6. I rolled out a fix yesterday; it is in all stores except F-droid (will probably be there in a few days)


In other more exciting news, user tags is almost here! Stay tuned!

 
 
 
  1. Fitted sheet must have label on bottom right seam
  2. Salted butter wrapping text must be red. Unsalted blue.
 

cross-posted from: https://vger.social/post/6164807

Radiation fog - Dane County, Wisconsin

 
view more: ‹ prev next ›