Constellations from Around the World (2019)
9 by fanf2 | 1 comments on Hacker News.
Wednesday, 31 July 2024
Tuesday, 30 July 2024
Hungary visa move stokes EU fears of Russian espionage, letter shows
from Yahoo News - Latest News & Headlines https://ift.tt/JVS6WxK
Monday, 29 July 2024
New top story on Hacker News: Can the moon influence human health? New research
Can the moon influence human health? New research
17 by sabrina_ramonov | 2 comments on Hacker News.
17 by sabrina_ramonov | 2 comments on Hacker News.
Sunday, 28 July 2024
Saturday, 27 July 2024
Trump Declares Outrageous Reason He Won't Pronounce 'Kamala' Correctly
from Yahoo News - Latest News & Headlines https://ift.tt/8lrYRxn
Friday, 26 July 2024
Thursday, 25 July 2024
Wednesday, 24 July 2024
Tuesday, 23 July 2024
New top story on Hacker News: Show HN: Briefer – multiplayer notebooks with schedules, SQL, and built-in LLMs
Show HN: Briefer – multiplayer notebooks with schedules, SQL, and built-in LLMs
21 by lucasfcosta | 7 comments on Hacker News.
Hi HN! We're Lucas and Lucas from Briefer and we're building better notebooks. Our notebooks are kind of a mix between Notion and Jupyter with extra features, like the ability to schedule notebooks, turn them into dashboards and apps, and write SQL queries whose results turn into data frames automatically. We're building better notebooks because we think they're a great idea poorly executed - for three reasons. The first problem with notebooks is that they're difficult to share. Non-technical people don't want to download docker containers and install Python libraries to see what the data team is doing. Then, the data team takes screenshots of their work and pastes them somewhere else. The issue with this approach is that the data gets stale, and the output is not interactive, so it's difficult to get feedback and iterate. The second problem with notebooks is that they get too messy too quickly. One morning you have 10 blocks, and by the end of the day you have 192, but only six of them are meant to be seen by other people and the rest is just you jiu-jitsuing with the data. Consequently, even if non-technical people could see your work, they'd have a hard time figuring out what's happening. The third problem with notebooks is that it takes too much work to do simple things like when you want to query a database. In that case, you need to have the database credentials in your machine, and you have to write a bunch of wrapper code. Calling APIs, plotting simple graphs, and adding interactive components is equally as annoying. We're solving the sharing problem by bringing notebooks to the cloud (so you can schedule them) and using CRDTs to manage their state. Whenever you edit a Briefer notebook, we reconcile that using Yjs, and then propagate it to everyone else who's editing that notebook. Regarding compute instances, each workspace gets its own, and we provision them on demand. By the way, we manage the execution state of your blocks using Yjs too, which makes it much more stable and responsive across all clients. When you click "run", for example, we don't immediately send a request to run the block. Instead, we change the block's state to "execution-requested". Then, the observers in the back-end react to the change and update the block's state with the results. In other words, the front end and the server communicate with each other through the notebook's state. One side updates the state, and the other reacts. To solve the "messiness" issue, we've invested a lot of time in designing clean notebooks and allowing you to organize blocks in ways that make them more presentable. In Briefer, you can group multiple blocks into tabs and decide which blocks appear in the published version of your notebook. That way, you can hide all that data wrangling and focus on results. We also know that a vertical format is not always the best way to display results, so you can use your notebook's outputs to build dashboards too. Last but not least, we're reducing friction in simple tasks like plotting graphs and querying databases. In Briefer, you can plot graphs using a click-through interface, and if you need to plot something more intricate like a Sankey chart there's also a built-in AI assistant that you can prompt to generate code. When it comes to queries, we turn their results into dataframes automatically, and you can use SQL to query uploaded files too (we use DuckDB for that). We're really happy we get to show this to you all, thank you for reading about it! Please let us know your thoughts and questions in the comments.
21 by lucasfcosta | 7 comments on Hacker News.
Hi HN! We're Lucas and Lucas from Briefer and we're building better notebooks. Our notebooks are kind of a mix between Notion and Jupyter with extra features, like the ability to schedule notebooks, turn them into dashboards and apps, and write SQL queries whose results turn into data frames automatically. We're building better notebooks because we think they're a great idea poorly executed - for three reasons. The first problem with notebooks is that they're difficult to share. Non-technical people don't want to download docker containers and install Python libraries to see what the data team is doing. Then, the data team takes screenshots of their work and pastes them somewhere else. The issue with this approach is that the data gets stale, and the output is not interactive, so it's difficult to get feedback and iterate. The second problem with notebooks is that they get too messy too quickly. One morning you have 10 blocks, and by the end of the day you have 192, but only six of them are meant to be seen by other people and the rest is just you jiu-jitsuing with the data. Consequently, even if non-technical people could see your work, they'd have a hard time figuring out what's happening. The third problem with notebooks is that it takes too much work to do simple things like when you want to query a database. In that case, you need to have the database credentials in your machine, and you have to write a bunch of wrapper code. Calling APIs, plotting simple graphs, and adding interactive components is equally as annoying. We're solving the sharing problem by bringing notebooks to the cloud (so you can schedule them) and using CRDTs to manage their state. Whenever you edit a Briefer notebook, we reconcile that using Yjs, and then propagate it to everyone else who's editing that notebook. Regarding compute instances, each workspace gets its own, and we provision them on demand. By the way, we manage the execution state of your blocks using Yjs too, which makes it much more stable and responsive across all clients. When you click "run", for example, we don't immediately send a request to run the block. Instead, we change the block's state to "execution-requested". Then, the observers in the back-end react to the change and update the block's state with the results. In other words, the front end and the server communicate with each other through the notebook's state. One side updates the state, and the other reacts. To solve the "messiness" issue, we've invested a lot of time in designing clean notebooks and allowing you to organize blocks in ways that make them more presentable. In Briefer, you can group multiple blocks into tabs and decide which blocks appear in the published version of your notebook. That way, you can hide all that data wrangling and focus on results. We also know that a vertical format is not always the best way to display results, so you can use your notebook's outputs to build dashboards too. Last but not least, we're reducing friction in simple tasks like plotting graphs and querying databases. In Briefer, you can plot graphs using a click-through interface, and if you need to plot something more intricate like a Sankey chart there's also a built-in AI assistant that you can prompt to generate code. When it comes to queries, we turn their results into dataframes automatically, and you can use SQL to query uploaded files too (we use DuckDB for that). We're really happy we get to show this to you all, thank you for reading about it! Please let us know your thoughts and questions in the comments.
New top story on Hacker News: Ask HN: I built a Yubikey-based domain controller. Is it sellable?
Ask HN: I built a Yubikey-based domain controller. Is it sellable?
17 by elevation | 7 comments on Hacker News.
I once worked in R&D where our competitive advantage was in keeping our customer relationships and intellectual property private, so we kept everything on-prem. No cloud, no SaaS, no WFH. In my own SMB, I still self-host git, CI, chat, etc. I love the privacy and control, but I also needed to open these services to remote workers without exposing them to the world. So I built an appliance to protect my internal web apps by requiring user/pass+yubikey at multiple layers of the stack: L3 (p2p vpn), L4 (mTLS), and L7 (OIDC). The appliance is self contained (VPN, LDAP, NTP, CA, OIDC), like a classic domain controller, and it keeps servers safe from any users without an authorized hardware key. I'd love to bundle this with an admin panel and sell it, but I forsee problems connecting with the right market: * Clients who have meaningful IT budgets will require inter-operation with their legacy domain controllers. This means I won't have an MVP without major changes and lots of testing. It also puts my own product at risk: if Microsoft doesn't want to support my integrations, they can disable my product with a software update. * Clients who are too small to have lots of legacy IT requirements will have small budgets and require lots of support. Some of these clients will grow larger, but this is a long game. I would love to support these clients but don't want to die for lack of revenue in the short term. How would you sell what I've built?
17 by elevation | 7 comments on Hacker News.
I once worked in R&D where our competitive advantage was in keeping our customer relationships and intellectual property private, so we kept everything on-prem. No cloud, no SaaS, no WFH. In my own SMB, I still self-host git, CI, chat, etc. I love the privacy and control, but I also needed to open these services to remote workers without exposing them to the world. So I built an appliance to protect my internal web apps by requiring user/pass+yubikey at multiple layers of the stack: L3 (p2p vpn), L4 (mTLS), and L7 (OIDC). The appliance is self contained (VPN, LDAP, NTP, CA, OIDC), like a classic domain controller, and it keeps servers safe from any users without an authorized hardware key. I'd love to bundle this with an admin panel and sell it, but I forsee problems connecting with the right market: * Clients who have meaningful IT budgets will require inter-operation with their legacy domain controllers. This means I won't have an MVP without major changes and lots of testing. It also puts my own product at risk: if Microsoft doesn't want to support my integrations, they can disable my product with a software update. * Clients who are too small to have lots of legacy IT requirements will have small budgets and require lots of support. Some of these clients will grow larger, but this is a long game. I would love to support these clients but don't want to die for lack of revenue in the short term. How would you sell what I've built?
Monday, 22 July 2024
Sunday, 21 July 2024
Saturday, 20 July 2024
Friday, 19 July 2024
My parents got me whole life insurance for nearly $700 a month when I was 17 — am I completely screwed?
from Yahoo News - Latest News & Headlines https://ift.tt/LbKIWdz
Thursday, 18 July 2024
Wednesday, 17 July 2024
Dollywood forced to close for the day an hour after opening. Here’s why
from Yahoo News - Latest News & Headlines https://ift.tt/kUbePHY
Tuesday, 16 July 2024
Monday, 15 July 2024
Cathie Wood says she wouldn't have sold Nvidia stake 'had we known that the market was going to reward it'
from Yahoo News - Latest News & Headlines https://ift.tt/xXL6PHJ
Sunday, 14 July 2024
Saturday, 13 July 2024
Chicago exhibition center modifying windows to prevent bird strikes after massive kill last year
from Yahoo News - Latest News & Headlines https://ift.tt/yuxtEan
Friday, 12 July 2024
Thursday, 11 July 2024
Wednesday, 10 July 2024
Tuesday, 9 July 2024
Boone County assistant fire chief drowns while rescuing people from floodwaters
from Yahoo News - Latest News & Headlines https://ift.tt/O34fSlA
Monday, 8 July 2024
Sunday, 7 July 2024
Saturday, 6 July 2024
Friday, 5 July 2024
Thursday, 4 July 2024
New top story on Hacker News: Ask HN: Who Wants a Penpal?
Ask HN: Who Wants a Penpal?
61 by sdsd | 14 comments on Hacker News.
Surely I'm not the only lonely computer nerd here :) If you're interesting in finding a penpal, post in this thread with the following format: alias: interests: language(s): link to something you think is cool: contact info: To prevent spambots from scraping this like they do the hiring threads, please obscure your contact info.
61 by sdsd | 14 comments on Hacker News.
Surely I'm not the only lonely computer nerd here :) If you're interesting in finding a penpal, post in this thread with the following format: alias: interests: language(s): link to something you think is cool: contact info: To prevent spambots from scraping this like they do the hiring threads, please obscure your contact info.
Wednesday, 3 July 2024
China's BYD posts 21% jump in quarterly EV sales, closes gap with Tesla
from Yahoo News - Latest News & Headlines https://ift.tt/V28LpjY
Tuesday, 2 July 2024
Monday, 1 July 2024
New top story on Hacker News: Show HN: Edna, note taking app for developers
Show HN: Edna, note taking app for developers
12 by kjksf | 2 comments on Hacker News.
I took a small break from coding SumatraPDF and wrote a note taking application that is perfect for me: https://ift.tt/thpRJO4 Edna is a note taking app for developers and power users. A cross between Obsidian and Notational Velocity. Markdown, plain text, code, works in browser so no installation required, private (notes are stored in your browser or disk) and secure (can encrypt notes with a password). The story so far. I was always attracted to editors with minimalistic UI, like https://mak.ink/ , simplenote, Notational Velocity. I like having most of the screen estate for writing because writing and editing is what note taking apps are for. But: most of them are very thin on features and UI. I saw Heynote and it was one of those minimalistic writing UIs with not many features. I liked their concept of dividing notes into blocks so I forked Heynote and started coding. The goal was to combine writing-oriented, minimalistic main UI while also providing on-demand UI for features and efficient operation. Things like context menu, type-down note switcher, command palette, quick access shortcuts, plenty of keyboard shortcuts. Another goal was privacy and security. The notes never leave your computer and can be encrypted with a password. It also makes the code simpler because I don't need any backend storage, user accounts and auth etc. Sadly, only Chrome and Edge provide the necessary file system api, on other browser you can only store notes in local storage, which means no sharing between computers or accessing the notes with other software. 40 working days and 528 commits later, here's what I've added: * added support for multiple notes * ability to store notes on disk * and if you store notes in a directory managed by DropBox, OneDrive etc., you get sharing of notes between computers * Ctrl + P: UI for switching between notes, creating new notes, deleting notes, inspired by Notational Velocity * Ctrl + Shift + P: command palette like in vs code * context menu to access frequently used functionality * Ctrl + E to open note from history (list of recently opened notes) * ability to assign Alt + 0 ... Alt + 9 quick access shortcuts * ability to encrypt notes with a password * export all notes to a .zip file * automatic, daily backup of notes to a .zip file (optiona, see Settings) * Ctrl + B to navigate between blocks * re-designed Settings UI * added ability to execute Go blocks * support Svelte and Vue in code blocks * ported the UI code from Vue to Svelte 5, just because I could * converted from desktop app to run in the browser (Ctrl is on Windows, on Mac it's ⌘). I've been using it daily while working on it. 94 notes and counting. I still have ideas for improvements but it has all the core features for productive work. The app: https://ift.tt/thpRJO4 The code: https://ift.tt/QApaIEF
12 by kjksf | 2 comments on Hacker News.
I took a small break from coding SumatraPDF and wrote a note taking application that is perfect for me: https://ift.tt/thpRJO4 Edna is a note taking app for developers and power users. A cross between Obsidian and Notational Velocity. Markdown, plain text, code, works in browser so no installation required, private (notes are stored in your browser or disk) and secure (can encrypt notes with a password). The story so far. I was always attracted to editors with minimalistic UI, like https://mak.ink/ , simplenote, Notational Velocity. I like having most of the screen estate for writing because writing and editing is what note taking apps are for. But: most of them are very thin on features and UI. I saw Heynote and it was one of those minimalistic writing UIs with not many features. I liked their concept of dividing notes into blocks so I forked Heynote and started coding. The goal was to combine writing-oriented, minimalistic main UI while also providing on-demand UI for features and efficient operation. Things like context menu, type-down note switcher, command palette, quick access shortcuts, plenty of keyboard shortcuts. Another goal was privacy and security. The notes never leave your computer and can be encrypted with a password. It also makes the code simpler because I don't need any backend storage, user accounts and auth etc. Sadly, only Chrome and Edge provide the necessary file system api, on other browser you can only store notes in local storage, which means no sharing between computers or accessing the notes with other software. 40 working days and 528 commits later, here's what I've added: * added support for multiple notes * ability to store notes on disk * and if you store notes in a directory managed by DropBox, OneDrive etc., you get sharing of notes between computers * Ctrl + P: UI for switching between notes, creating new notes, deleting notes, inspired by Notational Velocity * Ctrl + Shift + P: command palette like in vs code * context menu to access frequently used functionality * Ctrl + E to open note from history (list of recently opened notes) * ability to assign Alt + 0 ... Alt + 9 quick access shortcuts * ability to encrypt notes with a password * export all notes to a .zip file * automatic, daily backup of notes to a .zip file (optiona, see Settings) * Ctrl + B to navigate between blocks * re-designed Settings UI * added ability to execute Go blocks * support Svelte and Vue in code blocks * ported the UI code from Vue to Svelte 5, just because I could * converted from desktop app to run in the browser (Ctrl is on Windows, on Mac it's ⌘). I've been using it daily while working on it. 94 notes and counting. I still have ideas for improvements but it has all the core features for productive work. The app: https://ift.tt/thpRJO4 The code: https://ift.tt/QApaIEF
Subscribe to:
Posts (Atom)