My favorite part of the web is that it makes things hackable. Stuff like userscripts or even being able to muck around in devtools makes it so much more empowering than native apps that give you a "take it or leave it" approach to apps.
Mobile apps make me so mad because they give me no control over my device even with the prospect of "app permissions".
✊
@hisaac too many zooz, saxophone growlbass
@gabek you are a wonderful person 💚
@hisaac jakeenos is like parkway but better IMO.
Savoy is for when u want a solid centimeter thick of cheese on your pizza. IMO the one with Giardiniera, the chicago one, is the best at savoy
@hisaac I live near wrecktangle Detroit style pizza, apparently they are critically acclaimed, I think they are ok.
Otherwise jakeenos and savoy are good.
Just be warned savoy puts an insane amount of cheese, I always ask them to reduce the cheese quantity but its still too much
@t54r4n1 source: I have ridden an impossible wheel
@t54r4n1 aaahcktually, its an electronic impossible wheel
LOL
https://scholar.google.com/scholar?q=%22thank+alexandra+elbakyan%22
My brother is gonna love this hahaha
Okay, this is nuts!
While viewing a live #owncast stream, you can follow, as you'd expect from the #fediverse
BUT!!! When using the #liveChat you can link your identity to your #mastodon account with #FediAuth !!!! What!;?
It then sends you a DM with the AuthCode directly to mastodon!
Wow, #activitypub is awesome!!
> why use them?
Because its the only way to implement login without requiring JavaScript.
Cookies aren't inherently bad. There are some quirks, specifically the SameSite attribute. I eventually settled on two cookies, one SameSite strict and one SameSite lax. Both HTTP Only (not exposed to js) and both having a server side session token.
That way I can allow 3rd party referrer links to be logged in for specific actions ( click link in webmail to confirm email address ) while staying secure against 3rd party request forgery vectors in general.
@teal@cannibal.cafe @em@cassilda.house @mauve
At least last time I was looking at this, the libp2p libraries worked OK for apps, just not for browsers / interoperability w/ browser stuff.
I think a large part of the problem is that what libp2p is trying to do is kinda impossible, the image that they "sell" where it "just works" with pure p2p and no server, is and always will be unrealistic. Because of the "original sin" of ipv4 and NAT, there will always be a need for a server / rendezvous point.
I still use the UPnP client from libp2p, I its really good IMO. https://git.sequentialread.com/forest/go-libp2p-nat
I think webrtc is the way to go for publishing cuz it supports browsers, I like the Pion webrtc libraries cuz I can fairly easily get server<->server, server<->browser, and browser<->browser, working, and it has a feature where you only have to open / forward one UDP port on the server so it makes it easier to host. WebTorrent is also pretty cool.
I am a web technologist who is interested in supporting and building enjoyable ways for individuals, organizations, and communities to set up and maintain their own server infrastructure, including the hardware part.
I am currently working full time as an SRE 😫, but I am also heavily involved with Cyberia Computer Club and Layer Zero