3 ms·

Here is my take on the subject, in my case I was more curious what a shared public postgres server would feel like. https://www.public.outband.net https://www.

• cbdevidal 10mo ago
  Broken link
  • somat 10mo ago
    Unfortunately the whole thing is ip6 only. A side effect of how I wired everything up. I run the whole thing from my closet over an free he ip6 tunnel.
  • x______________ 10mo ago
    try https://web.archive.org/web/20250224200029/https://www.public.outband.net/ https://web.archive.org/web/20250224200029/https://www.publi...
• arjie 10mo ago
  This is fun. I thought at first it was my TERMINFO (xcolor-ghostty) but it's actually that it just takes a short while to load in the SSH public key before you can login. Sadly I can't see anyone else's databases. I thought that's where the fun would be! Maybe I'm doing something wrong. Anyway, look in prespecialize.public.messages for a message! I tried putting something at https://www.public.outband.net/home/prespecialize/index.html https://www.public.outband.net/home/prespecialize/index.html but I must have the permissions wrong, alas! Anyway, fun project :) I thought it was clever you used IPv6. Places a tiny little barrier to entry.
  • somat 10mo ago
    Every person gets their own postgres schema, sort of a namespace, other peoples tables will be under name.table but they have to grant access. something like "grant usage on schema myname to public_user; grant select on best_books to public_user;" or use row level security to grant controlled updates. create policy book_mod on best_books using (uid = current_user); grant insert(book, review) on best_books to public_user; grant update(book, review) on best_books to public_user; an example is foregoer.collab_data It looks like I left a bad public_html link in new accounts home directory the path is actually /var/www/(user_name)/ a fix could be "rm public_html; ln -s /var/www/${LOGNAME} public_html but I will probably go through and fix them administrativly