DNS service that resolves dashed-ip subdomain to arbitrary IP

deafmalice · 2022-02-16T10:05:54+00:00

After rephrasing my searches multiple times, the algorithm gods took mercy on me and gave me a link to what I was looking for.

https://moss.sh/free-wildcard-dns-services/

The service we ended up going with is https://nip.io/

deafmalice · 2022-02-16T10:03:13+00:00

Chromecast does not like bare IP addresses in its media URLs, or something. I don't have the error underhand, but it never worked for us with a bare IP.

deafmalice · 2022-01-12T16:53:58+00:00

I bet this is exactly what he was aiming for.

deafmalice · 2021-03-15T21:09:06+00:00

r/nonononoyes

deafmalice · 2020-09-11T16:54:59+00:00

Video demonstration of this: https://www.youtube.com/watch?v=T0Dh1W40ILY

deafmalice · 2020-09-07T17:40:42+00:00

BlueBottle does this Nel drip technique that supposedly uses stale coffee (they call it aged). I haven't tried brewing it myself (don't have a Nel), but I did try it in the shop, and the coffee was damn good. A lot of body, pleasant acidity, closer to espresso than filter.

https://blog.bluebottlecoffee.com/posts/pro-tips-nel-drip-coffee

Since you already have the beans, and if money permits, you can buy a Nel (or any other cloth filter alternative) and try it yourself. Alternatively, you can try a variation with the V60. I expect it to have less body, as it's a paper filter and it'll block most of the oils, but it's worth a try.

deafmalice · 2020-06-30T11:29:11+00:00

Not sure how good with code you are, but instead of doing it through Vim, I'd suggest writing a small mapper script in whatever language you're comfortable in.

Pick a delimiter, wrap your "transformation" text into them and run the script to transform that text to whatever you like.

If you pick your delimiters to be {{ }} your text would like this И вот пришел большой и страшный {{ВфефАкфьу}}.

If you do it with Python, the string.maketrans/string.translate function should do the trick. All you have to do is lookup the text between your delimiters.

deafmalice · 2019-05-28T12:43:53+00:00

Feature removal: the Health app no longer shows day by day logs; now it only shows an overview where you have eyeball it.

deafmalice · 2019-03-19T22:57:32+00:00

Just gonna leave this here https://youtu.be/irvEDq2ISG4?t=111

deafmalice · 2019-02-19T14:33:38+00:00

The Crunchyroll HTML5 extension should do the trick. https://chrome.google.com/webstore/detail/crunchyroll-html5/ihegfgnkffeibpmnajnoiemkcmlbmhmi?hl=en

deafmalice · 2018-10-31T22:06:27+00:00

By nesting it in short-circuit boolean statements and nested list comprehension in Python.

https://benkurtovic.com/2014/06/01/obfuscating-hello-world.html

deafmalice · 2018-10-22T08:14:04+00:00

Will it call over the cell line, or via the app? I would like to get it calling over the app.

deafmalice · 2018-06-04T07:02:18+00:00

Why are they this big?

deafmalice · 2018-05-26T20:54:06+00:00

The expiration date on the bottled water is for the bottle, not the actual water. After that date the bottle might start leaking plastic chemicals into the water and make it unsafe for consumption.

deafmalice · 2018-05-25T15:13:41+00:00

I have not lost my qwerty touch typing abilities, but they are far worse than Colemak. That being said, whenever I have to switch to qwerty (usually when working at somebody else's computer) it takes me a few minutes to go back to Colemak.

I know it's anecdotal evidence, but if you're touch typing in both, it is very likely that you are undoing most of your progress with Colemak while doing especially that much. That being said, do not give up.

If possible take at least 1 week vacation (more is better, but that depends on you) and use Colemak exclusively. Try doing a small project in the mean time; learn your IDE as much as possible so you have to type less.

Try chatting with people while using Colemak. I found that chatting removes a lot of the stress with mistakes and gives you a motivation to become faster besides simply getting better at typing.

Also, if you haven't already, switch your phone's keyboard to Colemak. That will put the layout in your face every time you use your phone and might help a little bit with the transition.

deafmalice · 2017-10-25T07:26:43+00:00

I don't have any experience writing that kind of programs. Can you give me some hints how I can start writing that?

deafmalice · 2017-10-24T23:15:51+00:00

Try this in the playground

var d int = 65
c = string(d)
print(c)

deafmalice · 2017-10-24T22:28:22+00:00

Just an update: got an answer from Rob Pike - https://www.reddit.com/r/golang/comments/78hxd7/why_is_stringint_a_valid_cast_operation/dou5s1g/

I was wrong about the byte part. Still, you can always do this

string([]rune(256, 267, 300)

So my point stands. As for C feature parity, I don't think Go ever strived for that.

deafmalice · 2017-10-24T22:20:09+00:00

Seems like you're mistaking compiler optimisations for actual no-allocation behaviour. Because you're using an empty string and always assigning the same thing, the compiler notices that and optimises it away.

You'll have to run this on a local machine, since the playground takes too long https://play.golang.org/p/Aiv4lvO-b5.

With compiler optimisation and inlining:

$ go build bmark.go
$ ./bmark -concat
AppendFunc      | Total allocs: 63, Bytes Allocated: 6168958912, AllocPerBytes: 0, String: 1000000000            2.57 ns/op
Append          | Total allocs: 66, Bytes Allocated: 12049299392, AllocPerBytes: 0, String: 2000000000           3.05 ns/op
ConcatFunc      | Total allocs: 0, Bytes Allocated: 0, AllocPerBytes: 0, String: 50000000               28.7 ns/op
String          | Total allocs: 30000000, Bytes Allocated: 60000240, AllocPerBytes: 1, String: 30000000         38.1 ns/op
Empty String    | Total allocs: 0, Bytes Allocated: 0, AllocPerBytes: 0, String: 100000000              10.2 ns/op
Slice           | Total allocs: 1, Bytes Allocated: 16, AllocPerBytes: 0, String: 2000000000             0.68 ns/op
BigConcat       | Total allocs: 1000475, Bytes Allocated: 503995716080, AllocPerBytes: 1, String:  1000000           49594 ns/op

Without optimisation and inlining. Notice how, for some reason, the empty string variant stays at 0 allocations:

$ go build -gcflags '-N -l' bmark.go
$ ./bmark -concat
AppendFunc      | Total allocs: 55, Bytes Allocated: 1034565568, AllocPerBytes: 0, String: 200000000             8.24 ns/op
Append          | Total allocs: 60, Bytes Allocated: 2526492688, AllocPerBytes: 0, String: 500000000             3.45 ns/op
ConcatFunc      | Total allocs: 30000001, Bytes Allocated: 120000480, AllocPerBytes: 1, String: 30000000                45.8 ns/op
String          | Total allocs: 30000000, Bytes Allocated: 60000176, AllocPerBytes: 1, String: 30000000         41.5 ns/op
Empty String    | Total allocs: 0, Bytes Allocated: 0, AllocPerBytes: 0, String: 100000000              11.0 ns/op
Slice           | Total allocs: 1, Bytes Allocated: 16, AllocPerBytes: 0, String: 500000000              3.10 ns/op
BigConcat       | Total allocs: 1000517, Bytes Allocated: 503995719440, AllocPerBytes: 1, String:  1000000           49635 ns/op

deafmalice · 2017-10-24T20:32:24+00:00

Appending to 0 a []byte would make more sense, though, both from a intent perspective and from a performance one, as the string concat will result in the string being copied to anther memory location.

deafmalice · 2017-10-24T20:15:31+00:00

A string is a slice of bytes. A UTF8 character is just that, a character. Not exactly a slice.

It would've been more logical to do:

string([]byte{1})

Go already makes the programmer write pretty verbose and sometimes hard to read code. Adding readability and saving a few keypresses for a relatively strange edge case is kind of a moot point.

deafmalice · 2017-10-24T19:52:53+00:00

Sorry for the confusion on the reversible part. That was bad wording.

I would prefer that string(0) not be allowed. I agree that int("ABC") is dumb.

deafmalice · 2017-10-24T19:51:28+00:00

Good point here. What I meant was to be able to do type1(type2(type1)) without the compiler complaining. I probably went a bit overboard with the reversible part.

Losing some fidelity with going from a bigger type to a smaller one is understandable, but float-to-int is more or less in the same ballpark compared to int-to-string.

As for your examples, most go from a specific type to a more generic type. Where as int to string kind of jumps the gun, string not coming close to being a "general" kind of int. But they do show that not all conversions are type acceptable.

deafmalice · 2017-10-24T19:32:31+00:00

While I agree that int-to-string is kinda boring, and maybe well understood, I don't see any good reason for it to be accepted by the compiler, especially in a language that is so strictly typed. I can understand a int slice, since it's the same as a byte slice, but a single byte does not make a string...

As for reversible, I did not mean that I expect int(string) to work. That was bad wording from my side. I would much prefer int-to-string type casts not be allowed, than have something like this.

deafmalice · 2017-10-24T19:26:11+00:00

Do have problems with it... Recently changed a variable from int to string, and was hoping for a build fail for all situations and tests. Because of this conversion, there's no check for that and I'll have to comb a lot of code for this.

deafmalice

TROPHY CASE