#3
ひゅうが霄
10/20 16:58:15
💕
4期ここまで凛様の出番が少なすぎるんですけどぉ
Thunderbolt Fantasy 東離劍遊紀4 #3【最新話】 @ABEMA で無料配信中 https://abema.app/8oas
Laeserin
9/5 14:49:46
💕🤔
So, I'd go for #3:
have a pre-selection dialog for the kind pattern (currently 30040/30041s or each kind alone), and have a small drop-down label, above or next to each section, where they can adjust the kind, but that is currently disabled and read-only. (They'll eventually need to be able to add/remove sections, as well, but that's future music.)
30041 alone because they may already have a 30040 and just want to add something new to the list.
30040 alone because they may just want to create an index for things that already exist.
⬆
Laeserin
9/5 14:48:40
💕🤔
Does it necessarily have to be a 30040/41 combination? They will eventually be able to publish wiki pages, too right, or a 30040 that contains a wiki page or another 30040. So they need to be able to define which kind each section should have, with 30040/30041 simply the default.
I'm just thinking that it might make sense to go full modularity in the design, from the start. Also probably need to put a help text above the editing field, that explains where you will define a split. Like, what happens with the content in the preamble? Does it go into a summary tag or does it get a preamble 30041? Is the header where you type in stuff that will end up in optional tags? Which tags will you process and how do they need to type them in? Can they see that information in processed form in the preview?
⬆
Michael J
9/5 13:32:27
💕
I'd like some design feedback on Alexandria.
I'm working on an article editor feature. A screenshot of an early draft is below. The overall goal is to be able to type AsciiDoc-formatted text, preview it in rich text form as it would appear in the Alexandria reader view, then publish it as a cluster of kind 30040 and 30041 events.
My thinking is to break the content down into sections. The content of each section will be published as a kind 30041 note. Each section will be indexed by a kind 30040 note, which will reference the content of the section as a kind 30041 and any subsections as 30040 notes.
Question: How would you like to preview your published events?
I see two options:
1. There are two preview steps: one is a "quick preview" you can see with a click while editing. It doesn't break the content down into 30040 and 30041 events, but it shows you what the nicely-formatted AsciiDoc content would look like. The second preview steps shows the content as it would appear in reader view, after it's been broken down into its constituent 30040 and 30041 events. This preview would have a confirmation dialogue that lets you approve or cancel publishing the events.
2. There's just one preview, and clicking the preview button while editing shows you the content as it would appear in reader view, broken down into 30040 and 30041 events. There would be no separate screen with a confirmation dialogue, and a publish button on the editor page would publish the events.
I'd love to hear people's thoughts!
#asknostr #alexandria #gitcitadel #nostrdev #nostrdesign
hit with a hint of s
9/5 8:07:33
💕
thank you, you are a genius
unfortunately my build gets stuck in here
venice | Logging in to venice...
venice | Using system-wide chromedriver: /usr/bin/chromedriver
and after a (longer) while
venice | Chromium initialization failed: Message: timeout: Timed out receiving message from renderer: 600.000
venice | (Session info: chrome=128.0.6613.113)
venice | Stacktrace:
venice | #0 0x637944f8ed8e <unknown>
venice | #1 0x637944ca5aa0 <unknown>
venice | #2 0x637944c91006 <unknown>
venice | #3 0x637944c90e02 <unknown>
venice | #4 0x637944c8edae <unknown>
venice | #5 0x637944c8f104 <unknown>
venice | #6 0x637944c8d9d1 <unknown>
venice | #7 0x637944c969a2 <unknown>
venice | #8 0x637944c8d7c0 <unknown>
venice | #9 0x637944c90a2c <unknown>
venice | #10 0x637944c8edae <unknown>
venice | #11 0x637944c8f104 <unknown>
venice | #12 0x637944c8d9d1 <unknown>
venice | #13 0x637944c85fff <unknown>
venice | #14 0x637944c8d7c0 <unknown>
venice | #15 0x637944c8d27e <unknown>
venice | #16 0x637944c8cf63 <unknown>
venice | #17 0x637944ca84c9 <unknown>
venice | #18 0x637944c7f787 <unknown>
venice | #19 0x637944c7ee31 <unknown>
venice | #20 0x637944d27a60 <unknown>
venice | #21 0x637944d26f63 <unknown>
venice | #22 0x637944d1a433 <unknown>
venice | #23 0x637944ce5578 <unknown>
venice | #24 0x637944ce652e <unknown>
venice | #25 0x637944f5d916 <unknown>
venice | #26 0x637944f60c47 <unknown>
venice | #27 0x637944f60708 <unknown>
venice | #28 0x637944f610d5 <unknown>
venice | #29 0x637944f4e1ee <unknown>
venice | #30 0x637944f6141f <unknown>
venice | #31 0x637944f38375 <unknown>
venice | #32 0x637944f7e3a5 <unknown>
venice | #33 0x637944f7e586 <unknown>
venice | #34 0x637944f8db4a <unknown>
venice | #35 0x768811a31144 <unknown>
venice |
venice | Traceback (most recent call last):
venice | File "/app/ollama_like_server.py", line 518, in <module>
venice | driver = login_to_venice(username, password)
venice | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
venice | File "/app/ollama_like_server.py", line 99, in login_to_venice
venice | driver = get_webdriver(headless=args.headless, debug_browser=args.debug_browser, docker=args.docker)
venice | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
venice | File "/app/ollama_like_server.py", line 73, in get_webdriver
venice | chrome_options.binary_location = None # Reset binary location
venice | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
venice | File "/usr/local/lib/python3.11/site-packages/selenium/webdriver/chromium/options.py", line 54, in binary_location
venice | raise TypeError(self.BINARY_LOCATION_ERROR)
venice | TypeError: Binary Location Must be a String
⬆
296b93a84a97d4f03eee5869cacc5fb3de7f07ac01d40f92eda62421a344a3a3
⬆
7cfdb97a414bb1c54a83d104a026b4bd1fe14c5e52aac007307202d81722dbe4
moyashamo
8/22 0:20:10
💕
『貨幣の「新」世界史』を読んでいる途中だけど面白い🎙#3
Read BTCのポッドキャスト更新です～
最近読んでる本の紹介です！
#ReadBTC
https://readbtc.substack.com/p/new-history-of-money-interesting