Question thread #140

[pauamma]

It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.

Comments

[nataraj]

What is the current status of REST-API?

[momijizukamori]

It's at the point where the entries endpoint is just about ready to go, but we really really need to implement proper ratelimiting protections first, which is a level of deep server magic I don't have the knowledge to do myself, so it needs someone higher level than me to do (which is unfortunately like, two people).

[nataraj]

Thank you for your efforts.

we really really need to implement proper ratelimiting protections first, which is a level of deep server magic I don't have the knowledge to do myself, so it needs someone higher level than me to do (which is unfortunately like, two people).

Are there any chances it is ever done?

[cora]

Not a question, more of an FYI/concern: If GoDaddy is providing DNS to Dreamwidth, you may want to check this out if you haven't seen it already: https://www.theregister.com/2025/04/17/zoom_outage_godaddy_blamed/

11 years ago, GoDaddy also used to provide DNS for my employer - after they got one singular complaint about spam for our domain, they yanked the entire domain offline. I suspect (without any kind of evidence, solely going on feelings here) something similar may have happened to Zoom. Either way, if GoDaddy is providing services to Dreamwidth, it's likely worth following up with them on what their policies are around when they'd intentionally turn DNS off for Dreamwidth.

For a dev question:
If I wanted to get started with learning perl in 2025, as someone who does best when trying to solve a problem or puzzle - what would be a good place/way to start?

[pauamma]

As far as I can tell, Dreamwidth exclusively relies on AWS for its name servers.

[pauamma@Pusat-Tasek] ~% drill dreamwidth.org soa
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 24740
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; dreamwidth.org.	IN	SOA

;; ANSWER SECTION:
dreamwidth.org.	900	IN	SOA	ns-715.awsdns-25.net. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
...
[pauamma@Pusat-Tasek] ~% drill dreamwidth.org ns
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 46657
;; flags: qr rd ra ; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 8 
;; QUESTION SECTION:
;; dreamwidth.org.	IN	NS

;; ANSWER SECTION:
dreamwidth.org.	933	IN	NS	ns-715.awsdns-25.net.
dreamwidth.org.	933	IN	NS	ns-422.awsdns-52.com.
dreamwidth.org.	933	IN	NS	ns-1826.awsdns-36.co.uk.
dreamwidth.org.	933	IN	NS	ns-1090.awsdns-08.org.
...

As for your dev question, I think it depends on whether you're more interested on learning "Modern perl" which I hear uses MOO and MOOSE for its object orientation layer, or legacy perl which can date back to the mid-1990s *cough*LiveJournal code still in Dreamwidth*cough*. It also depends on what kinds of puzzles you enjoy solving as vehicles for learning perl. For instance, would you be more interested in fixing issues in existing code, or finding out how to use perl to solve problems of your own?