Oriel Jutty :hhHHHAAAH:

Indoor European. Knows #regex. Writes #code (in #C or #Haskell or #Perl or #JavaScript or #bash). Not a fan of racism, sexism, transphobia, or bigotry. Almost done thinking.

Kompatibel mit handelsüblichen Klemmbausteinen.

Exit vim: :q
Verified: https://infosec.exchange/@barubary
Pronouns: he, his, him, him
Goose value: 71
OPSEC: 100%

Public Key

npub1d58c27jepmfanyu9cvvjghw2uu0auj2xf8g3lapswf590hg4q8ps9rwmvf

NIP-05 Address

barubary_at_infosec.exchange@momostr.pink

Profile Code

nprofile1qqsx6ru90fvsa57ejwzuxxfyth9ww877f9ryn5gl7sc8y6zhm52srscprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmnt88hymt

Publishing to

relay.momostr.pink

Author Public Key

npub1d58c27jepmfanyu9cvvjghw2uu0auj2xf8g3lapswf590hg4q8ps9rwmvf

Show more details

Last Notes

2026-08-11 12:36:08 UTC

- reply

Out of interest, does your screen reader stumble over things like emoji, quotation marks, and all-caps words in alt text?

2026-08-04 07:30:09 UTC

- reply

lol wut "This guess [by Gemini] was non-hallucinated and plausible, but [...] wrong."

2026-07-22 17:47:13 UTC

Liability Laundering Machine

2026-06-17 06:11:43 UTC

- reply

https://en.wikipedia.org/wiki/Archive.today#Attack_on_Gyrovague_and_Wikipedia's_restrictions
> On 20 February 2026, the English Wikipedia banned all links to archive.today, citing the DDoS attack and evidence that archived content was tampered with
What you read on archive.is may not be the original article.

2026-06-12 10:22:53 UTC

- reply

> making a huge difference in software development and cyber security right now
That may be true, but does not necessarily imply the effects are positive.

2026-05-22 05:22:44 UTC

- reply

https://media.infosec.exchange/infosec.exchange/media_attachments/files/116/616/546/014/394/098/original/de13fc1e5bbd4f37.png

2026-03-31 06:42:36 UTC

- reply

> But I'm sure that article is good advice for people who... find "letting the invoking system leak into the domain model" a very sensible phrase they completely understand. Haskell programmers...
:sa_confused:
That's not even Haskell jargon. (And it is the first sentence in a section that fully explains what the author means, including sample code.)

2026-02-12 16:40:59 UTC

- reply

id (1 + 2::Int)
is not the same as id $ 1 + 2::Int. <code>a = id (1 + 2::Int) -- parses as a = id ((1 + 2) :: Int) </code>
but<code>a = id $ 1 + 2::Int -- parses as a = (id $ (1 + 2)) :: Int </code>
That is, one version has the type annotation on the argument 1 + 2, the other version has it on the result of the function application. This makes no practical difference with id, but most functions aren't id.
(Why? Because $ isn't special syntax; it's just an operator. On the other hand, :: is special syntax that grabs as much expression context to the left as possible.)

2026-01-11 16:54:13 UTC

- reply

https://github.com/SwiftOnSecurity/sysmon-config/pull/105

2025-11-04 19:38:12 UTC

- reply

A cyber group, you say? A/S/L?

2025-08-18 10:04:38 UTC

- reply

you mean https://en.wikipedia.org/wiki/Joose_(framework) ?

2025-08-06 10:06:26 UTC

- reply

This isn't even Microsoft employees. He's talking to developers and Github users in general.

2025-07-05 06:22:20 UTC

"Tiere (ohne Hund / Katze)"
#FotoVorschlag
https://media.infosec.exchange/infosec.exchange/media_attachments/files/114/799/181/506/013/517/original/8992114403c335f9.jpg

2025-07-03 07:07:48 UTC

- reply

OK, I won't mention _|_ for bottom.

2025-06-25 16:33:53 UTC

"Lichtreflektion"
#FotoVorschlag
https://media.infosec.exchange/infosec.exchange/media_attachments/files/114/744/961/459/110/076/original/fd3ccbf47801a3af.jpg

2025-06-23 04:05:10 UTC

- reply

https://en.wikipedia.org/wiki/X-Face

2025-06-21 08:37:55 UTC

- reply

