Tyrubias

It’s not that third party apps want to freeload and therefore have triggered this boycott. A big part of the reason people are upset is the handling of the monetization of the API. The pricing is absurd compared to what similar services charge and the timeline for third parties to switch over is extremely limited. There are many other ways they could have monetized their API without triggering this backlash. For example, they could restrict API usage to people who pay for Reddit Premium. Then, given sufficient time, third parties could rearchitect their workflow to support this.

Also, people are upset at how Reddit management, especially their CEO (Steve Huffman), has handled this transition. The potentially libelous comments regarding Christian Selig (Apollo developer) are just one of the many things people are upset about. The bungled communication and lack of transparency just continues to show that Reddit just wants to squeeze value out of the community without any genuine effort to make it better.

I can’t say for sure whether the boycott will work or not. But I definitely can say that there will be lasting consequences. This is a negative inflection point for Reddit as a community and as a community, especially if they forcibly remod communities that go dark.

The silver lining is that if Reddit does manage to squeeze an IPO out of this, we all have a new stock to short ;)

Uh oh, now I’m paranoid my LastPass export didn’t have everything, and I deleted my account years ago

Seems like it’s down for me too in NYC

How does this compare to something like BlazingSQL[1], which IIRC also does something similar for SQL?

[1] https://blazingsql.com/

Yes, I believe you are intended to duplicate the table once a certain load factor (fraction of elements filled) of your choosing is reached.

For linear probing, this is recommended to keep your probe lengths logarithmic:

https://www.sciencedirect.com/science/article/abs/pii/019667...

Removing elements for a hash table using linear probing is fairly non-trivial. Without using so-called “tombstones” to flag an element as deleted, you essentially have to shift elements up in the table.

Also, your rudeness is really quite unwarranted. If everyone took that attitude, where would the teaching examples ever come from?

I’ve never really understood why standard Unix functions rely on internal global state. For example, strtok():

https://en.cppreference.com/w/c/string/byte/strtok

Was there some reason it was optimal to write these functions this way back in the early days of Unix?

This looks great! I hate it when I have to commit and push a new change for a simple bug. That being said, how does this differ from something like act [1] (besides the fact this is for Gitlab)?

[1] https://github.com/nektos/act

There have been a number of complaints that Google has racially/sexually inappropriate results (i. e. people have reported that searching for "Jews" returns anti-Semitic results), so this could be seen as a way to balance the scales rather than introducing further bias.

Source: https://www.snopes.com/fact-check/found-out-about-jew/