freamon

joined 1 year ago
[–] [email protected] 2 points 5 months ago

Big Luna Bloom fan.

[–] [email protected] 1 points 5 months ago

Just posting to nag you about this: can [email protected] be added as an exception to the automod?

[–] [email protected] 3 points 5 months ago

Lemmy doesn't seem to get much recognition in the wider Fediverse - it tends to get bundled as part of 'other apps'. Mastodon is much bigger, so better integration with Lemmy probably gets deprioritised below their own issues and feature requests (e.g. I was reading today that Markdown support is often requested, but the base version still doesn't have it)

[–] [email protected] 15 points 5 months ago (3 children)

I don't think it's technically impossible - all the information that another site needs to properly interpret some activity is in the JSON that's sent. I get the sense that it might be unrealistic to expect Mastodon to make the necessary changes though. It seems more of a political issue than a technical one.

[–] [email protected] 40 points 5 months ago (5 children)

It's partly an issue of keys. Every fediverse actor has a private key and a public key. When my instance sends this to [email protected], it's signed by my private key, and lemmy.world uses my public key to verify it. When [email protected] sends this comment out, it uses it's own private key to sign it. It can't just re-transmit my comment, because it doesn't have my private key. All it can do is Announce that I've made the comment (and sign the Announce).

Mastodon treats Announces as Boosts, so every post/comment is interpreted as a thing that [email protected] has boosted, so you get all these un-connected posts appearing. I think it's mostly up to Mastodon to remedy.

It works better if a Mastodon actor posts into a Lemmy community, then you get the mix like you imagine. e.g.: https://mastodon.world/@Flash/112095241193510662 (this particular post was crowbarred into Lemmy via [email protected], but it would be the same if the author had done it.)

[–] [email protected] 1 points 5 months ago

One of the reasons it's inconsistent is that Lemmy tries to balance the media it serves locally vs. the media it lets remote hosts serve. Also it's a bit naΓ―ve about image conversion. So if you link to an actual GIF at giphy.com (for example), it works consistently across the most the most platforms if Lemmy leaves it alone. If it doesn't, it'll bring it in and convert it to a WebM file, which not all clients know what to do with. Even if they do though, looping isn't always on by default for video, so the effect of a GIF that relies on looping might be nullified.

It's probably best to focus on the clients with the biggest user-base, rather than try to target them all. For lemmy.world/c/gifs, the most popular posts have been uploaded to imgur.com - which convert most GIFs to MP4s - and the post's author has linked to the inline version at i.imgur.com.

[–] [email protected] 5 points 5 months ago (5 children)

