wclarkey commented 2 years ago

ToDo list:

Cloudflare API integration for automation
Website
Dashboard (??)

MaskDuck commented 2 years ago

also maybe ci checks as well? im a maintainer for a larger project and we had been intergrating ci checks and it works really nice.

wclarkey commented 2 years ago

also maybe ci checks as well? im a maintainer for a larger project and we had been intergrating ci checks and it works really nice.

If i may ask, what are ci checks?

MaskDuck commented 2 years ago

exactly this part.

wclarkey commented 2 years ago

Oh I see! The plan is to eventually have a dashboard so that there is no GitHub PR. But that will need some looking into.

wdhdev commented 2 years ago

dashboards would be a cool idea :D

wclarkey commented 2 years ago

dashboards would be a cool idea :D

Lots planned, exams and college work getting in the way atm tho.

ConnorDoesDev commented 2 years ago

what would the dashboard do? e.x what features would it have

wclarkey commented 2 years ago

what would the dashboard do? e.x what features would it have

Be a more automatic way of managing your subdomain and allow you to edit records delete the domain etc. Probably will have more features such as additional domains other than is-a-good.dev and maybe url forwarding

part1cleth1ef commented 2 years ago

you should prolly use something to keep the records private (I am aware that it is trivial to find the records but that is mostly just bruteforcing and backlinking)

wclarkey commented 2 years ago

you should prolly use something to keep the records private (I am aware that it is trivial to find the records but that is mostly just bruteforcing and backlinking)

This is the idea behind the dashboard. The only problem with making a dashboard is the fact that most of the project's current traffic is completely gone. The main amount of traffic comes from GitHub.

There are both pros & cons to using a dashboard.

Pros:

Safer for data (IP addresses, emails etc)
Easier subdomain management
Possibility for more features
Advertisements and promotions can be impelemented

Cons:

Quite long development time
Possible huge decrese in traffic towards project
More maintainance towards the project
Costs money to host and maintain the hosting server -> this project is already running at a loss because of the domain price.

There are both pros and cons to this. After the college year ends, I will be looking at how this can be implemented and possibly solve most of the cons.

wclarkey commented 2 years ago

We will be working on a website soon anyways, that may bring in more traffic towards the project.

MaskDuck commented 2 years ago

@part1cleth1ef, dns records are not something hideable. theres way to get a dns record publicly.

for example: click me to see twitter.com's dns records

part1cleth1ef commented 2 years ago

@MaskDuck, dns records are actually brute forced generally speaking (most people can't access the zone files) see https://serverfault.com/questions/16101/how-to-list-all-cname-records-for-a-given-domain

wclarkey commented 2 years ago

Theres plently damage someone can do with domain records but it's highly unlikey it will actually happen or fo much damage in our case. Most of our records are CNAME records to GitHub. Meaning that its highly unlikely that the origin server will be affected unless its a large scale ddos. If the record that is being ddosed starts to affect our service we can use Cloudflare's under attack mode. The main idea behind setting up a dashboard is to keep user data safer, this data includes their contact information. We currently include contact information in the records so that we can contact users about any issues or changes with the service. This will be removed and changed when we look towards moving to automating the service and eventually using a dashboard. Even though we are looking at making the service more private, the dns records are still publically available as with any dns record.

wclarkey commented 2 years ago

Some plans have changed about this

Automation will still be implemented.

A dashboard may not be implemented, this is because it will take a lot of maintainance and development time. The registration will be done the same way as most other projects like this with the help of @Tweak4141.

We will also still be implementing a website.

Tweak4141 commented 2 years ago

Automation to do: CI checks and PR automerge. Annual clean of inactive/unreachable websites.

wclarkey commented 2 years ago

Website to do:

Website static page
"Menu" like interface before users reach website, easily redirected towards the repo or website

wclarkey commented 2 years ago

Other automation:

Email validation script (Might not be needed)

wclarkey commented 2 years ago

Website to do:
* Website static page

Done Website accessible from here.

DoctorStrange49 commented 2 years ago

What do we have to write in record type in json file ?

wclarkey commented 2 years ago

What do we have to write in record type in json file ?

Look at the docs please. https://docs.is-a-good.dev And also reply to the comment on your PR

wclarkey commented 2 years ago

Todo:

Repository housekeeping
Org housekeeping
Rewrite readme(s)

ConnorDoesDev commented 2 years ago

closed, opened, reopened my inbox is dying

wclarkey commented 2 years ago

oppsie, im not used to using a trackpad

is-a-good-dev / register

To Do #54

Some plans have changed about this