What is Hackers' Pub?

Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.

0
0
3
0
0
3
0
0
5
0
0
0
3
0
0
0
0
0
5
siema czy w FTDL leci jeszcze jakiś pilot? bo mam wrażenie, że nie. napisałem na maila piotr.sikora@ftdl.pl żeby mi w końcu wywalił subskrypcję ale nie dostałem żadnego odzewu, a tydzień później subskrypcja jak przechodziła tak przeszła, i po robocie pewnie będę reklamacje do banku pisać
1
1
0
0
0
0
0
0
1
0
0
0
0

一直很好奇不同人對 ChatGPT 下同樣的 Prompt,會生出一樣的圖嗎?

Cozy room corner, eye-level. Golden sunlight from left blinds, striped shadows. Five-drawer wooden cabinet against wall, black and white cat sleeping on top. Orange tabby and calico play-fighting in front, exaggerated paws, dynamic pose, comic motion lines. Japanese light novel anime style, soft pastel colors, clean lineart, cel shading, warm atmosphere, vertical, high detail.

有沒有人可以幫我用這段試一下,我的GPT生成的圖長這樣⬇⬇⬇

0
0
0
1
0

낮 동안 우리를 활기 있게 하신 저의 주님, 날아다니는 스파게티 괴물 님,
당신과 함께 있으리니, 자는 동안도 지켜 주시어 편히 쉬게 하소서.

"7. 저희 마음에 고요한 성면의 숨결을 불어넣으시어, 두려움 없이 잠들게 하소서."

🍝 날아다니는 스파게티 괴물 님께서 여러분과 함께.
😋 또한 주교의 면발과 함께 하소서.
🍝 기도합시다.
저의 주님, 날아다니는 스파게티 괴물 님, 이 밤을 편히 쉬게 하시고, 거룩한 죽음을 맞게 하소서.

2026-02-25T00:05:20+09:00


0
0
0
0
1
0
1
0
0
0
0
1
0
0
0
0

RE: mamot.fr/@rigo/116122496081934

Actually, let's talk for a moment about this pernicious falsehood that you can "just interpret it as JSON."

1. The specs are different. A simple example of this is the matter of whether lists are sorted. This comes directly from the test suite: "JSON objects are compared member by member without regard to the ordering of members within the object." In standard JSON, [1,2,3] is an ordered list, that is only true in JSON-LD if the list is marked that way.

2. Variance in parser behavior. A JSON-LD parser is supposed to drop things that are not defined in the @'context, but JSON has no such limit. This means that with a slight difference in the @'context a field may be dropped by some parsers and included by others, _even if the field is theoretically supported by the underlying software_.

3. JSON-LD does not have a great way of representing arbitrary precision numbers. xsd:integer and xsd:double are the kinds of things you have.

Unless you define one, of course, but that brings us to

4. The context can rewrite the specification. Does "foo:bar" have meaning? In a well-formed JSON object backed by JSON Schema or Open API I can give you the answer that immediately. In a JSON object serialized from a protobuf following those standards I can give you a direct, clear, unequivocal meaning in the vast majority of cases.

The only times I can do that with JSON-LD are IF I HAVE PARSED THE CONTEXT, WHICH POSTS LIKE THIS TELL ME I DON'T NEED TO DO.

This again brings us back to variant parser behavior. If _your_ parser reads it as JSON-LD and _mine_ does not, we are NOT READING THE SAME OBJECTS in a way that can be controlled and manipulated maliciously.

5. Absolutely inane use of sum types that aren't even required to be LABELED sum types means that you may get a different payload structure entirely and have no way of interpreting it UNLESS you are using JSON-LD.

If an object can be a URI OR an object OR a value OR a list of URIs etc then validation requires checking ALL of these.

1/

@hrefnaHrefna (DHC) What I keep wondering is, would it be possible to define a subset of JSON-LD which has less flexibility— for example, perhaps more things are defined by convention, or the things the context may define are more limited in some way which lowers the processing time— but which is still prefixed with enough information that a compliant JSON-LD parser derives the same object?

0
0
0