Indie game developer 🇨🇦
Working on some games for game jams in my free time
Admin of programming.dev and frontend developer for sublinks
Account has automation for some scheduled posts
Site: https://ategon.dev/ Socials: https://ategon.carrd.co/
Indie game developer 🇨🇦
Working on some games for game jams in my free time
Admin of programming.dev and frontend developer for sublinks
Account has automation for some scheduled posts
Site: https://ategon.dev/ Socials: https://ategon.carrd.co/
The instance finder is built to encourage the use of topic specific instances rather than general use ones so that communities are grouped together better in the same site. The site can then manage all the communities effectively and have the site customized to accomodate them better (and make it feel more like a home for what you like looking at and discussion with others rather than one of many reddit clones)
Categories are mainly so that people are sent to a topic instance that matches their interests. Science goes to mander, programming to p.d, sports to fanaticus, gaming to lemmy.zip, etc.
If youve got some suggestions on how to improve it though let me know, still in progress
Letting you know that if you enter the link into the url box when making a post people can go to it from the post feed. Also the hashtags dont do anything on lemmy (the posts do get federated over to mastodon but mastodon just has a link to the post rather than the post content)
the difference with instances and communities is theres 1k instances and 30k communities. Communities are also created and removed as a much faster pace than instances and there would be different lists per instance (or the same, idk. Just thinking people might get auto subscribed to a bunch of different communities on the same topic, or instead an instance would get ignored)
Going to be making community flairs anyways in pangora so can just add it on
Couple things I think would have to be added for this to work. One would be tagging communities based on the content in them so these subscribe lists dont have to be constantly manually updated and instead can be set on a community level. Then would be handling for taking in the category from the url and saving that so its used later when they sign up (I dont think base lemmy would want to integrate behaviour from the pangora site but it could be integrated into instances running pangora)
Being made primarily for desktop (or mobile as a PWA). Currently it opens up a new page for the post since ive been doing the same page routes as lemmy-ui but that sort of behaviour is neat. Might need to add something like it
It supports more markdown than base lemmy and the alternate uis (code blocks, latex, etc.). Supports hotkeys to do various things. Has a better community list with more info. Mostly the same features as lemmy-ui for non pangora instances apart from these but looks better than lemmy-ui. (pangora is a lemmy soft fork to add features on top of it)
Theres a bunch of stuff itll have added on but only for instances that are running pangora since thats how I get the info about them (planning to add in user tagging, better mod tools, letting communities follow other communities to get their posts in the community feed, letting communities set other communities so that their comments show in the comment section as well if a post is cross posted between them, and a bunch of other stuff)
Only instance thats guaranteed to be running pangora is programming.dev but some others might also use it
I've been working on a new frontend (pangora-ui) thats a similar style in terms of design. Theres some progress over in !pangora@programming.dev. These features can't be put into that though since the frontend is instance specific (lemmy-ui equivalent) and this is for all instances (join-lemmy equivalent)
I recently pushed out an update that shows a preview instead of just sending them to it (with a button where someone can get a new instance for the category). I updated the post to reflect that now
Similar ish to what you said but I've been keeping it at 1 instance shown at a time to stop choice paralysis (but they can see other ones in the category now by getting a new 1 instance)
Letting you know that I pushed an update to the site. Shows a preview of an instance with description, uptime, users amount, communities amount, where its hosted, and software, instead of sending the user to it instantly.
And regional has their own caategory + some other stuff moved around
Bot guidelines for some of the major instances dont allow bot posting unless its been approved by a mod. Also makes more sense for mods to choose what bots to allow in their community rather than response bots being fully allowed everywhere since that can easily get out of hand if a bunch get made
Note the remindme bot uses an allowlist and this community isnt in it, youd have to get your community mods to request it gets added in the repository if you want to use it here
Lemmy itself needs JS to work, wouldnt make sense to limit myself to not using it when the sites im sending people to dont have that restriction. Whats the bloat youre talking about, I can look at it
Sure I can add in some language handling
lemmyf isnt currently listed since its one of the instances that I had no idea existed. Would be under nsfw though
Instances have been added if they have a decent amount of activity and dont break the programming.dev rules (no hate speech, no illegal content, no lolicon). The ones currently here are just basically ones that I know exist but other ones can get added if someone sends me links to them or an issue gets opened on the repository
Sure I could adapt it a bit to do that. I can show info on one and then add in a refresh button to get a new instance in that category or something similar.
And sure I can move regional into their own category
For the background I used tsParticles for the particles, and the gradient behind that uses framer motion to change colors by moving a linear gradient back and forth
Instance is chosen when theres no subcategories for what the user selected
As an example of that when someone first goes to the site they get shown the 10 main categories (technology, gaming, sports, etc.). If they select technology they are then shown the technology subcategories (programming, android, radio, general). if they select general technology that has no subcategories so they are randomly sent to one of the three general technology instances (discuss.tchncs.de, lemmy.sdf.org, or infosec.pub)
A lot of the categories only have one site it sends to but thats fine for now since it still is distributing people to the different sites based on categories
Im not looking at location data at all but in the everything/other category theres countries that can be selected to send the user to country instances
This community got voted to be a collector community for all of the programming content in the instance
So that kind of thing is allowed to be posted here and people in the comments can give people communities to crosspost it to lead them towards that area for future posts
This makes it so users can be lead to other communities in the instance to then post in instead of not knowing where to do so (if theyre in another instance they cant browse our local communities very well in the default UI without needing a third party site)
I can add a way to automate that with a bot in the comments
no way other than mentioning it. Used to use keywords to trigger it but that got removed to comply with bot guidelines (and since it only really detected the messages correctly half the time due to how lemmy provides the comments to it). If you type in part of it it should give you an option to autofill if youre using lemmy-ui
PMs would be ideal but it doesnt work across platforms. I can try to put in a check to see if someones on lemmy and switch to messaging if so but would be a bit since I have a lot of other things to finish up in my backlog of tasks for things like pangora (someone else can feel free to make a pull request though)

thanks, ill look through it for stuff to add to pangora once im done with ludum dare