Wäre natürlich cool, wenn @npub12dn…0hjt auch funktionieren würde.

2025-06-21 07:46:17 UTC

- reply

"Geometrie im Alltag"
#FotoVorschlag
https://media.infosec.exchange/infosec.exchange/media_attachments/files/114/720/238/971/314/787/original/e60356f7a8de2c19.jpg

2025-06-21 06:49:23 UTC

- reply

"Geometrie im Alltag"
#FotoVorschlag
https://media.infosec.exchange/infosec.exchange/media_attachments/files/114/719/989/849/977/749/original/3c8a1e719a978c84.jpg

2025-06-21 06:30:19 UTC

"Geometrie im Alltag"
#FotoVorschlag
https://media.infosec.exchange/infosec.exchange/media_attachments/files/114/719/933/684/766/922/original/02bbe5a350c0af77.jpeg

2025-06-05 06:56:52 UTC

Farbe: Komplementärfarben
#FotoVorschlag
https://media.infosec.exchange/infosec.exchange/media_attachments/files/114/629/439/935/582/305/original/e14c2b5c1c082887.jpg

2025-04-26 03:15:30 UTC

- reply

We are [Dancer2](https://metacpan.org/pod/Dancer2 ).

2025-01-14 20:45:32 UTC

- reply

If you tell a regex engine to find all matches, they normally don't overlap; i.e. each search takes off where the previous match stopped. So for a pattern of [0-9]* against the string 30-45 I'd expect four matches: The two digits at offset 0 (30 at the beginning of the string), the zero digits at offset 2 (, just before -), the two digits at offset 3 (45, after -), and the zero digits at offset 5 ( at the end of the string).
(None of the matches can contain - because [0-9] only matches digits.)

2025-01-14 20:15:38 UTC

- reply

A regex always finds the leftmost match. Your first regex, [0-9]*, can match at offset 0 in >335 because * means "0 or more of the preceding thing", so it can match all 0 digits before >. On the other hand, [0-9]{1,3} requires at least one digit to match, so the first location where it can succeed is at offset 1, matching all three available digits.

2024-11-27 18:01:31 UTC

- reply

... wait, you're not sluttymayo?

2024-11-25 21:42:58 UTC

- reply

5.8? I can't wait!

2024-11-01 07:52:46 UTC

- reply

But then I'd have to create a gitlab account and, worse, write PHP. :-(

2024-11-01 07:24:52 UTC

- reply

Some bizarre code in there.<code>in_array( $inbox_message["actor"], $followers_ids ) ? $from_follower = true: $from_follower = false; </code>
Removing the duplicated code, this is just<code>$from_follower = in_array( $inbox_message["actor"], $followers_ids ) ? true : false; </code>
And ... ? true : false is redundant, leaving:<code>$from_follower = in_array( $inbox_message["actor"], $followers_ids ); </code>

2024-10-30 20:17:00 UTC

- reply

Yes.
Here's my thoughts so far. (All code is untested.)
You need something like foreign import ccall "wrapper" mkCallback :: IO () -> IO (FunPtr (IO ())) to turn Haskell actions into C callbacks.
Basic usage (not exception safe):<code>do p <- allocateData onDone <- mkCallback (deallocateData p) c_send p onDone </code>
(Also, this leaks onDone, which should be freed using freeHaskellFunPtr when no longer needed.)
As for how to implement allocateData and deallocateData, you could straight up use malloc, copyBytes, and free from Foreign.Marshal.
Things get a bit more interesting if you don't want to make a copy, but use the underlying storage of a ByteString directly. Using Data.ByteString.Internal, you can crack open the ByteString and get the underlying ForeignPtr.<code>case bs of BS fptr _ -> withForeignPtr fptr $ \p -> do onDone <- mkCallback (touchForeignPtr fptr) c_send p onDone </code>
Placing touchForeignPtr in the callback should ensure that the foreign pointer stays alive until the callback is invoked.
It may also be possible to play games with useAsCStringLen and threads, preventing the inner action from returning until an MVar is filled (which would be done by the callback).

2024-10-30 15:49:48 UTC

- reply

I'm having trouble picturing what you're talking about from this description. What is the function declaration and what does it mean for a "user" to "hold" a pointer?

2024-10-25 10:06:47 UTC

- reply

Simplified:<code>import Servant ((:<|>) (..)) </code>
More simplified:<code>import Servant.API.Alternative </code>