freamon

EDIT: Issue is fixed now, thank you.

~~I'm not sure anything from this instance is federating anywhere since this change.~~

~~Looking at activitypub, attempting to subscribe to something gets no reply (the screenshot below shows me trying with 3 different communities, followed by what's expected to happen with a random community on another 0.19 instance)~~

~~Looking at an active community (like nuclear@feddit.nl), there's been 6 posts in the past 2 days that aren't showing up anywhere else (at <whatever_instance>/c/nuclear@feddit.nl)~~

Ah. I'm guessing that this instance has now made the same change as programming.dev - counting 'active users' as people who post, comment or vote, not just those who post or comment.

Stats will be a bit crazy for a few days, as the 7-day average will include the massive 1-day increases (e.g. !redhead@lemmynsfw.com went from 46 active users to 1569) but they'll normalise from about the 12th December.

Oh. So it seems lemmynsfw is on 0.19 already (I had to change the bot a bit)

Re: trending communities, if a link gives you this error:

The server returned this error: FetchError: invalid json response body at http://lemmy:8536/api/v3/post/list?community_name=exchristian%40lemmy.one&page=1&limit=20&sort=New&type_=All. This may be useful for admins and developers to diagnose and fix the error

that's just a timeout that's usually resolved by a refresh. It'll happen more often with links from that list than elsewhere, because it's more likely to provide links that no-one else on feddit.nl has visited before.

I just had a click around on the latest post, and that was the only error I got. If it's not that though, please leave a comment. I'm on the same instance as you, so can investigate what the problem might be, and it's my bot, so can try to fix it if need be.

I created an account here and a couple of communities, but it was sort of by accident that I'm here. At the time, join-lemmy referred to the Awesome Instances GitHub page, and that recommended feddit.nl, and said don't overthink it, so I didn't. If I had thought about it more, I would've joined up to feddit.uk I suppose (although that's the instance that people are now concerned about now, ironically enough).

But given the .nl domain, maybe feddit.nl should just be a place for people to talk to one another in languages (other than English) that are popular in The Netherlands. For the focus to generally be specific to one location, and for Communities that other instances in the Fediverse don't provide. (sort of like what I imagine feddit.it does for the people of Italy).

I'm fairly active on Lemmy (from accounts on endlesstalk.org and lemmy.world), but the content I really want to create is animated in some form - as a gif or a webp file. My efforts in this are being stymied by Lemmy, as it seems utterly determined to wreck them, either by half-arsing an unwanted transcode, or re-compressing something that's already compressed. So, similar to others in this thread, but for completely different reasons, I'm waiting for the software itself to mature before I can fully unleash my genius on the world.

As for frontends, I've started using photon at lemmy.world. It's really nice, especially for the aforementioned animated stuff. I've even started using phtn.app for browsing on my phone too. (There's also Tesseract, a fork of photon that I've only seen at db0 and dubvee.org, but would like to play with.)

I'm guessing this is from the latest episode - if so, this Community is becoming my primary source for knowing when a new episode drops.

Mysteriously, this isn't currently playing via the standard web page on lemmy.world. But it does when viewed from other instances/frontends/apps, so I don't understand.

Casually hands over receipt:

Yeesh. Dunno why Nostalgia is tagged NSFW, but it's only moderator is long gone now. Won't appear in future. Will filter out shitultrassay while I'm at it.

Have found it impossible to upload this file directly to Lemmy. It's already a compressed WEBP file, but whatever settings I use, Lemmy insists on copying it and compressing it further, until there's only about 5 pixels left. So the only options left are for the post to be a link to the external url, or for it to look like a comment post, but with an inline image squashed inside. Neither are ideal.

EDIT: My experience with Lemmy:

EDIT 2: Now have something a bit more acceptable, loaded directly to Lemmy.
Lemmy always seems to compress WEBP at 75% - I uploaded an image, it compressed it, I downloaded Lemmy's version and re-up'd that, and it compressed it again. Presumably I could do this forever.

So, I created the original WEBP using the 'lossless' setting (it was about 2.5MB), uploaded that and let Lemmy convert it, and now it doesn't look too bad. The only thing is I had to use the version I tested at enterprise.lemmy.ml, 'cos feddit.nl got confused by the transparent frames. So the trick seems to be: upload the least efficient version imaginable

Ooops. I tested it before I posted, and the reason it worked is because it turns out that authentication isn't needed for that query.

I've edited the comment now, and there only being one part means that there's no need for an ampersand, so there's no probs with special characters.

Hi. I've found the best place to test the api is here

Example script for making a post

my_instance="https://lemm.ee"

auth="YOUR-JWT"
community_id=COMMUNITY-ID
name="TITLE OF POST"
body="BODY OF POST"

API="api/v3"

create() {
        end_point="post"
        json_data="{\"auth\":\"$auth\",\"community_id\":$community_id,\"name\":\"$name\",\"body\":\"$body\"}"

        url="$my_instance/$API/$end_point"

        curl -H "Content-Type: application/json" -d "$json_data" "$url"
}

create

You'll need to get your instance's community.id for the community you want to post to. To use this community as an example, it would be:

my_instance="https://lemm.ee"

API="api/v3"

resolve() {
        end_point="resolve_object"
        www_data="q=https://lemmy.zip/c/linuxscripts"

        url="$my_instance/$API/$end_point?$www_data"

        curl "$url"
}

resolve

(lemmy will probably sanitise the ampersand in that query, so you'll have to replace the HTML with a literal ampersand)