No settings page (as far as I'm aware), but you can use the API to get everything (posts, comments, etc):

step 1: get login token -

curl --request POST \
     --url https://lemmy.ml/api/v3/user/login \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '
{
  "username_or_email": "2br02b",
  "password": "YOUR-PASSWORD"
}
'

step 2: use login token (big long string starting with 'ey') to get data -

curl --request GET \
     --url 'https://lemmy.ml/api/v3/user?username=2br02b&page=1' \
     --header 'accept: application/json' \
     --header 'authorization: Bearer YOUR-JWT'

Increment page number until you have everything. source: https://lemmy.readme.io/reference/get_user

[–] [email protected] 2 points 6 months ago

Edited to account for blahaj updating to 0.19.3 ... hopefully that's the last big instance to change.

It's been about a week since sh.itjust.works and lemmy.world updated, so results from those instances will start appearing again soon.

[–] [email protected] 2 points 6 months ago (1 children)

Voyager has a setting for "No subscribed in All/Local" that does this. It's better on than off, obviously, but it doesn't turn All or Local into some kind of goldmine.

I get the sense that, unless you're willing to do it yourself, feature requests for Lemmy don't have much chance of being realised.

[–] [email protected] 5 points 6 months ago (1 children)

Bit mad, as in a bit strange - e.g. "it's a bit mad to take a single word out of its obvious context for such a desperately cheap shot".

[–] [email protected] 6 points 6 months ago (6 children)

Wait, what? A user posts a thing to a server, and that thing isn't then duplicated to 50 other servers ... yeah, I don't see how that can work.

(I'm just kidding - your site looks neat.)

[–] [email protected] 5 points 6 months ago

[email protected] - yeah, go on then. subbed.

 

From my nginx access log:

your.ip.address - - [21/Feb/2024:06:50:09 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://lemmy.sdf.org"
your.ip.address - - [21/Feb/2024:06:50:09 +0000] "POST /inbox HTTP/1.1" 400 0 "-" "Lemmy/0.19.3; +https://lemmy.sdf.org"
your.ip.address - - [21/Feb/2024:06:50:09 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://lemmy.sdf.org"
your.ip.address - - [21/Feb/2024:06:50:09 +0000] "POST /inbox HTTP/1.1" 400 0 "-" "Lemmy/0.19.3; +https://lemmy.sdf.org"

2 of the entries are "https://lemmy.sdf.org/activities/like/88bc5b6d-f11f-4245-90aa-908e43befe97" being sent twice,
the other two are "https://lemmy.sdf.org/activities/like/437327e5-a262-46bc-8ce7-1c2c5bd440b3" being sent twice

I've reported this problem to other affected servers that I've seen:
the lemmy.ca post suggests the problem was something to do with running multiple containers with the same index number;
the endlesstalk.org post suggests that re-starting the backend containers is a fix
(their answers will likely more sense to you than to me, as I don't run lemmy).

Thanks!

 
13
submitted 6 months ago* (last edited 6 months ago) by [email protected] to c/[email protected]
 

Hi. Just looking at what lemmy.ca sends my server:

From nginx log:

your.ip.address - - [20/Feb/2024:03:48:47 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://lemmy.ca"               
your.ip.address - - [20/Feb/2024:03:48:49 +0000] "POST /inbox HTTP/1.1" 400 0 "-" "Lemmy/0.19.3; +https://lemmy.ca"         
your.ip.address - - [20/Feb/2024:03:48:57 +0000] "POST /inbox HTTP/1.1" 400 0 "-" "Lemmy/0.19.3; +https://lemmy.ca"              

Dumping the JSONs reveals 3 duplicate files, all containing:

"id": "https://lemmy.ca/activities/create/0968bf93-ac05-4178-bf3f-28cdc65fc338"
"actor": "https://lemmy.ca/u/HairyOldCoot"
"object": {
  "id": "https://lemmy.ca/comment/7454502"            
  "content": "That was an episode of Sliders."
  "published": "2024-02-20T03:48:45.810068Z"

These are 3 Creates, not 1 Create and 2 Updates or anything. I've chosen a comment 'cos that's public info, but it's the same for all other activity too (Votes, Deletes, etc).

lemmy.ca isn't alone in this. endlesstalk.org sends everything twice (info posted here), as does lemmy.sdf.org and mander.xyz, but lemmy.ca is the only one I've seen send stuff 3 times. Other instances (e.g. aussie.zone, feddit.nl, lemm.ee, lemmings.world, lemmy.world, programming.dev, reddthat.com, sh.itjust.works, slrpnk.net) don't, but there's nothing obvious like lemmy version numbers to indicate the difference.

Whilst I'd prefer you didn't send me stuff 3 times, I'm mostly mentioning it because I doubt it's good for your own resources to send every activity by every lemmy.ca user out multiple times. Also, the OPs of my community are from Mastodon, so I imagine you're sending them the same message 3 times too ...

 
 
 

After 6 years, project 4K80 (the 4K fan-edit of Empire Strikes Back) finally has some release candidates.

The linked post details why it took so long (compared to 4K77 and 4K83), and the plans for the future.

It's something I'll download when they've worked on it a little more. For now though, Adywan's 'The Empire Strikes Back Revisited' remains my favourite version.

 

Given the shared underlying protocol, I didn't like that if I saw something interesting on Mastodon, and wanted to post it on Lemmy, I'd have to screenshot it and/or re-attribute it to me rather than the original author.

Tails is an experimental community. Instead of announcing just what a Lemmy user has posted, it announces what a Fediverse actor has posted. This means that, so far, it's featured posts from Mastodon accounts like Mr Lovenstein, warsandpeas, George Takei, Low Quality Facts, and other interesting people. Lemmy users have been able to reply to the author, and have also replied to those other Mastodon accounts that responded.

You can see for yourself at [email protected]

(the usual rules apply: if you're the first person on your instance to do this, you'll likely get a blank screen or an error. Wait 10 secs or so, press refresh, and you should have it).

 
 

For Season 1, it took a extra year for the FX ... so maybe this means Season 2 will appear in February next year?

Maybe they were able to get some done during the strikes. Or maybe Andor will get shoved up the priority queue. Either way, it could even be out later this year.

Looking forward to it either way. I'm sure I'll find time to squeeze in an extra rewatch of Season 1 in the meantime ...

view more: next β€Ί