Skip to content

Add direct URLs wherever applicable#82

Open
purplebar0 wants to merge 1 commit intoBryanLunduke:masterfrom
purplebar0:patch-1
Open

Add direct URLs wherever applicable#82
purplebar0 wants to merge 1 commit intoBryanLunduke:masterfrom
purplebar0:patch-1

Conversation

@purplebar0
Copy link
Copy Markdown

Without removing original URLs, added direct URLs to referenced/relevant posts/publications, unless the original URL is the source itself. Using 𝕏 to denote original Lunduke Journal posts on X, but substituting for something else if need be is easy.

Solves #22, #60 and #79.

For additional context, while Lunduke Journal X posts give editor's insight into why an OS was added to the corresponding column, X is not a libre service, and getting to the actual source requires the extra step of opening the X post first, if the source was linked to begin with.

Other than fixing a typo, nothing else was edited.

**Without removing original URLs**, added direct URLs to referenced posts, unless the original URL is the source itself.
@purplebar0 purplebar0 changed the title Added direct URLs wherever applicable Add direct URLs wherever applicable Apr 23, 2026
@purplebar0
Copy link
Copy Markdown
Author

I'm open to suggestions for changing the label for Lunduke Journal X posts, since it would be trivial to substitute.

I realise that some sources are on X, and that in some cases Lunduke Journal X posts were the sole source, so I thought 𝕏/LJ, or even 𝕏.com/LJ could be more specific than just 𝕏.

@aamaanaa
Copy link
Copy Markdown

he will not merge this. whis whole repo is just abusing the situation to promote him self lol.

@ShobanChiddarth
Copy link
Copy Markdown

Can someone fork this and maintain it please

@solbu
Copy link
Copy Markdown

solbu commented Apr 25, 2026

whis whole repo is just abusing the situation to promote him self lol.

We don't know that, which is why people keep submitting issues and PRs,

@ShobanChiddarth
Copy link
Copy Markdown

Hey @purplebar0 assuming Lunduke will never merge this PR, do you plan to constantly maintain and update your fork of this repo with the developer statements? If that is the case I could just follow your fork and stop following this one. And also enable issues in your fork.

@purplebar0
Copy link
Copy Markdown
Author

Hey @purplebar0 assuming Lunduke will never merge this PR, do you plan to constantly maintain and update your fork of this repo with the developer statements? If that is the case I could just follow your fork and stop following this one. And also enable issues in your fork.

I've been meaning to delete my GitHub account for a long time (anytime now), so I'd rather pass on the torch to someone else.

@ShobanChiddarth
Copy link
Copy Markdown

Hey @purplebar0 assuming Lunduke will never merge this PR, do you plan to constantly maintain and update your fork of this repo with the developer statements? If that is the case I could just follow your fork and stop following this one. And also enable issues in your fork.

I've been meaning to delete my GitHub account for a long time (anytime now), so I'd rather pass on the torch to someone else.

Okay that is fine. If anyone else is willing to take up the responsibility please let me know so I can star that repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants