infosex.exchange <3

You are probably looking for the infosec.exchange Mastodon instance

This host is mostly for my random stuff, and in little part acts like a well-intentioned placeholder for the typosquatted domain.

Discoverability and Archiving

Currently I'm using this host for saving the items from my own feeds to the Wayback Machine and provide in-links for search engines. I hate that I have to do this, but the non-sense ideology of Mastodon pretty much ruined the search feature for Fediverse as a whole, and this wasn't changed by the fact that they owned their mistake and implemented search eventually.

Yes, I (or anyone else) could do similar things with other peoples published feeds, regardless of the tantrum. No, you can't defederate this, because the process doesn't rely on an instance.

Gluttony Section for Search Engines

[RSS] Be Careful About Your Data on the Internet (Reverse Engineering a Dating App)

https://dozheiny.net/2025/12/17/be-careful-about-your-data-on-the-internet.html

#ReverseEngineering an Iranian dating app
this post | permalink
I wonder how long the "Death to Fix Central!" thread will become by the end of the year over at MIDRANGE-L :D

#IBM
this post | permalink
@G33KatWork I expected a Jazzy/Jowi set, but wasn't disappointed :)
this post | permalink
@BiNotBoth My way of filling out tax forms is that I pretend to be a character in a Franz Kafka novel. It actually becomes entertaining pretty fast!
this post | permalink
uv is a pretty useful band-aid
this post | permalink
@WPalant "makes perfect sense when you are in the business of breaking stuff so people have to pay you for fixing it" - https://dzone.com/articles/why-you-should-avoid-jsf
this post | permalink
@wirepair Thanks I'll take a look. Language is less important, I'm more interested in the API design rn.
this post | permalink
@algernon You mean the HTML parts? I had a similar problem but IME if the CSS is good HTML is very basic, e.g. this is what I have around sugar.css:

https://github.com/v-p-b/sugardocy/blob/main/sugar-template.html
this post | permalink
@algernon @liebach Have you tried sugar.css? It's pretty minimal but customizable.

https://sugar-css.com/
this post | permalink
Is there a #logging library that provides nice interfaces (not N config variables) for both:

- "Reliable" logging, when you want to e.g. flush every message immediately because you are debugging
- "Performant" logging, when you don't want to waste time on I/O?

(what's the proper terminology here?)

There must be of course middle-ground, e.g. I imagine errors should always be recorded reliably in many situations, but I imagine that e.g. auto-tweaking performance on debug log level would be reasonable.
this post | permalink
Next Page