Mac @ mac @programming.dev

Indie game dev

---

Read more

Posts

70

Comments

39

Joined

2 yr. ago

https://boost.lemy.lol <- link to it, doesnt work for instances not connected to it like lemmy.world but theres still ~ 26 major ones

In the past imgbb was used to post CSAM to some communities so some instances remove links to images hosted on it (or I guess ban the user in the instance you were on)

Edit: seems like that was lemmy.world, reach out to their community team and ask to be unbanned if you want your account unbanned, seems like they did that for someone else in the past

The modlogs public to see removed comments. Just a bit difficult to navigate through currently

Instances are the ones hosting the data on their servers + things not having mods can devolve very quickly with things like the nazi bar problem or the scam links that have been getting posted and removed in some communities. This is a different thing than whats in the post though, the post is talking about all communities needing to be fetched manually the first time theyre viewed

Code blocks got updated in 0.19, lemmy.world is still on a 0.18 version

Subreddit had 3 posts within the last month so not that far off tbh

I can look for some post sources to give the community here some more activity

Active is a combination of that and hot but is essentially hard capped at 2 days. Things past that wont show up

Theres the new comments sort which works like that though

When the draw function calls itself it yields control to that new function its calling. When that function ends it takes back control and continues doing what it was doing.

This means all of the for loops in all of the functions will execute. Draw(1) will do the for loop and then return as it hits the end of the function (standard behaviour when you reach the end of a function even if theres no return statement). Then draw(2) will do the for loop as it gets back control now that draw(1) is done and then return, etc. all the way up

All parts of a function are recursive, theres no such thing as a non recursive part

This code has a recursive call (function calls itself) within the function so that has to be taken into account when tracing it

This would make the function execute multiple times so the for loop would end up executing multiple times.

Lets say main calls draw with a height value of 10 (draw(10)). First it sees that n is greater than 0 so it keeps going. Then it calls the draw function with a value of 10 - 1 aka 9. Now its executing in the draw(9) function. Greater than 0 so continues and calls draw(8). etc. all the way down to draw(0) where it sees that n is equal to 0 so returns out of the function due to the return statement.

Now that draw(0) finished executing draw(1) can keep going and goes to the for loop. Here it prints 1 # and then prints a new line (and then returns since it hit the end of the function). Now that draw(1) is done draw(2) can keep going and prints 2 #'s and then prints a new line (and then returns). This keeps going all the way up to the initial draw call, draw(10) which prints 10 #'s and then a new line, returns, and then the main function keeps going but theres nothing after that so it returns and the execution ends.

The effect from coming back after the recursive calls makes it seem like n is increasing but its just different calls to the same function. i is taken into account for but printing the amount of #'s since thats whats within that loop

Letting you know, the download and github links on the git.rela.dev site navbar dont work

Its probably set as a private repository

Yeah active is currently the default sort in programming.dev until scaled sort comes out so commenting helps the most out of everything here

now hit top 10 communities of the day due to the last 2 posts

searching across all of github was made to be logged in then

repository level searching though is relatively recent. Heres the blog post about the change dated in June this year https://github.blog/changelog/2023-06-07-code-search-now-requires-login/

This comment by an employee in the thread also calls out it was in 2023 and links to the blog post

Image Transcription: Meme

[Paneled meme with a brain that gets increasingly glowing]

[The brain is smaller than the skull]

    
if dayOfWeek.name == "Sunday" || dayOfWeek.name == "Saturday"
    weekend = true

  

[The brain is glowing in some areas]

    
if dayOfWeek < 2 || dayOfWeek > 6
    weekend = true

  

[The brain is shooting out rays of light]

    
weekend = !((dayOfWeek - 1) % 6)

  

I am a human volunteer who transcribes posts to improve accessibility on programming.dev and you could be one too! !transcribing@programming.dev

lemmy-ui does the oldest post

but you can get to any other post instead by tapping them in the cross-posted to section

So in this if you tap the title you go to the post on gamedev since its the oldest post. But if you tap game_design at the bottom you go to the post on game_design

no, theyre still two different posts and have different post views outside of the feed. Just one is more prominently shown in the feed while the rest are just links in the cross-posted to section below the post in the feed when it detects that multiple posts have the same url. Comment threads combining would be a separate feature

yeah ill probably have to make an issue on all of their repositories

its pretty much only supported by the main instance web frontends (lemmy-ui and pangora-ui) (been supported on lemmy-ui since before all of the apps were made)

currently recommended in programming.dev to cross post to as many communities as you can to give content to the lower activity communities and since there tends to be a lot of overlap with topics but thats conflicting with current app behaviours

Havent done a check on all of them yet but figure they should all match the behaviour of the main lemmy frontend and its better behaviour to have then to just let it flood

So far I made this post here and opened up an issue in the jerboa repository since those were the two that were reported

Weird, heres the content in it

It is with immense sadness that we must share with you the news of the loss of our friend, our leader, and our mentor, Kris Nóva.

It was Nóva who inspired us to come together to build Hachyderm, whose vision created Nivenly, and whose mission we continue to carry forward. In her working life beyond Nivenly, she has left behind a legacy of professionalism and strength of vision, and we all miss her terribly.

This is very fresh and raw for us in the Nivenly community right now, so we ask for patience while we figure out how we move forward. But move forward we will, as we know that is what Nóva would want.