I can strongly recommend the SponsorBlock extention (also available in revanched).
jochem
joined 3 years ago
I was big into downloading before streaming services were a thing. Music streaming is one of the few services that's totally worth my money: no hassle and I rarely have to resort to other platforms to find what I want (very different from video streaming, which totally sucks when it comes to that).
Every country that joined the EU after the 1992 Maastricht treaty has to adopt the euro. Denmark signed that treaty, UK as well, but if they rejoin, they'd more than likely be treated as a new member.
It's bought by Avast. I immediately uninstalled it when I learned about the news. No way that they don't want get a return on investment by e.g. selling your data.
Consent-o-matic is better (actually sets the minimum amount of cookies) and is developed by university employees, whom I trust more.
I would even argue that points, stories and sprints are not things you need. If you go kanban, you don't need sprints. You still need to be producing and you probably want to get a feel for complexity so you can prioritize, but that can be done without points.
Stories are also very scrum specific and you can turn them into whatever format you want. I usually still call them stories, but they're basically just a little card that describes the context (why do want something) and the deliverables (what will be implemented to meet that want).
Markdown is notoriously understandized, so there are lots of unofficial extensions. This is a major downside of markdown, as you cannot trust a renderer to properly show the formatting beyond the basics.
It's still really nice, because of two great features:
- it's super easy to learn. Just look at a few examples and off you go.
- even when it's not rendered, it's still easy to read (which I think contributes to making it easy to learn).
If I would guess, then it has to do with making long lines fit in a window without requiring horizontal scrolling.
Markdown is used a lot in the context of software development. Software code is usually accompanied by a readme, detailing what it does, how to setup your environment for development, how to contribute, etc.
The defacto standard is to write this in markdown. Since it's written in a software development program (an IDE), you don't have text wrapping, meaning lines continue when they don't fit in the window. This is because otherwise the code becomes unreadable. Most code can also be kept to fairly short lines, normally not requiring any horizontal scrolling. However, a long sentence in a readme will easily become much longer than a line of code. So being able to break a line anywhere without having an actual line break in your rendered output is super useful for that.
This is btw how html also behaves. Markdown gets rendered to html.
Have you seen how meta does business?! Talk about a straight up evil corporation.
They don't know how to play nice. They have no interest in playing nice. They're out to make as much money, whatever it takes. They either buy their competitors or try to kill them. The fediverse is not for sale and we need to keep a healthy distance so they don't get a chance to kill us.
Do not federate with meta.
This is top notch cycling infra, even for the Netherlands. You rarely see them this wide.
How do you differentiate between a small instance where 10 votes would already be suspicious vs a large instance such as lemmy.world, where 10 would be normal?
I don't think instances publish how many users they have and it's not reliable anyway, since you can easily fudge those numbers.
I have the same problem with !amsterdam@kbin.social. Tried subscribing and posting from lemmy.ml, but I don't see posts here beyond the one I created (which btw didn't become visible at kbin.social, so it's not working both ways).
Edit: this morning I edited an existing post I made from lemmy.ml to kbin.social. The post showed up with its edit. A bit later I also saw a post from kbin.social show up in lemmy.ml, so I think interacting with content will at some point force federation if it was not working initially. YMMV
view more: next ›
The name of the function, what goes in and what goes out in most cases should be enough to get a good idea on what the function does.
It also helps to make a diagram of how everything ties together. Just boxes and arrows is enough.
When writing your own code, it takes a bit of experience to know when to put something in its own function. It's very obvious when you're replicating code. It's also very common to cut things up when a function gets too big. Look for bits of functionality that you can give a good name.