The reason why I am building an alternative to #Obsidian is simple:
I want a native notes app for #macOS that supports #Markdown with live-preview.
The **native** part is what’s important. I want something natively built for the macOS platform.
I know there are native Markdown editors for macOS, but none of them support REAL live-preview. At least not that I could find. And believe me, I’ve been looking…
They all have this side-by-side feature with the raw Markdown syntax on the left and the rendered Markdown on the right.
I also have many more ideas, like building a moodboard with an infinite canvas for notes, links, images, and videos.
**Basically, the perfect app for brainstorming new ideas!**
View quoted note →
Frederik Handberg
npub1nj0c...2gqz
23 🇩🇰 Studying for a degree in Software Engineering while building fun projects and working freelance as a News Photographer 📷
I share my software projects, photos and videos from my work as a news photographer, and progress updates as I learn to sew garments.
Basically, I just write about my hobbies.
frederikhandberg.com
I’ve mentioned before on #Nostr that I want to build a #Markdown notes app with live-preview, exactly like how it works in #Obsidian (my favorite notes app).
Today I finally had a few hours free to develop a little prototype, just to see if I could get the live-preview part working.
Good news: **it actually _mostly_ works!**
Basically, if you haven’t tried Obsidian, here’s how it works:
- It supports Markdown, but so do a lot of other apps.
- What makes Obsidian so good (imo at least) is the live-preview. By default, it hides the Markdown syntax, but when you put the cursor inside some styled text, the syntax shows up again.
My prototype isn’t perfect yet… Notice how if there’s italic text inside bold, only the outer styling shows up.
#dev #macOS #Swift #AppKit
There’s a thunderstorm right now with heavy rain.
I saw all the flashes of lightning and thought it would be cool to get on video.
Nothing happened, so I stopped recording and went back to bed.
Then of course the lightning started again… ⛈️⚡️
My first post from Nosotros!
btw. there’s some overflow in the dialog when writing a post. At least it happens when quoting another post.
View quoted note →
Wow. The UI looks awesome 🤩
View quoted note →
I had underestimated how much SVG code it takes for a QR code.
It was simply not practical to inject the SVG code directly into the `<script>` tag like `data-qr-code="data:image/svg+xml;base64,…”`.
Especially because the `<script>` tag is something clients will be using, it looks rather unprofessional to have a ton of lines of code just for a QR code.
Instead, I opted to use an API called `QRServer` to show QR codes on clients’ websites.
When clients use the widget creator, I don’t use the API. Instead, I generate the QR codes locally using an NPM package called `qrcode-generator`. The QR code updates in real time as the user types their URL, which would put unnecessary strain on the API - that’s why I generate the QR codes locally. #dev
View quoted note →
The Web's Missing Piece: How DID-Nostr Quietly Solves Social Portability


DEV Community
The Web's Missing Piece: How DID-Nostr Quietly Solves Social Portability
After decades of platform lock-in, the first truly portable social graph standard has arrived. It's...
It’s crazy that #ActivityPub still doesn’t have a solution for letting users switch instances while transferring their posts and comments.
At least #ATProto has solved that problem.
And then we have #Nostr where you never need to worry about that. Just run a private relay, and then you have a backup of all your events, allowing you to broadcast them to new relays.
Injecting SVG code into the script tag was a mistake. I hadn’t thought it through… Turns out it takes a lot more SVG code to build a QR code than I imagined 😅 #dev
View quoted note →
I'm doing an internship for my Software Engineering degree this fall semester.
One of my tasks is to develop a widget that clients can embed on their websites using a simple `<script>` tag. That tag should fetch a JavaScript file from our server that contains all the logic.
Yesterday I worked on coding the widget's UI. Today I need to figure out how to handle QR code generation. Ideally, I'd like to do it on the client side so we can avoid building API routes or storing anything in a database.
I’m looking at the npm package `qrcode-generator`.
With it, I could probably just generate the QR as SVG and inject it directly into the page from the script. #dev
In my opinion, there’s no reason at all to have these kinds of metrics on a decentralized protocol like Nostr.
Metrics like follower counts, like counts, total views, etc. are never going to be accurate anyways.
*By accurate I also mean by humans.*
They aren’t even accurate on centralized platforms like Facebook and Instagram because of all the bot accounts.
The only to get accurate metrics is to have a centralized platform that requires ID verification to create an account. And, one ID can only be associated with one account. Then creating bot accounts become an impossible task.
We should obviously not want this. It’s dystopian…
I’m just saying to explain that these kinds of metrics are irrelevant on Nostr.
View quoted note →
#press


#Communities on #Nostr would be really cool. Basically, I want communities similar to how subreddits work on #Reddit.
I’m not entirely sure how it should work, or if the features I think are necessary are even possible on Nostr given how relays work.
Ideally, there should be moderation which would require admins, because who else is going to remove unwanted posts and comments. Like, if the community is about a certain topic, then it’s annoying if someone posts something completely unrelated.
**Some of the features that would be required imo:**
- Users can create communities with a name, description, and a photo/banner.
- The creator and admins can assign and manage group roles.
- Admins should be able to remove unwanted posts and comments.
- Admins should be able to ban unwanted users from the community.
- Communities can be public, private, or invite-only.
- Users can join public communities.
- Private communities would require approval from an admin before being able to join.
- Invite-only communities require an invitation to join. Invites could be sent via Nostr DMs.
- Users can publish posts to communities.
- Communities should be able to decide whether posts require approval before being published.
I wonder if someone is working on this stuff already 🤔
I think communities could really shine on Nostr, especially now that Reddit is starting to require ID verification.
It’s scary. Surveillance is everywhere, both online and IRL…
These two are adorable ❤️😂
Video from the structure fire in Løsning 🔥 #press
More pictures from the structure fire occurring right now in Løsning 🔥 #press


Villa totalskadet efter voldsom brand i Løsning.
House completely destroyed after severe #fire in Løsning. #press


By far the biggest field #fire I’ve been to 🔥 #press