Bike to Wherever Day

Bike to Wherever Day
By

Join people across the city bicycling today for the annual Bike to Wherever Day. The SFMTA is proud to be the official citywide sponsor of Bike to Wherever Day 2023, San Francisco's favorite biking celebration!   

Hosted by the San Francisco Bicycle Coalition, Bike to Wherever Day celebrates  bicycles as a fun and healthy way to get around. This annual event invites people to pedal to their destinations, and it promotes bicycling both as an alternative commute and as a healthy and safe alternative to driving to…wherever. 

We encourage everyone, including those who don't usually bike, to get out and cycle today. After grabbing some wheels  (your own or a bikeshare bike), consider joining one of the Neighborhood Rides. Need more reason to stop by? You also can pick up your free Bike to Wherever Day canvas tote bag, filled with goodies, courtesy of the SF Bicycle Coalition. 

Resources to Help You Plan Your Bicycle Trip 

The SFMTA has go-to resources to help you plan your bicycle trips.  The interactive bike network map highlights recommended routes and shows bikeshare station locations. Go to our Get Out, Get Going website  to find an interactive multi-mode map with information about other sustainable ways to get around that you could pair with your bicycle trip, including walking and using shared mobility devices, like a scooter or moped.   

The SFMTA supports low-carbon transportation options like bicycles, and we continue to expand our dedicated bike lanes around the city to make streets safer and more comfortable for bicycling.  

You can check out our Slow Streets Program with over 18 corridors  that have traffic limitations so they can be used as shared spaces with walkers and bicyclists. Biking, scooting and rolling  are integral to our new Active Communities Plan, a 2-year process to develop a plan for active mobility in San Francisco.  For more information, visit the project website (SFMTA.com/ActiveCommunities).  

Published May 19, 2023 at 02:50AM
https://ift.tt/s2cFGH4

Show HN: Jesth – Next-level human-readable data serialization format https://ift.tt/r0FJsNl

Show HN: Jesth – Next-level human-readable data serialization format Hi HN ! I'm Alex, a tech enthusiast. I'm excited to show you Jesth, a next-level human-readable data serialization format. This project started out as a markup language for writing the docstrings of functions that would ultimately be consumed by a documentation generator. Basically the idea was to split a docstring into sections like Description and Parameters. Each section would consist of a header in square brackets and a body (lines of text between two headers). Here's what a docstring for a sum function would look like: This function takes in two integers a and b and returns their sum. [parameters] - a: First integer - b: Second integer [return] Sum of a and b The Description section in the example above is actually an anonymous section, i.e., a section with an empty header. Meanwhile, I was thinking of a way to automate part of my dev workflow by storing in a file commands grouped into tasks such as project creation, build, testing, release, et cetera. Similarly with the markup language for my documentation generator, I would use square brackets to define the tasks. Thus, a task would consist of a header and a body which would be a list of commands to be executed sequentially. I built this project and named it Backstage. Here is a hypothetical backstage.tasks file: [release] & test & generate_doc & git_stuff & build # upload to PyPI $ twine upload --skip-existing dist/* [git_stuff] $ git add . $ git commit -m {message} $ git push origin master The example above is illustrative only and would not work. It contains 2 sections "release" and "git_stuff". Running the "release" task from the command line is equivalent to sequentially executing the commands in the "release" section. The documentation generator and the scripting language, despite the obvious similarity in their formats, did not share any parsing code. So, to stop repeating myself, I created a file format and its library named Jesth which stands for "Just Extract Sections Then Hack". The library acts as an incomplete INI file parser that only hands the programmer the sections (as headers and their associated bodies which are lists of strings). No further interpretation of the data is done by the parser, allowing the programmer to unleash their creativity through useful hacks. In its latest iteration, Jesth has matured and also includes a proper and extensively tested hack to convert a compatible section into a dictionary data structure, making Jesth my de facto preferred format for config files. I find Jesth more readable than TOML, YAML, and JSON. Here, encoding a dictionary data structure in its own section with another section containing a prompt for ChatGPT: [prompt] I want you to act as a detective story writer. I will provide you with two dictionary data structures representing the profiles of two people. Your goal is to write a thrilling neo-noir story. My first request is: "guess who the killer and victim is from the profiles, then build a story that includes every detail of the profiles". [profile] # This section can be converted into a dictionary data structure name = 'Jane Doe' birthday = 2000-12-23Z10:17:37Z photo_jpg = (bin) VGhpcyBpcyBub3QgYSBwaG90by4uLiBCdXQgdGhhbmsgeW91 IGZvciB5b3VyIGludGVsbGVjdHVhbCBjdXJpb3NpdHkgOyk= --- books = (dict) romance = (list) 'Happy Place' 'Romantic Comedy' sci-fi = (list) 'Dune' 'Neuromancer' epitaph = (text) According to the law of conservation of energy, no a bit of you is gone; you are just less orderly. --- [profile] name = 'John Doe' birthday = null books = (list) 'American Predator' 'Mindhunter: Inside the FBI's Elite Serial Crime Unit' You can learn more by reading the project's README and playing with the demo. Let me know what you think of this project. https://ift.tt/WUjhpIo May 18, 2023 at 10:38PM

