Hello fedi. i am trying to solve the "fetch all replies" problem once and for all that makes the fedi feel a lot more desolate and with a lot more reply guys in it than it should be. this is take two, where before i had it triggered by a button, but now i think it should happen on the server-side whenever you expand a post. can anyone help me out figure out how to make this more efficient by only fetching posts that the server doesn't already have? i am not sure what the best strategy would be, and if anyone with experience doing efficient rails and SQL stuff could give me some pointers that would be gr8. the patch is actually extremely simple it just needs a few nice things to make it not DDoS everyone.
Scheduler::VacuumScheduler and Scheduler::UserCleanupScheduler run at the time I am most active. I am sure that is why I have some weird issues when I am surfing my timeline, like when it goes blank. Is there any way to alter the time that they run in SideKiq? If they could run at like noon instead of midnight that would be great.
But never thought that I would be coding it this way, and it works ✨ Don't have to wait for next/newer versions of masto.js when there are API endpoints/parameter/method changes. It lacks types but fine for me.
Now deployed on #PhanpySocialDev (dev.phanpy.social). Media-first UI experience only kicks in for #Pixelfed account log-ins. Basic features work, except:
Local and Federated timeline show the same thing
Trending, Bookmarks, Reply, Lists, and Filters don't work
Question: a desktop software that queries the public Mastodon API to provide an overview of an instance (about page, rules, admin account, user count, moderated instances) – would that have any scraping / block circumventing concerns?
This would be without access token and such, so authorised fetch, disallow public API access, etc. would prevent fetching any information. And all of this is publicly available information that can be queried from /api/v1/instance without requiring authorization (by default). Basically, nothing you couldn't find by going to instance.example/about.
I want an opinion. If you have a rule to not allow signups with some email domain, would you expect it to also apply to signup requests, when your server is in manual-approval mode?
Looks like the New Interface for #MastodonSocial#DotSocial doesn't run in #IceCat on my (now-fixed after nearly 3 months) PC! The error is Uncaught TypeError: Object.hasOwn is not a function, which is presumably because IceCat doesn't use the latest JS (it's something like a couple of years behind FF), but that shouldn't be a reason to break on it! I hope this new interface isn't rolled out to here too! #MastoDev@Gargron
The newly released 0.7.0 version of @Tuba, your #GNOME-native #Mastodon client, is friggin' awesome. Not only does it ship tons of bugfixes and allows darker images in dark mode, but it also ships the ability to create, edit and apply words filters (as you can see in my screenshot here) so you can simplify your timelines views.
Congratulations to #MastoDev@GeopJr for this fantastic leap forward!
Is there an #ActivityPub server where I need to parse HTML for <link type="application/activity+json" href="..."/> to get to the JSON representation of an object? I want to add support for this in #Smithereen but I need something to test against.
Doing a random check of my server logs, looking for oddities and trouble.
In 'journalctl -u mastodon-web' I see, "ERROR -- : [ActionDispatch::HostAuthorization::DefaultResponseApp] Blocked hosts: <my server IP address>" as shown below.
Does this just mean someone/something is trying to access my Mastodon instance from the IP address and not the host name?
Safe to ignore? Normally the IP forwards to the domain name. I just checked and it does.
I think one of the most powerful changes we could make to content discovery on Mastodon is by showing hashtagged posts to everyone following that tag.
Right now, you only see tagged posts from your federated feed, which is (I think): posts and boosts from your follows, from anyone on your server, and from anyone followed by anyone on your server
If you’re on a big server then yes, that is a lot of posts, but it’s no way near all of them!
I'd like a way to mute people on Mastodon for a month or half a year; many are not toxic enough for an indefinite mute, but draining enough that a week feels too short.
I've long seen people question why there's a perception that Mastodon is hard to use.
Let me use a really concrete example I just came across that breaks the maxim "don't make me think":
Bluesky just added keyword muting, and it's way easier than doing it here.
While viewing any feed/post:
Moderation > Muted words and tags > type in word (the focus is in text field, no click required) > hit enter > click back button twice to return to where I was.
But why? Surely I shouldn't ever run the mastdon database as super user, so this will always cause issues, as pg_repack can only be run as superuser? And most people probably don't have the extension installed at all.
It's not a deal breaker, just a wish list item, but I wished filters would let you see the username of the post you muted when filtering with a warning.