No, but think of it this way-- creating good bug reports is a valuable type of contribution for open source projects. If you aren't able to fix the issue yourself then it is still appreciated to take the time to write up a good bug report (describe the issue, the expected result, the actual result, and steps to reproduce). So don't let a free account stand in your way π
starshipwinepineapple
joined 8 months ago
I assume Yale isn't broke but idk. Universities are just like any other business where they will cut products that aren't making money or performing as well as others. The article talks about the course needing many teacher assistants to field student questions and hold labs, and that originally these costs were covered by a donation which has now run out.
It also could just be some internal politics and blaming it on financials is the public reason.
But you're not wrong that student tuition costs should theoretically go to the courses they sign up for
CS50 is produced by Harvard and is opencourseware (free) that isn't going away.
What is changing is that Yale won't be offering CS50 courses going forward, seemingly due to funding issues.
Edit: i see now they're talking about private IP, but in case you want to learn about getting a static IP for other things...
Many ISPs will give you a dynamic (changing) IP rather than a static (unchanging) IP. Just check your IP once a week for a few weeks to see if it changes.
There are some services that get around this by checking your ip regularly and updating their records automatically. This is called a dynamic DNS provider (DDNS). I used to use "noip" but since then there are quite a few like cloudflare DDNS.
Beyond that you just would want to make sure your router or whatever device is assigning IPs on your network to give a static assignment to the server. Assigning IPs is handled by a DHCP server and it would usually be your router, but if you have a pihole you might be using that as a DHCP server instead.
Between DDNS and DHCP you can make sure both your external IP and internal IP are static.
Notably codeberg is not a corporate owned like github/gitlab, and you can become a voting member of the nonprofit through donations. Pretty neat imo. I made an account there last year but just got around to creating a repo there for a smaller project. It was straightforward and familiar.
One thing that's holding me back though is the CI is in closed testing but you can request access.
Yes. If you're using lets encrypt then note that they do not support wildcard certs with the HTTP-01 challenge type. You will need to use the DNS-01 challenge type. To utilize it you would need a domain registrar that supports api dns updates like cloudflare and then you can use the acme.sh package. Here is an example guide i found.
Note that you could still request multiple explicit subdomains in the same issue/renew commands so it's not a huge deal either way but the wildcard will be more seamless in the future if you don't know what other services you might want to selfhost.
Agreed, though i do think it's a privacy thing. Many people use privacy and anonymity interchangeably but they are different things.
The options are:
- use a single email. If it is leaked you need to update hundreds of accounts or risk falling for a malicious email
- use a catch-all email and each service gets a separate email, but you can't turn off receiving mail at a specific address unless you use a sieve filter. This doesn't stop people from just guessing random addresses.
- use specific aliases for each service. Idk about this specific project but usually you can turn off receiving mail at an alias. So if a company gets a data breach i just change my email (or close the acct), then i turn off the old alias.
I did the catchall for a few years but have been doing aliases for 5+ now. In the end, the only people/ companies who have my email are the ones I want.
Even has kitty timestamps further down π»
Just some general advice:
- get regular users. Contributors are going to be a subset of users as another commentor mentioned.
- make sure to have a CONTRIBUTING.md and that it is clear/ easy to follow. Some projects will link to a separate wiki from the .md which is fine. But make sure your "first time contributor" instructions are easy to follow to set up whatever dev environment needed. The less clear the documentation then the more motivated the contributors will need to be.
- if you haven't already, make issues with feature requests that you are wanting to add. Include enough details that someone other than you will understand your requirements.
- consider a label you use to signify "great issue for a first time contribution". These should be relatively simple fixes or simple features but give time for someone else to try them instead of completing it right away. Make sure to reference this label in your contribution documentation as a great starting point. If you're able to get someone to do a simple fix then they will have set up the dev environment and may do other future issues.
- advertise that you're looking for contributors. Point out your docs, first time contributor label, and any specific features you want/need help with.
It's also lots of work to make free and open source projects, which is why i say good bug reports are a valuable type of contribution. It is a type of contribution. Imo setting up a free account is the least thing someone can do if they use the project.
And anyone who cares about privacy can use junk data and one time email (this should just be standard practice for anyone that cares and why i didn't mention it). 2fa is a small issue too IMO.
I don't particularly care for github either but if a project is on github then that's how the maintainers are expecting contributions--if you want to help in some way, or want your bug fixed, then you'll need an account or try contacting them in other way.