Show HN: Do not chat with your pdfs alone. Let others join the fun too https://ift.tt/EuyifFp

Show HN: Do not chat with your pdfs alone. Let others join the fun too https://ift.tt/QlL4OcS May 18, 2023 at 02:31PM

Show HN: Cosigny - Crowd source the best credit card and loan terms. https://ift.tt/p0zM8cG

Show HN: Cosigny - Crowd source the best credit card and loan terms. The goal is to create spreadsheet with crowd sourced data regarding credit products and profiles so we can see how we measure up and find the best deals. Don't go too hard on me. I linked a few google sheets together. Hope you find it useful. https://ift.tt/xYIObfq May 18, 2023 at 10:41AM

Show HN: PENVM – Programmable, extensible, network virtual machine https://ift.tt/HFIoMqB

Show HN: PENVM – Programmable, extensible, network virtual machine The PENVM platform provides the building blocks to facilitate the leveraging of networks. There is no lack of frameworks and tools for working with servers, communicating over the network, and processing. What PENVM does is make this simple and easy to use, reuse, and share. Low-level concerns with networking and communication are not exposed. Network setup and management is simple. Communication is uncomplicated. And integration within applications is smooth with freedom to apply as needed. PENVM provides the means to get up to speed quickly with little hassle. This kind of development does not need to difficult anymore. https://penvm.dev/ May 17, 2023 at 11:42PM

Show HN: Metatype – an open-source HTTP/GraphQL query engine for APIs and data https://ift.tt/ZDorpuO

Show HN: Metatype – an open-source HTTP/GraphQL query engine for APIs and data Hey everyone, we built Metatype [0] as a different way to build APIs and backends based on 3 parts: 1. a Python package to build virtual graphs connecting all components of your stack (think databases, third-parties, and existing systems) 2. an HTTP/GraphQL query engine built in Rust/Deno that authorizes and optimizes queries over the graphs 3. a CLI to provide a nice developer experience and fast feedback cycle We developed this platform to tackle some of the challenges we often saw in tech teams we worked with: - most developers (especially backend) still spend too much time on tasks with no real added value (crud, data validation, compliance, etc.) - when growing a product, it is difficult keeping up with business needs and remaining agile/innovative with technology (especially when there is limited funding) We believe it provides multiple advantages over more traditional approaches: - it offers multiple runtimes [1] with pre-defined operations (e.g. Prisma) and can replace the needs for an ad-hoc backend - when the project grows, you can easily introduce new APIs or break existing ones in smaller parts while keeping the same interface - you can write complex business logic directly in Typescript or Python and run them directly inside the query engine - most of the frontend are today built on composable components, this brings a similar approach to backend development - third-parties APIs can be easily integrated, providing you visibility and control over them - it is interoperable with existing systems, and can be introduced step by step - it can be easily self-hosted or customized according to your needs The project is now in public beta, and is run in production by a few companies. We are looking to collect more feedback and early users to help us improve the platform. For the tech curious reader, we also had to build a few new open source pieces to make this happen: - a WASI runtime for Python [2] to run Python code inside WASM inside the engine - a task runner [3] supporting live reload and managing dependencies as DAGs - a way to inject secrets [4] from your preferred vaults into the engine [0]: http://metatype.dev [1]: https://ift.tt/NbjL8V1 [2]: https://ift.tt/M5CaLTc [3]: https://ift.tt/V489aDX [4]: https://ift.tt/SW1gxE0 https://ift.tt/xRtwS3I May 18, 2023 at 01:55AM

Show HN: LogSpend – Gain full visibility and control over your OpenAI costs https://ift.tt/KyPoCeG

Show HN: LogSpend – Gain full visibility and control over your OpenAI costs https://logspend.com/ May 18, 2023 at 01:06AM