i find it annoying to have to manually change urls to subscribe to a community outside lemmy.world, so i wrote a bookmarklet to quickly switch to the lemmy.world instance
to use, just drag the following code to your bookmarks bar (name it whatever you like), then click it when you want to use it
javascript:(function() {const myInst="lemmy.world";let currUrl=window.location.toString().split("/");let currInst=currUrl[2];currUrl[2]=myInst;let newUrl=currUrl.join("/")+"@"+currInst;window.location=newUrl;})())
readable version:
javascript:(
function() {
// make sure to change this if using on a different instance
const myInst="lemmy.world";
let currUrl=window.location.toString().split("/");
let currInst=currUrl[2];
currUrl[2]=myInst;
let newUrl=currUrl.join("/")+"@"+currInst;
window.location=newUrl;
})
()
Thanks that super useful, especially in places like /c/newcommunities where people (including me) are still unsure how to properly link communities.
also, you should replace
const myInst="lemmy.world";
withconst myInst = window.location.hostname;
, it automatically fetches what instance you’re on.that (unless i’m misunderstanding) isn’t the point of it. it’s made for quickly taking you from e.g.
https://lemmy.ml/c/jerboa
tohttps://lemmy.world/c/jerboa@lemmy.ml
, so it needs a const to know which instance to take you toedit: i guess i could replace
let currInst=currUrl[2];
withlet currInst=window.location.hostname;
but i can’t see a practical difference and so i chose the shorter one
Hello, I just made a new bookmarklet where it automatically transfers all of your subscribed communities to another instance, can be found here
i’ll be honest, i’m not sure what that’s for? is it moving to another account if you want to change your home instance? if so, that’s a good idea, i could add it to the post if you want in case this comment gets buried
spoiler
although i’m not entirely certain using https://github.com/Rob--W/cors-anywhere/issues/301 is a great idea…
Tried this with a throwaway, but it’s broken.
Subscription location has changed.
When corrected, it asks to visit https://cors-anywhere.herokuapp.com/corsdemo to request access. Despite doing so, it never gets past that point.
When/if you fix it, you might give some context about how you’re handling user credentials.