stifle867 10mo ago • 33%
Either (or both) of the two games by this developer: https://play.google.com/store/apps/dev?id=8857752720402747582
stifle867 10mo ago • 100%
You could download a terminal app (termux from f-droid) and run ls > file.txt. You would first want to cd (change directory) to the location you're interested in. This will generate a file.txt with the output of ls (list files command).
stifle867 11mo ago • 92%
Desperate for that blue check money
stifle867 11mo ago • 100%
what were the titles of your posts?
stifle867 11mo ago • 100%
There's like 100-200+ individual contributors to each of the apps. Practically impossible for everyone to agree to relicense especially considering the community reaction to the sale.
stifle867 11mo ago • 100%
Another option would be to build in on a VPS, especially because a lot of them will give free credits and bill by the hour
stifle867 11mo ago • 100%
Why do you say that? Unless they completely rewrite the app from scratch it is not even possible to have a closed-source version of the app. That's what the GPLv3 does.
stifle867 11mo ago • 100%
The same system he was responsible for sending people into as part of his daily work, assuming they were still alive.
stifle867 11mo ago • 33%
Why don't you revert it back to the original structure and instruct makemkv to operate on that directory?
stifle867 11mo ago • 100%
AFAIK the code is all GPLv3 so they won't be able to close-source it.
stifle867 11mo ago • 100%
I was talking about immediately switching. There is enough time to build the apps from source for yourself before they upload their shittified version.
stifle867 11mo ago • 100%
I'm still working on my part 1 😭 string parsing makes me feel so stupid haha. But I'm adamant on coming up with a "nice" solution even if the number of lines aren't minimal. I've got something quite nice at the moment and I anticipate coming in under 100 lines (including whitespace, comments, and formatting).
stifle867 11mo ago • 100%
I haven't been parsing the input string character by character and instead have been parsing into native data structures. It makes the code more verbose but it's how I want to do it. Unfortunately it does mean most of the time coming up with a solution is structuring the data so I'm hoping I come up with a faster way after a few days.
stifle867 11mo ago • 100%
Don't worry China, we super promise not to militarise it 🤞
stifle867 11mo ago • 100%
It's enough to wash away cars and everything else alongside it.
stifle867 11mo ago • 100%
I hate it when they quote a time but no timezone. 10.37PM according to who?
stifle867 11mo ago • 100%
doubly weird suggestion for someone coming from iPhone for the first time
stifle867 11mo ago • 95%
All the code is GPLv3 so it will remain FOSS. There's no need to immediately switch to other apps. You can optionally fork then build the apps for yourself.
stifle867 11mo ago • 100%
As an alternative could he compile your program?
I'm using [this starter kit](https://github.com/mhanberg/advent-of-code-elixir-starter) for the scaffolding so I can simply run `mix test` for the example and `mix d01.p2` to run the solution for my specific data set. I've got the following code that passes p1 completely and the p2 example but not my specific data set. I can't find any bugs but the result fails for being "too high" and I'm really not sure why this is not being accepted. I have the debug output for each step and running through it manually everything seems right to me. Is anyone able to point me in the right direction on what I'm missing? ::: spoiler https://pastebin.com/US8ikNLx ``` defmodule AdventOfCode.Day01 do def part1(args) do args |> String.split(~r/\n/, trim: true) |> Enum.map(&line_calibration_value/1) |> Enum.sum() end def part2(args) do args |> String.split(~r/\n/, trim: true) |> Enum.map(&words_to_numbers/1) |> Enum.map(&line_calibration_value/1) |> Enum.sum() end defp words_to_numbers(string) do numbers = ["one", "two", "three", "four", "five", "six", "seven", "eight", "nine"] String.replace(string, numbers, fn x -> (Enum.find_index(numbers, &(&1 == x)) + 1) |> Integer.to_string() end) end # TODO: doesn't work if the string has no numbers defp line_calibration_value(string) do # remove any non-numeric characters number_from_string = String.replace(string, ~r/[^\d]/, "") calibration_number = [ # first number String.at(number_from_string, 0), # last number, or first number is string has length of 1 String.at(number_from_string, -1) ] calibration_number |> List.to_string() |> String.to_integer() end end ``` :::
Experts believe the volcano could be ready to erupt because, while there were thousands of tremors happening in the week before last, since midnight on Monday, only 165 have been recorded.
pragmaticstudio.com
This only comes around once a year and is a great time to pick up some of their great courses using promo code 2023THANKS. * Elixir & OTP ~~$149~~ down to $89 * Phoenix LiveView ~~$129~~ down to $77 * Full-Stack GraphQL with Phoenix ~~$99~~ down to $59
I got a push notification about how my Pixel just got more useful...yeah ok let's check this out. Turns out no, it's nothing new to me as Android 14 has been out for about a week now. EXCEPT for a new "Immersive View" mode in Google Maps. It's just that I can't help but feel something here is wrong...missing even. If you didn't see it, well I'm pretty sure the bridge doesn't have a huge structural gap in it. How long before Google kills this feature?
I've noticed a small issue with my email client for quite some time now where composing a new email will have several blank lines by default. It's not too much of an issue to simply delete them but hey, maybe no one had pointed this out before! So I filed a bug report only to get this response... basically it's not a bug, its a feature!
I've been a Proton Unlimited subscriber for some time now. I've always had an issue on Proton Mail (Android) when composing a new email it comes pre-filled with a number of blank lines in the body. Definitely a minor issue as it hadn't been fixed for a long time I decided to file a bug report. This was Proton's response: >Currently, this is the expected behavior when you are composing a message through the Proton Mail Android application. > >Please kindly note that other users have expressed their opinion regarding this behavior as well and we have added your vote for this feature improvement request. Basically: it's not a bug, it's a feature! Is there actually anyone out there relying on this "feature"?