Hi Lemmy! Boost 1.0.35 is out, and it brings support for Lemmy 1.0 🎉 This is the changelog:

General

• Support for Lemmy 1.0 instances
• Configure communities you moderate, including icons, banners, visibility and posting permissions
• Insert custom instance emojis in posts and comments
• Added controversial comment sorting
• Explain why community posts are unavailable

Lemmy 1.0

• Create and follow multi-communities to bring your favorite communities together in one feed
• Customize notifications for posts and communities
• Add colorful tags to posts and find content more easily
• Block unwanted words and add personal notes to users
• Discover random communities with a single tap
• Request access to private communities
• Improved search with more filters
• New moderation tools to manage posts, comments and community requests
• Browse the moderation log of your instance, a community or a user

PieFed

• View and delete your uploaded media from your profile or settings

📲 To join the beta and test the new features first follow this link https://play.google.com/apps/testing/com.rubenmayayo.lemmy or visit the Play Store and scroll down to "Join the Beta"

⚠️ Found a bug about this version? Comment below

❤️ Boost. Ever since I found it for that other shit site.

IMO it's the best. Loaded with features and custom options.

Keep up the great work!

Community name in the feed was shortened to "[email protected]" when the actual community was "Offbeat News - Not The [email protected]" as correctly rendered when viewing the full post. Given the meaning of onion/not the onion, this can lead to confusion as to whether the post is satire or real news.

Boost currently does not support setting nor reading alt text on image posts.

I recently implemented an alt-text rule on one of my communities as a countermeasure to those "twitter post" style images where the content is text on an image, which is not legible by a screen reader. However, not being able to see the alt text makes it hard for me to moderate, and not being able to add it to image posts makes it hard for the users of my community to add alt text without putting it in the post body.

This missing feature could accidentally exclude visually impaired users from consuming image content produced by Boost users unless the poster thinks of adding an alt text to the post body and the visually impaired user thinks of checking the body instead of the dedicated alt text field.

We need the internet to be a more inclusive and accessible place, and this starts with helping netizens produce accessible content.

I don't mind having ads, it provides income for boost from users who don't pay for it. This is okay, I'm not arguing against it.

However, trash tier ads pushing medical scams served up my meta of all places are another thing entirely.

That's not okay.

And no, "then just pay to use boost" isn't a valid response for a few reasons :

1. Not everyone will, and those that don't shouldn't be subject to manipulation and scams that could cause real world harm if they don't know any better. That looks bad for boost.
2. I run services myself and I don't hold my users hostage and use that as an excuse to get them to pay me money. A good user experience should convert users, not a bad one. I'd be surprised if you or boost do as well.

This is feedback for boost, not an invitation for flaming...

The post: https://lemmy.zip/post/71738735

Boost crashes immediately after hitting reply, every time. No issue replying to the post via the Lemmy.zip web interface.

type: crash
osVersion: google/shiba/shiba:17/CP2A.260805.005/2026091001:user/release-keys
flags: dev options enabled
package: com.rubenmayayo.lemmy:37, targetSdk 36
process: com.rubenmayayo.lemmy
processUptime: 8218 + 487 ms
installer: com.android.vending

java.lang.RuntimeException: android.os.TransactionTooLargeException: data parcel size 646716 bytes
Bundle stats:
  android:viewHierarchyState [size=4632]
    android:views [size=4580]
  androidx.lifecycle.BundlableSavedStateRegistry.key [size=640920]
    android:support:activity-result [size=1268]
    android:support:fragments [size=639272]
      fragment_fd41aa64-84af-49b6-ab0c-72303288c84b [size=638760]
        arguments [size=12032]
          submission [size=11984]
        savedInstanceState [size=625152]
          submission [size=312264]
          contribution [size=312264]
PersistableBundle stats:
  [null]
	at android.app.servertransaction.PendingTransactionActions$StopInfo.run(PendingTransactionActions.java:156)
	at android.os.Handler.handleCallback(Handler.java:1095)
	at android.os.Handler.dispatchMessageImpl(Handler.java:135)
	at android.os.Handler.dispatchMessage(Handler.java:125)
	at android.os.Looper.loopOnce(Looper.java:296)
	at android.os.Looper.loop(Looper.java:397)
	at android.app.ActivityThread.main(ActivityThread.java:9569)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:575)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975)
Caused by: android.os.TransactionTooLargeException: data parcel size 646716 bytes
	at android.os.BinderProxy.transactNative(Native Method)
	at android.os.BinderProxy.transact(BinderProxy.java:656)
	at android.app.IActivityClientController$Stub$Proxy.activityStopped(IActivityClientController.java:1562)
	at android.app.ActivityClient.activityStopped(ActivityClient.java:103)
	at android.app.servertransaction.PendingTransactionActions$StopInfo.run(PendingTransactionActions.java:141)
	... 9 more

The app doesn't seem to account for the button bar on Android 16 and just assumes the user is using gestures. Could we fix this? The settings bar is the same height as the button bar and is completely inaccessible.

This is specific to the lateral menu and home screen. The home screen has a workaround by enabling the bottom navigation bar, however this is not ideal as it adds extra icons.

Settings activity itself seems to properly implement the button bar.

Scrolling the body of This post is super choppy, gets better once it's all offscreen

Boost showed I had an unread notification but no information on what it was. Logging in to the web portal showed that I got a new follower.

Is this a boost bug perhaps? What injects this proxy part? slrpnk.net admin said they think it's a client bug so here I am

Note the hhttps (double h) and the missing h further after the proxy ttps

What title says. Last update made it so I that the app quits with just one tap even if it's set to two.

version 1.0.33 com.rubenmayayo.lemmy is installed.

Kind of weird, but no ads show. Maybe just a bug with the latest update?

I can often see thumbnails for avif pics and when I click to view it I just get a black screen. If I long press the pic and click on the link it loads in the browser fine. I've gotten used to this and I can detect it pretty fast now since there's no loading bar at the bottom for these. But is there anything that can be done to get these to load with a single click like other image files?

I guess it's the second or third post I created here with this issue. Is this only happening to me?

Had to open in browser to see it.

cross-posted from: https://discuss.tchncs.de/post/65681514

Trying to upload a video (barely 10 seconds long) and it tells me:

"These actions are forbidden"

Am I missing something?

I can't find the option anywhere lol

Anybody that knows how I can have bottom part of boost be above the navigation menu? Linuxmemes is hidden behind navigation bar