Nah, I'm sure it'll be fine. It'll be like a Fediverse Brexit ...
andrew_s
joined 1 year ago
Neat. I saw your name in the 'Users' list (Search -> Explore Instance -> Users).
The API needs a DB upgrade, and so right now I'm in a queue behind 'Feeds', which is a feature that will add some new tables. I don't yet know what kind of upgrade it needs to be, i.e. how much things can be fudged vs. implemented properly.
Oh, right. Thanks. Sorry, I'm realising now that what I said was a bit of lazy assumption. I've just looked, and saw that Interstellar is also Flutter, so you're a lot more likely to know than me (I've very new to all this). I'll edit my post.
Yeah, the API is very similar in lots of ways. Some fields have different names (e.g. post.title instead of post.name), the 'site' response is a lot smaller, and there's things like 'activity_alert' for subscribing to other people's posts/comments and unsubscribing to your own (aka turning off inbox replies). Some routes aren't covered, either because the app didn't call them, or because there's no back-end support (e.g. viewing Modlogs), or because I de-prioritized them for now (e.g. viewing Reports).
I've started doing an OpenAPI spec thing, which I'm finding tedious to create, but it should make everything clearer when it's published.
Maybe I've the wrong idea. This app is a fork of Thunder (for Lemmy), and Thunder is only available on f-droid via the IzzyOnDroid repo, so I was thinking that it contained some binary blobs from Google.
More so 'other Fediverse socials'.
Here's an example on PieFed, that's a PixelFed user tagging their photos with 'dailyphoto' and then sharing via a.gup.pe on Mastodon: https://piefed.social/tag/dailyphoto
Lemmy has mangled that script a bit.
Where it says '%24%7Bpage%7D', it should a dollar sign, an open curly bracket, the word 'page', then a close curly bracket.
It displays a bit better at the source (click the multi-coloured fedi-link thing).
The only way I can think of is to use the API to get all communities, and then filter out the ones without local subs. So a basic BASH script would be:
#!/bin/bash
echo -n '' > /tmp/allcomms.txt
page=1
while true
do
communities=$(curl --request GET --url "https://walledgarden.xyz/api/v3/community/list?type_=All&page=%24%7Bpage%7D&limit=50" --header 'accept: application/json' | jq .communities[])
if [ "${communities}" == "" ]
then
break
fi
jq -r '[.community.id, .counts.subscribers_local] | @sh' <<<$communities >> /tmp/allcomms.txt
page=$(( page + 1 ))
sleep .5
done
while read id count
do
if [ $count -eq 0 ]
then
echo "$id has no local subs"
fi
done < /tmp/allcomms.txt
(It'll take a few minutes to run)
After that, how you purge the communities with those IDs I'm less sure of. My guess would be:
Get a login tokin:
JWT=$(curl --request POST --url https://walledgarden.xyz/api/v3/user/login --header 'accept: application/json' --header 'content-type: application/json' --data '{"username_or_email": "YOUR_USERNAME","password": "YOUR_PASSWORD"}' | jq -r .jwt)
Use Admin/Purge from the API:
curl --request POST --url https://walledgarden.xyz/api/v3/admin/purge/community --header "authorization: Bearer $JWT" --header 'content-type: application/json' --data "{"community_id": ${id}, "reason": "no local subs"}"
As long as purge lets the community be recreated again (which it should do), then that should be okay.
Don't take my word for any of this for an in-production Lemmy server, though. Test first!
Whatever the views are about MBFC, Tesseract integrated it better than LW's bot. If you don't like MBFC, it's just an option in your user settings to turn it off for Tesseract, whereas the bot caused a bunch of problems that weren't even related to concerns about accuracy and bias. Drive-by bots can be annoying, because it leads people to believe there's legit content where there isn't, and not every client respected LW's bot use of spoiler Markdown, so they ended up with a massive comment from it that dominated the screen.
22
Not just AI datacenters needing own power: Taiwanese server-maker Quanta has bought microgrids
(go.theregister.com)
There's more than one way to do this, of course. For group-based forums like piefed, I think the most promising way is to automatically create a local community for each person that someone wants to follow. Incoming activity is then put into the appropriate community, and so you have a consistent UI of UserA has posted to technology@wherever, and UserB has posted to [UserB's community]@piefed.social. This avoids the '2 websites in 1' look that can happen when a site wants to display both lemmy-like communities and mastodon-like microblogs.
I haven't done too much work on it, in case this idea gets shot down in flames. So far, what I've got is:
-
A user searches for another remote user, e.g.
@freamon@pixelfed.dk -
When they're found, the user is offered the opportunity to create a 'Follower Community' (for want of a better name. I've been using 'fan club', but that's maybe a bit naff)
-
The community is created, formatted from the profile id, so
[https://pixelfed.dk/users/freamon](https://pixelfed.dk/users/freamon)becomes[https://piefed.social/c/pixelfed_dk_users_freamon](https://piefed.social/c/pixelfed_dk_users_freamon) -
A follow request is sent to the remote user (from the user doing the search, or a dedicated bot account, maybe)
-
Incoming activity will just be to activitystreams and followers, so there won't be any matches in 'to', 'cc' or 'audience'. In that case, 'attributedTo' is looked at, using the same conversion as above: so something from
[https://pixelfed.dk/users/freamon](https://pixelfed.dk/users/freamon)will be sent to[https://piefed.social/c/pixelfed_dk_users_freamon](https://piefed.social/c/pixelfed_dk_users_freamon)if it already exists. -
The posts will show in the community like any other. Other users can then subscribe to the community in the normal way, and get updates whenever the remote actor publishes something for their followers.
-
Posts from Mastodon would need another post-type to look their best (something that simulates how they look over there). Posts from Pixelfed already display well using Masonry:
On pixelfed:
On piefed:
-
Post replies and upvotes (maybe) should make their way back to remote user, the same way they do if they'd actually made a post in a local community.
Random thoughts:
There would need to be an Undo Follow sent if the community was deleted.
A local community called c/pixelfed_dk_users_freamon looks a bit ungainly, but there's likely a way communities like this could be rendered as something like [SELF] in the homepage feed.
I realise pixelfed are planning to implement Groups, but that hasn't really worked out for mastodon, so we'll see how it goes. I think the ability to follow individuals will still be useful.
The remote user could be made a moderator for the local community, and it set to 'mod posts only' so it would only contain stuff from them.
This approach doesn't require any database changes.
I've just bashed this together for now - looking to get your thoughts before I continue ...
view more: next ›
You should listen to the voice that's telling you not to add more spoons to this already heavily-stirred bowl of shit.