Well, I started this morning fixing a minor bug in FeoBlog. But then the GitHub Action build failed which sent me down a day-long rabbit hole that ended up with me upgrading from ActixWeb v3 to v4.
It's a bit disappointing because Rust is in theory not supposed to break backward compatibility. But I guess some bits of their API leaked and then got used by libraries I was using.
Not really what I had planned for my Sunday but glad to be on newer versions of things, I guess? 😅
Me: You should remain professional and avoid burning bridges.
Facebook recruiter: Hi! Want to use ML to moderate virtual social spaces?
Me: On second thought, …
When Node became popular, I never understood the hype around server-side JavaScript, other than that it took what had before then been mostly client-side and making it usable on the server.
But the pitfalls of writing large systems on the server without type checking seemed too great. And I wasn't that fond of JavaScript at the time.
By the time I got around to playing with Node more seriously, TypeScript was a thing. In FeoBlog I wanted to write a browser-based client that would both be a nice UI and a great demo of the client/server capabilities of the system. I chose Svelte as my UI toolkit, and I very much enjoy the features it offers. However, bundling JavaScript for the browser is still a pain to get working. And if you ship everything as a Single-Page Application, you lose out on indexing, and old/underpowered browsers.
FeoBlog actually has remnants of an early server-side template system which it falls back on for that purpose, but you lose out on a lot of features, and it's lost parity with the new Svelte UI. It would be nice if I could write code once and have it render on the server OR the client.
So now I'm starting to see the appeal of server-side JS. But... I don't really want to run Node. Thankfully there's Deno, which I've already enjoyed writing some scripts for.
AND, there's a cool new web framework called Fresh. It's got the same super-fast dev cycle that I've enjoyed with Deno, and the result is code that can render things on the server OR client.
If you want to see a(n incidental) demo of Fresh, take a look at Deno Deploy: Crazy Fast Cloud Functions - Architecture Speedun, which is where I first discovered it.
Looking forward to see where this goes!
I do not have a kind view of anyone who brags about not voting. And anyone trying to convince you not to vote has motives you should definitely question.
… But watching the Democrats just roll over on every damned thing is really making it feel like a pointless ritual. Democracy Theater.
They're guaranteed the vote of anyone like me who is against what Republicans are doing, so won't throw away their vote on a further-left party. But as a result they keep moving right to try to pick up more "middle" voters.
Feeling a bit frustrated and hopeless about the future for the U.S.
Just to be clear, though: I'll still be voting.
Uhh, WaPo… is this an ad for Trump? "Inaction" as democracy "came under attack"? He was and is continuing to attack democracy by continuing to lie about the legitimacy of the election. He spoke at the rally that ended up invading the capitol while the election was being finalized! And told them to do it! WTF kind of reframing is this?
This is as bad as the bootlicking "shots were fired and someone died at an altercation involving police" trope.
I've been writing Java since before Generics and still ran into this landmine:
Coworker (reviewing my code): container.contains(null)
can throw a NullPointerException.
Me: I don't think so, the docs say:
Returns true if this collection contains the specified element. More formally, returns true if and only if this collection contains at least one element e such that (o==null ? e==null : o.equals(e)).
And this code works as I expect:
import java.util.*;
public class Contains {
public static void main(String[] args) {
// Interestingly, List.of requires all its elements be non-null. Weird.
// var list1 = List.of("foo", "bar", "baz");
// var list2 = List.of("foo", "bar", null);
var list1 = makeCollection("foo", "bar", "baz");
var list2 = makeCollection("foo", "bar", null);
check(list1);
check(list2);
}
private static Collection<String> makeCollection(String... args) {
// return Arrays.asList(args);
return new HashSet<String>(Arrays.asList(args));
}
private static void check (Collection<String> list) {
System.out.println(list.contains(null));
}
}
Coworker: read a bit further. Docs also say:
Throws […] NullPointerException - if the specified element is null and this collection does not permit null elements (optional)
… sure enough. In my case I'm actually using a Set.of(predefined, elements)
, and that particular implementation will throw
if passed a null
.
UGHHh. NULLS.
FWIW, Kotlin handles this much more nicely:
fun main() {
val c1 = setOf("foo", "bar")
val c2 = setOf("foo", null)
val value: String? = null
println(c1.contains(value))
println(c2.contains(value))
}
… though you can only depend on that sane behavior when using its setOf()
constructor. If you might ever be passed a non-null-safe Java Collection you're back to needing to protect yourself against NPEs.
So the Supreme Court is going to overturn Roe v. Wade and basically let religious fundamentalists control women's bodies.
I feel the need to write something about it.
But then the next thought is: Oh, I should take some time, really organize my thoughts, find links to sources, etc, etc. That way lies me never writing anything. "Perfect is the enemy of good [enough]", etc.
So instead, here's my stream-of-thought braindump.
First, this is terrible. It's terrible for women. Especially in states that want to ban abortion. (And even with RvW many had already effectively banned it by making it practically unavailable.) Especially poor women who don't have the means and connections to leave for more liberal states.
If the court is saying there is no right to privacy, next you'll have states start outlawing contraception.
Then they'll pass laws saying it's illegal to travel to another state to get an abortion. (I think some already exist for minors?)
Without a right to privacy, anti-sodomy laws are back on the table, and also gay marriage bans.
Without a right to privacy, the government can regulate all sorts of personal details about your life with … what limits?
The permissibility of abortion, and the limitations, upon it, are to be resolved like most important questions in our democracy: by citizens trying to persuade one another and then voting.
Yeah, because that worked out so well for slavery, and interracial marriage, and segregation, and gay marriage. And, oh, what's that? Abortion.
It's just such a big "fuck you". "If you want rights, you should merely convince the majority to stop taking them from you."
And, as I've seen others point out, that's a double "fuck you" in the context of the court recently gutting the Voting Rights Act and states ramping up voter suppression and gerrymandering.
The political process is broken and I don't see it getting better any time soon.
$OurProduct is a love letter to $audience. ❤️
Look, if you're describing something as a "love letter" and then charging money for it, that's "solicitation".
Saw this one while out yesterday. Anybody know what kind of flower it is?
Uh-oh. "Svelte" has taken over as the language with the most lines of code in FeoBlog.
It's funny. I started FeoBlog because I wanted the data structure to be the way that distributed social networks work. But in order to make using that appealing, you've got to have a nice UI. And it turns out there's a lot involved in working toward one of those. Who knew?
So sounds like Twitter's getting bought in a hostile takeover.
I've been working on the next version of FeoBlog and I had a couple more features that I wanted to sneak in, but I should just release what I've got. (Agile! (lulz))
If you want to help me test it, or just want to play around with an open, distributed platform let me know!
I've been working on the next version of FeoBlog quite a bit lately. It's been fun!
One of the new features will be allowing FeoBlog to remember your private key for you, since working with them can be a bit cumbersome. I enjoyed this little experimental UI for letting users configure that behavior based on their preferred security level:
However, it ended up being a bit cumbersome to use in practice, so I'm going to change it to instead give you all the options, and then details about the security implications of the options you set. That way, it's less about shaming the user to choose the higher security level, and more about letting them configure it how they want and informing them of the consequences.
Another of the new features is Windows support! I switched to using ESBuild instead of Snowpack. Not only is it able to properly bundle, on Windows, I think it's actually faster as well. AND I found a plugin that lets me write my web worker as a module and inline it within the app bundle. 🎉 Definitely would recommend trying it if you're deploying JS to the browser.
Since about v0.5.0, I've been using FeoBlog as my own sort of RSS reader. I've got a few scripts that read Twitter, Mastodon, and some RSS feeds into FeoBlog for me, and then I just view my "My Feed" page and there's everything in one convenient place.
One surprising benefit of this is that I actually feel less of an urge to keep on top of things. The feed isn't going to get reordered by some unknown algorithm. There's no little "unread" counter telling me how many more I have to read until I'm "caught up". Plus, those posts aren't going to go away, I'll always be able to find them in the feed history. (Though it could be easier.)
So, generally a more healthy relationship with social media. Which is to say: I'm reading a bit less than before.
I’m flying home to San Diego today. Trying to check in to my American Airlines flight, they’re telling me I can’t carry on my bag, and offering to charge me to check it.
But their web site says:
… sooo which is it? I guess I’ll check in at the counter and see. Hopefully the lines aren’t bad. 🤞
https://github.com/NfNitLoop/feoblog/releases/tag/v0.6.0
Support for the Open Graph Protocol.
Now when you share links to other web sites, (or Discord) they'll be able to generate previews if they support OGP.
Quick access to share links.
Click the arrow at the top-right corner of a post to access share links.
db prune
to remove data that's no longer being used.
db usage
to see who's hogging all your disk space.
(See also: The tablestream crate I created to help with this output.)
So, working on FeoBlog, I wanted to print some data into a table in a terminal, and I was picky about how I wanted to do so, so I wrote my own.
In particular, I wanted to be able to:
The existing ones I found on crates.io required holding the table in memory.
So I just wrote my own:
There's now an official Discord server for FeoBlog. If you have questions, feedback, or just want to chat, drop on by!
Note: Discord invite links can expire, so check this user's profile for the latest link if the above one doesn't work.
Released: July 18, 2021
https://github.com/NfNitLoop/feoblog/releases/tag/v0.5.0
You can now filter and search your "My Feed" page.
Is someone posting a bit too much today? You can temporarily hide them from
your feed to see what everyone else has to say. Looking for a post you saw
last week? Now you can search for a keyword and view only posts/comments that
mention that.
Posts are no longer clickable.
Previously, the entire block containing a post was clickable, and would take
you to the page for that post. But that resulted in a lot of accidental
clicks. Also, since the cursor changed to a pointer for the whole block, it
was difficult to see if images were clickable. Now that behavior is gone. You
can click on the timestamp of a post to go to a page for just that post.
#52 Automatically redirect to the "My Feed" page when logged in.
If you're logged in, you're probably repeatedly coming to FeoBlog to check
your feed. So that's now the default view.
Whew. Have been working on some nice FeoBlog changes that I'll probably release this weekend.
I should probably make another video. The UI is looking much better now than the one I showed in v0.1. Plus, I've learned a couple things about video capture since then.
But for now, shower and bed. 😴
Now available here! https://deno.land/x/feotweet@v0.2.0
It adds support for syncing a single user's tweets to FeoBlog, as well as copying tweet attachments into FeoBlog.
Developing in Deno is still pretty fun. Though I did spend a couple days scratching my head due to this bug.
Apparently HTTP clients don't do well when you close the HTTP connection when they're still sending bytes at you, even if you've already sent a response.
The HTTP 1.1 spec isn't super clear on what should happen in this case. For example, it says this about closing connections, but seems to imply it's only for idle connections:
A client, server, or proxy MAY close the transport connection at any time. For example, a client might have started to send a new request at the same time that the server has decided to close the "idle" connection. From the server's point of view, the connection is being closed while it was idle, but from the client's point of view, a request is in progress.
This means that clients, servers, and proxies MUST be able to recover from asynchronous close events.
And it says this about "Client Behavior if Server Prematurely Closes Connection":
If at any point an error status is received, the client
SHOULD NOT continue and
SHOULD close the connection if it has not completed sending the request message.
... but that's only in the case of an "error" status, not an OK status.
Chrome handled this case by ... pausing for about 5 seconds, then continuing without error. (!?) And Deno handled this case by ... well, in the case I reproduced in that bug report, the next call to fetch()
would fail, but during debugging I saw other sorts of odd failures. Like calling .read()
on a Deno.Reader
that seemed completely unrelated to the HTTP connection would fail and say the rid
(Deno "resource ID") was invalid. Yeah, that one had me confused for a while. I wasn't able to reproduce that one in a minimal example, though.
I was able to work around the issue by just waiting for all the bytes to be sent before sending an HTTP response. But this seems like a thing that people could use to DoS your server. If you try to be nice and read all these unnecessary bytes they sent to you they can just do it forever. Though I guess there are countless other ways to DoS an HTTP server in addition to this, so what's one more?