this post was submitted on 21 Jun 2021

5 points (100.0% liked)

Lemmy

12718 readers

54 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to [email protected].

founded 4 years ago

MODERATORS

[email protected]

5

Github release tracker, a RSS feed bot for Lemmy? (lemmy.juggler.jp)

submitted 3 years ago by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

The user linked seems to be a feed tracker bot for Lemmy. Anyone got an idea where the source-code for that might be?

top 9 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 3 years ago (1 children)

@[email protected] was so kind as to share the code; https://github.com/tateisu/gitHubReleaseWatcher

cc @[email protected] @[email protected]

[–] [email protected] 2 points 3 years ago

awesome, thanks!

[–] [email protected] 1 points 3 years ago (1 children)

Have you tried asking the instance owner?

[–] [email protected] 1 points 3 years ago (1 children)

I speak little Japanese ;)

[–] [email protected] 1 points 3 years ago (1 children)

You can try writing in English and copy paste translation from deepl or google just in case. No harm in trying.

[–] [email protected] 2 points 3 years ago (1 children)

Ofc I am aware that I could do that, but I was rather wondering if anyone knows which bot is used without bothering the instance owner with question like that.

[–] [email protected] 1 points 3 years ago (1 children)

Any progress on that? Might be the time to bother them ;]

[–] [email protected] 1 points 3 years ago (1 children)

Seems like the federation with them is one way only, so I can't actually subscribe to the community from here. Other contact options are not immediately obvious.

[–] [email protected] 2 points 3 years ago

There seems to be a "matrix.juggler.jp" where I would guess one could meet the person/people running this instance, but I've just signed up and bothered them on their lemmy instance, we'll see.