• Activity
  • Votes
  • Comments
  • New
  • All activity
    1. Android aftermarket development and its boring state

      So many ROMs. So many features. But they all look the same. I mean, I love that there are many options, but aren't you bored of going to XDA and finding only ROMs that follow the [9.0] EDGY NAME...

      So many ROMs.

      So many features.

      But they all look the same.

      I mean, I love that there are many options, but aren't you bored of going to XDA and finding only ROMs that follow the [9.0] EDGY NAME IN CAPS formula?

      They all look stock. Android is supposed to be about personalization. Where are the highly customized UIs? Why are all fanboys so scared of breaking the scheme that Material has inforced upon us, and then whine about how Android is inconsistent? I wish that something like MIUI would appear again, like, a ROM made by a no name that ended up making a gigantic empire.

      I wish to see someday another developer, making its own thing.

      Breaking the AOSP UI mold.

      [NOTE] This is reposted from reddit (it was made by me tho) because I wanted to discuss it here.

      15 votes
    2. Anybody use Strikethru?

      I used Bullet Journal for a year, then went back to Org mode with Orgzly on mobile. I find I'm more productive with pen and paper b/c when I see a rabbit hole I can't do nothing but jump into it...

      I used Bullet Journal for a year, then went back to Org mode with Orgzly on mobile. I find I'm more productive with pen and paper b/c when I see a rabbit hole I can't do nothing but jump into it and go right down, and trying to conform to ways app devs' workflows and hack them to behave the way I want cause friction which is for me greater than that of dealing with a meatspace physical notebook. Bullet Journal was nice, but I wonder if Strikethru could be even nicer. I never fully conform to these methods, but they are generally nice starting points to build a custom one, so I generally like starting out with them.

      My use case is, I have four types of tasks: projects, like "study statistics" or "transcribe scans" which can take weeks or months to complete, and sometimes have deadlines; todos which have no specific completion time (e.g. long time shopping lists, books to buy, stuff to check back on later, things to research); tasks that are scheduled for a certain date/time or a range thereof; and lastly tasks that recur on varying intervals, like posting the thread to ~books every other week or completing a particular task that pertains to a project, say reading pages from a book that is relevant to the "study statistics" project. Bullet Journal provided a means for all of this, but the amount of rescheduling and rewriting was inconvenient, and inconvenient is the evil enemy of making habits and getting things done for a fucked up procrastinator like me. When I look at Strikethru, I am not sure if it can handle this, if it's too simple for more complex stuff. So I wonder what you guys do with it. I'd be glad if you could share your workflows and/or advice me on how I could make use of this particular system, or anything else out there!

      Edit: prior art:

      I've commented on both of these talking about how I use a modified Bullet Journal method.

      8 votes
    3. What have you been listening to this week?

      What have you been listening to this week? You don't need to do a 6000 word review if you don't want to, but please write something! If you've just picked up some music, please update on that as...

      What have you been listening to this week? You don't need to do a 6000 word review if you don't want to, but please write something! If you've just picked up some music, please update on that as well, we'd love to see your hauls :)

      Feel free to give recs or discuss anything about each others' listening habits.

      You can make a chart if you use last.fm:

      http://www.tapmusic.net/lastfm/

      Remember that linking directly to your image will update with your future listening, make sure to reupload to somewhere like imgur if you'd like it to remain what you have at the time of posting.

      13 votes
    4. Updates to "Activity" sorting method (the site's default)

      Since it launched, Tildes has always been using "Activity" as the site's default sorting method, which behaves like a classic forum—any new comment in any topic causes it to "bump" back to the top...

      Since it launched, Tildes has always been using "Activity" as the site's default sorting method, which behaves like a classic forum—any new comment in any topic causes it to "bump" back to the top of the list. This has generally worked well overall, and has been a good way to keep threads visible and active over longer periods.

      However, there have been a few issues related to it, such as controversial threads staying at the top of the site for long periods of time, and bickering back and forth between two users causing threads to constantly bump back up to the top even if nobody else is interacting with the topic at all. We haven't had great ways to deal with this so far, and have mostly had to work around it by setting the default time period to "last 3 days" so that threads can't dominate the site indefinitely, or even locking threads to force them to drop off.

      As an attempt at a better solution, "Activity" has now had its behavior changed so that topics will only bump to the top when something "interesting" happens, instead of for every single comment. The exact methods we're using to determine "interesting" will need experimentation and to be adjusted as we see how they work, but initially it's entirely based on comment labels:

      If a comment or any of its parent comments has an active Noise, Offtopic, or Malice label (note: it generally takes at least two users applying the label to make it "active"), the comment will not cause the thread to bump to the top. For example, this means that if a particular comment gets labeled as Offtopic, any replies "below" that comment will no longer bump the thread in the Activity sort. This will also apply retroactively, so if someone posts a new top-level comment, the thread will still initially bump to the top, but if that comment is then labeled as Noise, it will "un-bump" and return back to its previous location in the listing.

      Since this will give us a better way to prevent threads from staying at the top of the site forever, I've also now changed the default time period back to "all time".

      If you'd rather keep the previous behavior and continue having threads always bump to the top when a new comment is posted in them, you can use the new "All activity" sorting method instead. Logged-in users can set it as their default sorting across the site by changing to it on the home page and clicking "Set as default" to the right of the time period dropdown.

      Any feedback is welcome, but these are questions that I'm particularly interested in:

      • Are there cases where the label-based "uninteresting" judgment won't work well? Links to specific examples would be ideal, if possible.
      • What other methods could we use to judge a new comment as "uninteresting"?
      • Should we try triggering bumps from other non-comment events? For example, if a topic is getting voted up a lot, should it bump even if there isn't a new comment?

      As usual, I've also given everyone 10 invites again (and don't worry, I haven't forgotten about turning the visible comment votes back on either, and I'll do that this afternoon, along with posting a thread to discuss it).

      65 votes
    5. Genetic Algorithms

      Introduction to Genetic Algorithms Genetic algorithms can be used to solve problems that are difficult, or impossible to solve with traditional algorithms. Much like neural networks, they provide...

      Introduction to Genetic Algorithms

      Genetic algorithms can be used to solve problems that are difficult, or impossible to solve with traditional algorithms. Much like neural networks, they provide good-enough solution in short amount of time, but rarely find the best one. While they're not as popular as neural networks nor as widely used, they still have their place, as we can use them to solve complicated problems very fast, without expensive training rigs and with no knowledge of math.

      Genetic algorithms can be used for variety of tasks, for example for determining the best radio antenna shape, aerodynamic shapes of cars and planes, wind mill shapes, or various queing problems. We'll use it to print "Hello, World!".

      How does it work?

      Genetic algorithm works in three steps.

      1. Generate random solutions
      2. Test how good they are
      3. Pick the best ones, breed and mutate them, go to step 2

      It works just like evolution in nature. First, we generate randomised solutions to our problem (in this case: random strings of letters).

      Then, we test each solution and give it points, where better solutions gain more points. In our problem, we would give one point for each correct letter in the string.

      Afterwards, we pick the best solutions and breed it together (just combine the strings). It's not bad idea to mutate (or randomize) the string a bit.

      We collect the offsprings, and repeat the process until we find good enough solution.

      Generate random solutions

      First of all, we need to decide in which form we will encode our solutions. In this case, it will be simply string. If we wanted to build race cars, we would encode each solution (each car) as array of numbers, where first number would be size of the first wheel, the second number would be size of the second wheel, etc. If we wanted to build animals that try to find food, fight and survive, we would choose a decision tree (something like this).

      So let's start and make few solutions, or entities. One hundred should be enough.

      from random import randint
      
      goal = "Hello, World!"
      allowed_characters = list("qwertyuiopasdfghjklzxcvbnmQWERTYUIOPASDFGHJKLZXCVBNM ,!")
      
      def get_random_entity(n, string_length):
          entities = []
          for _ in range(0, n):
              entity = ""
              for _ in range(0, string_length):
                  entity += allowed_characters[randint(0, len(allowed_characters)-1)]
              entities.append(entity)
          return entities
      
      print(get_random_entity(100, 13))
      

      Test how good they are

      This is called a "fitness function". Fitness function determines how good a solution is, be it a car (travel distance), animal (food gathered), or a string (number of correct letters).

      The most simple function we can use right now will simply count correct letters. If we wanted, we could make something like Levenshtein distance instead.

      def get_fitness(entity):
          points = 0
          for i in range(0, len(entity)):
              if goal[i] == entity[i]:
                  points += 1
          return points
      

      Crossover and mutation

      Now it's time to select the best ones and throw away the less fortunate entities. Let's order entities by their fitness.

      Crossover is a process, when we take two entities (strings) and breed them to create new one. For example, we could just give the offspring one part from one parent and another part from second parent.

      There are many ways how to do this, and I encourage you to try multiple approaches when you will be doing something like this.

      P:  AAAABBB|BCCCC
      P:  DDDDEEE|FGGGG
      
      F1: AAAABBB|FGGGG
      

      Or we can just choose at random which letter will go from which parent, which works the best here. After we have the offsprint (F1), we should mutate it. What if we were unfortunate, and H (which we need for our Hello, World!) was not in any of the 100 entities? So we take the string and for each character of the string, there is a small chance to mutate it - change it at random.

      F1:  ADDDEBEFGCGG
      F1`: ADHDEBEFGCGG
      

      And it's done. Now kill certain part of old population. I don't know which percentage is best, but I usually kill about 90% of old population. The 90% that we killed will be replaced by new offsprings.

      There is just one more thing: which entities do we select for crossover? It isn't bad idea - and it generally works just fine - to just give better entities higher chance to breed.

      def get_offspring(first_parent, second_parent, mutation_chance):
          new_entity = ""
          for i in range(0, len(first_parent)):
              if randint(0, 100) < mutation_chance:
                  new_entity += allowed_characters[randint(0, len(allowed_characters)-1)]
              else:
                  if randint(0, 1) == 0:
                      new_entity += first_parent[i]
                  else:
                      new_entity += second_parent[i]
          return new_entity
      

      When we add everything together, we get this output:

      Generation 1, best score: 2 ::: QxZPjoptHfNgX
      Generation 2, best score: 3 ::: XeNlTOQuAZjuZ
      Generation 3, best score: 4 ::: weolTSQuoZjuK
      Generation 4, best score: 5 ::: weTgnC uobNdJ
      Generation 5, best score: 6 ::: weTvny uobldb
      Generation 6, best score: 6 ::: HellSy mYbZdC
      Generation 7, best score: 7 ::: selOoXBWoAKn!
      Generation 8, best score: 8 ::: HeTloSoWYZlh!
      Generation 9, best score: 8 ::: sellpX WobKd!
      Generation 10, best score: 9 ::: welloq WobSdb
      Generation 11, best score: 9 ::: selloc WoZjd!
      Generation 12, best score: 10 ::: wellxX WoVld!
      Generation 13, best score: 10 ::: welltX World!
      Generation 14, best score: 10 ::: welltX World!
      Generation 15, best score: 10 ::: welltX World!
      Generation 16, best score: 11 ::: zellov Wobld!
      Generation 17, best score: 11 ::: Hellty World!
      Generation 18, best score: 11 ::: welloX World!
      Generation 19, best score: 11 ::: welloX World!
      Generation 20, best score: 11 ::: welloX World!
      Generation 21, best score: 12 ::: welloX World!
      Generation 22, best score: 12 ::: Helloy World!
      Generation 23, best score: 12 ::: Helloy World!
      Generation 24, best score: 12 ::: Helloy World!
      Generation 25, best score: 12 ::: Helloy World!
      Generation 26, best score: 12 ::: Helloy World!
      Generation 27, best score: 12 ::: Helloy World!
      Generation 28, best score: 12 ::: Helloy World!
      Generation 29, best score: 12 ::: Helloy World!
      Generation 30, best score: 12 ::: Helloy World!
      Generation 31, best score: 12 ::: Helloy World!
      Generation 32, best score: 12 ::: Helloy World!
      Generation 33, best score: 12 ::: Helloy World!
      Generation 34, best score: 13 ::: Helloy World!
      Generation 35, best score: 13 ::: Hello, World!
      

      As we can see, we find pretty good solution very fast, but it takes very long to find perfect solution. The complete code is here.

      Maintaining diversity

      When we solve difficult problems, it starts to be increasingly important to maintain diversity. When all your entities are basically the same (which happened in this example), it's difficult to find other solutions than those that are almost the same as the currently best one. There might be a much better solution, but we didn't find it, because all solutions that are different to currently best one are discarded. Solving this is the real challenge of genetic algorithms. One of the ideas is to boost diverse solutions in fitness function. So for every solution, we compute distance to the current best solutions and add bonus points for distance from it.

      20 votes
    6. What is a scam that people should know about?

      There are, sadly, far too many people and companies out there more than willing to take advantage of people. Fortunately, awareness is usually a good defense. What are some scams that we should...

      There are, sadly, far too many people and companies out there more than willing to take advantage of people. Fortunately, awareness is usually a good defense. What are some scams that we should all know about so that we don't fall for them?

      38 votes